Skip to content

Export configuration

Under Admin → System → Config export a super admin downloads the instance configuration as a ZIP file. It is meant for moving to another monitoring tool: the file contains what you would have to rebuild there, but no measurement data.

To move from Vesana to Vesana (new server, new instance) use Backup & restore. Vesana cannot read the export back in.

Selection

  • Tenants: leave empty for all tenants, otherwise only the selected ones. Hosts, checks, rules and accounts of other tenants are then left out.
  • Include credentials: without the tick every existing secret is replaced by <omitted>. With the tick they are decrypted and stored in plain text.

Below the selection the page shows how many objects of each kind are included. The download asks for an identity confirmation and is recorded in the audit log (config_export).

Contents of the ZIP file

File Contents
vesana-export.json the complete configuration (format vesana-config-export, version 1)
hosts.csv one host per row: tenant, name, IP, DNS name, folder, site, tags, profile, execution, collector
checks.csv one check per row with its effective values: type, execution, interval, thresholds, direction, target, script
scripts/ the bodies of the monitoring scripts in use as files (.sh, .ps1, .py)
README.txt short description of the files

The CSV files are UTF-8, comma separated. A value starting with =, +, - or @ is prefixed with ' so that a spreadsheet does not run it as a formula.

What vesana-export.json contains

  • tenants, folders (with path), sites, collectors (without keys)
  • hosts with their credential fields (SNMP, SSH, API), profiles and checks
  • checks with their effective values: profile value and per-device override are combined
  • the profiles the hosts use, with their checks
  • monitoring scripts with description, interpreter and adjustable values
  • notification channels, alert rules with escalation steps
  • dependencies, scheduled and recurring downtimes
  • credential sets
  • users (without password and second factor) with their roles per tenant, roles with permissions, teams with members

Every object carries its id. References such as host_id, tenant_id or channel_ids on an alert rule point to ids in the same file. Where it helps, the name is given next to it (tenant, folder, profile, script).

Not included

  • measurements, history, logs, audit log, current status
  • agent tokens, API keys and collector keys: useless outside Vesana
  • dashboards, maps and status pages
  • internal telemetry checks of the agents