Documentation forSolarWinds Platform Self-Hosted

Modify multiple alerts or share alerts in the SolarWinds Platform

This topic applies only to the following products:

SolarWinds Observability Self-Hosted

DPAIMIPAMLANAMNCMNPMNTASAMSCMSRMUDTVMANVNQMWPM

Use the Alert Manager to bulk edit multiple alerts. You can enable or disable multiple alerts or add pre-configured actions.

Alerts must be enabled to be executed. For example, if an alert is scheduled to run for a short period of time each year, it must be enabled so the schedule runs. A disabled alert will not be executed, even if it is scheduled to run.

Edit alerts

Select an alert and click Edit. You can edit the alert definition:

Add actions to alerts without opening the Alert Wizard

Assign actions that you have already configured to alerts. You can assign multiple actions to multiple alerts. Actions are categorized into trigger and reset actions based on how the action was created in the Alert Wizard.

SolarWinds does not provide generic actions due to the differences in intent behind trigger and reset actions. For example, a trigger action to send an email is usually a notification that an event happened, while the associated reset action is usually a notification that the event has been resolved.

Share alerts with others (export and import alerts)

SolarWinds customers share their customized alerts in the SolarWinds THWACK community. Visit THWACK.solarwinds.com to download and import alerts created by others.

Export an alert to save the alert definition as an XML file on your local computer. Alerts are exported to XML and can only be imported from XML. You can send this file to other coworkers or share it in the SolarWinds THWACK community.

Before you share an alert, check the exported file for confidential information, such as SMTP server credentials. Delete this information or password-protect the sensitive information in the alert before making it public. Also review your company policy on sharing this type of file.

Password-protect sensitive data when exporting and importing alerts

Importing sensitive data is not supported. Secure sensitive data in alerts with a password or remove the sensitive data when exporting the alert.

Sensitive data might include:

Starting with 2024.4, a new FIPS-compliant encryption algorithm is used. As a result, you cannot import sensitive data from alerts exported in an earlier release (prior to 2024.4). If you need to import such an alert, see the workaround.

To protect sensitive data in an alert to be exported:

  1. On Alert Manager, select the alert to export.
  2. Click Export/Import > Export.
  3. Decide whether to strip the sensitive data or protect it with a password.
  4. If you decide to password-protect the data, provide a password and complete the export.

The alert is downloaded to your default download location.

When importing the alert, you can either import the alert without the sensitive data, or provide the password to include the sensitive data.

  1. On Alert Manager, click Export/Import > Import.
  2. Navigate to the location of the alert.
  3. Provide the password or select not to import sensitive data.
  4. Complete the import.

Import alerts with sensitive data that were exported in SolarWinds Platform earlier than 2024.4

In 2024.4 a new FIPS-compliant algorithm is used. Be aware that completing these steps means reverting to an older, non-FIPS-compliant algorithm.

  1. Go to Advanced settings and search for MinSupportedAlertVersion on the Global tab.

    To access advanced settings, append the following to the hostname/IP address of your SolarWinds Platform Web Console in the browser: /Orion/Admin/AdvancedConfiguration/Global.aspx

  2. By default, the MinSupportedAlertVersion is set to 1. To import an alert that was exported in an earlier SolarWinds Platform version, set the value to 0 and save your changes.

    Be aware that you are using a non-FIPS-compliant algorithm.

    You can import the alert now.