Skip to main content

Documentation Index

Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

A site is the operational record for a managed MikroTik router. SDX stores the site record, enriches it with metadata, and uses it as the target for policies, jobs, backups, scripts, workflows, metrics, and reports.

​
Prerequisites

Before you manage sites, make sure you have:
  • Permission to view or manage sites.
  • A clear naming and tagging standard for your organization.
  • Router access if you are onboarding a physical device.
  • A control plane policy ready for new sites.

​
Create a Site

1

Open Sites

In the SDX portal, go to Sites.
2

Add the site

Select Add, enter a site name, and save the record.
3

Onboard the router

Open the new site, generate the bootstrap command, run it on the MikroTik router, and wait for the first heartbeat.
4

Add context

Add tags, notes, and any required metadata after the site appears online.

​
Understand Site Status

Online

The router is checking in and SDX has recent heartbeat data. Live commands and remote access are more likely to succeed.

Offline

SDX has not received expected heartbeats. Queued jobs can still be accepted by SDX, but the router cannot pick them up until it reconnects.

Last Seen

The most recent timestamp SDX has for the site. Use this with fault history when you investigate intermittent links.

Tunnel State

The management tunnel state. Live commands and transient access depend on the active management path for the site.

​
Review a Site

Open a site to inspect:
  • Overview and status
  • Device identity and RouterOS details
  • Metrics and live dashboard data
  • Fault event log
  • Inventory and discovered devices
  • Remote access tools
  • Configuration backups
  • WAN failover settings
  • API credentials and management settings
  • Notes, metadata, and tags
Some views use stored data and remain useful while a site is offline. Live views require the management path to be available.

​
Edit Site Details

Use the site settings or overview actions to update the site name, notes, tags, metadata, or operational settings. Keep names human-readable because they appear in dashboards, reports, notifications, workflow context, and search. Changing metadata is usually immediate in the portal. Applying a device-level change, such as a policy update or job, may be asynchronous.

​
Delete a Site

Only delete a site when you are sure the router should no longer be managed by SDX.
Deleting a site removes the operating record used by downstream features. If you are troubleshooting an offline router, keep the site and use the troubleshooting checklist instead.
Before deletion:
  • Export or review any backups you need to retain.
  • Check whether workflows, reports, policies, or notification rules depend on the site.
  • Confirm the site is not part of a managed VPN, captive portal, WAN failover, or security rollout.
  • Record the reason in your internal change or ticketing system.

​
Best Practices

Name for Operations

Use names that make sense in an alert at 2 a.m. Avoid internal abbreviations that only one person understands.

Tag Before Scaling

Create consistent tag keys before you onboard many sites. Retrofitting tags after reports and workflows exist is slower.

Back Up Before Changes

Request a fresh backup before policy, script, WAN, or security changes.

Use Fault History

Do not rely only on the current status badge. Review recent faults and heartbeat history for intermittent issues.