Netobs Servers

Managing configuration of dashboards, folders, and alert rules can be difficult. By adding Grafana, Mimir, and Loki server(s) to the Nautobot Netobs App, the app can back up critical pieces of information for you.

While there is only 1 Nautobot job associated with this, it can be scheduled to run at periodic intervals to backup the Telemetry servers.

Config

There are some settings in Constance that can be set to configure Netobs Servers. To edit these, go to the Netobs Dashboard and click on config.

Name	Description	Default
NETOBS BACKUP BASE_DIR	If the backups need to be put in a subfolder	``

Netobs Server Models

Netobs Servers are observability servers you want to backup potentially user created data that doesn't live in Git.

The server is connected to an External Integration in Nautobot. In a kubernetes or docker environment, it would be setup with the internal hostname (http://grafana.grafana.svc.cluster.local:3000 or http://grafana:3000).

The server type can be either Grafana, Loki, or Mimir so the job knows what to try and backup.

For Loki and Mimir, you can specify the Org ID that is used for namespacing in the External Integrations Header. If your using the X-Scope-OrgID in HTTP headers.

For Grafana servers, a Secrets Group with a token set is needed to access the API.

The Git Repository should be the repository you want the configs stored to. The default directory will be the slugified version of the name of the server. So if you have Grafana Dev as the name of the server then in git, it will be saved to <base dir>/grafana-dev/.

Netobs Server Backup Job

The Netobs Server Backup Job takes no input and can be scheduled to run periodically.

The job will backup any Netobs Servers that has an Active status to it's specified Git Repo.