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.

Metadata turns a list of routers into an operable fleet. Tags and site files give your team enough context to filter sites, assign ownership, build reports, trigger workflows, and investigate incidents quickly.

​
Prerequisites

Before you standardize metadata, decide:
  • Which tag keys are required for every site.
  • Which values are allowed for each tag key.
  • Who owns tag definitions.
  • Which notes or documents should be attached to sites.
  • Whether tags should be mandatory for sites or other resource types.

​
Metadata Types

Tags

Structured key-value context. Tags support filtering, reporting, workflow conditions, and resource selection.

Notes

Human-readable operational context, such as access instructions, circuit notes, or support history.

Media

Site images or visual context that helps identify the location or installation.

Documents

Files attached to the site, such as handover notes, diagrams, maintenance records, or customer documentation.

​
Design a Tag Model

Start with a small number of high-value tags. Common tag keys include:
  • region
  • customer
  • environment
  • service-tier
  • owner
  • site-type
  • maintenance-window
Use predictable values. For example, choose either production or prod, not both.
Tags become inputs to reports and workflows. Keep them boring, consistent, and easy to audit.

​
Create a Tag Definition

1

Open tag management

Go to Settings > Tag Management.
2

Create the tag

Add the tag key, choose a color, and define whether the tag should be mandatory for one or more resource types.
3

Apply values

Add tag values to sites or other supported resources.
4

Audit coverage

Review which sites are missing mandatory tags and fill gaps before using the tag in workflows or reports.

​
Add Site Context

From a site, use metadata, notes, media, and documents to capture context that is not visible from RouterOS alone:
  • Physical location or rack notes
  • ISP and circuit references
  • Customer contacts
  • Internal escalation notes
  • Photos of the installation
  • Change or handover documents

​
Use Tags in Operations

Tags are most valuable when they drive action:
  • Filter sites in fleet views.
  • Select sites for reports.
  • Route workflow logic with resource tag conditions.
  • Apply or remove tags from a workflow.
  • Group operational ownership by region or customer.

​
Best Practices

Keep Keys Stable

Rename tag keys rarely. Downstream workflows and reports may rely on them.

Prefer Enumerated Values

Use a limited set of approved values where possible.

Document Mandatory Tags

If a tag is required, explain who owns it and what each value means.

Avoid Secrets

Do not store passwords, private keys, or tokens in metadata, notes, files, or tag values.