Configuration backup
SUSE Observability Self-hosted
Overview
SUSE Observability configuration can be exported and imported. The import/export functionality can be used to automate the installation process or for backup purposes. An export and import can be made in the settings page of SUSE Observability's user interface by using the buttons 'Export Model' and 'Import Model'.
Export configuration
An export of the SUSE Observability configuration can be obtained from the SUSE Observability UI, the SUSE Observability CLI or using curl commands.
SUSE Observability CLI
Note that the lock status of configuration items installed by a StackPack configuration won't be included in the export.
To export configuration using the sts
CLI, run the command:
curl
Note that the lock status of configuration items installed by a StackPack configuration won't be included in the export.
To export configuration using curl, follow the steps below. The <api-token>
used for authorization is available on the CLI page in the SUSE Observability UI main menu:
SUSE Observability UI
Note that the lock status of configuration items installed by a StackPack configuration won't be included in the export.
To export configuration from the SUSE Observability UI:
Go to Settings > Import/Export > Export Settings
Click the button STS-EXPORT-ALL.
Import configuration
SUSE Observability CLI
Import is intended to be a one-off action - importing multiple times might result in duplicate configuration entries. This behavior applies to importing nodes without any identifier.
Note that the lock status of configuration items installed by a StackPack won't be included in configuration export files - all configuration items will be unlocked after import.
To import SUSE Observability configuration using the sts
CLI, follow the steps below.
Before import, clear the SUSE Observability configuration by following the instructions at clear stored data.
curl
Import is intended to be a one-off action - importing multiple times might result in duplicate configuration entries. This behavior applies to importing nodes without any identifier.
Note that the lock status of configuration items installed by a StackPack won't be included in configuration export files - all configuration items will be unlocked after import.
To import SUSE Observability configuration using curl with authentication, follow the steps below.
Before import, clear the SUSE Observability configuration by following the instructions at clear stored data.
The <api-token>
can be found on the CLI page in the SUSE Observability UI main menu.
SUSE Observability UI
Import is intended to be a one-off action - importing multiple times might result in duplicate configuration entries. This behavior applies to importing nodes without any identifier.
Note that the lock status of configuration items installed by a StackPack won't be included in configuration export files - all configuration items will be unlocked after import.
Before import, clear the SUSE Observability configuration by following the instructions at clear stored data.
To import SUSE Observability configuration in the SUSE Observability UI:
Go to Settings > Import/Export > Import Settings.
Choose the
*.sty
file that you want to import configuration from.Click the button START IMPORT.
Advanced import/export
Individual configuration items
It's possible to export and import individual configuration items through the SUSE Observability user interface. For example, to export or export a component type:
Go to the Settings page and click Component Types.
To export an individual component type, click Export as config.
To import a configuration item, click Import Model.
Idempotent import/export
There is a way to use identifiers and namespaces that come with them to perform a configuration update of the specific sets of nodes idempotently. This approach doesn't lead to duplicates, but checks for the changes within a specified namespace and applies them to existing nodes, including removing nodes, as well as allow for creating the new ones.
Node identifiers are specified in a following pattern: urn:stackpack:{stackpack_name}:{type_name}:{object_name}
. The namespace effectively used by this process is urn:stackpack:{stackpack_name}:
. If every configuration node has an identifier and they're all in the same namespace, then you can perform an idempotent update using following STS CLI commands:
export
import
Last updated