Network Management

Anomaly Alerts are not being sent to the Cloud and the charts remains empty in SolarWinds Platform

Even if the Platform Connect is connected, the Anomaly Alerts data are not being populated.

First published date

12/12/2025 1:12 PM

Last published date

12/12/2025 4:17 PM

Overview

After using Platform Connect to connect to the SolarWinds Observability Cloud, the Anomaly Based Alerts are not being populated.

Only the alerts that are using "Trigger when Anomaly Detection service unavailable" option can get datapoints in the chart.

It happens because the data is in the SQL Database, not in the cloud.

Product section

Orion Platform

Cause

Some Anomaly-Based Alerts (ABA) contain nodes with category "0" (which means "something other than NetworkDevice or Host").

These nodes are not supported by our current anomaly detection flow and are causing an exception in the UAMS plugin log. 

ERROR SolarWinds.AIIM.AnomalyDetection.Client.Dal.AnomalyBasedAlertsDal - Getting anomaly based alert sources has failed
System.InvalidOperationException: There is no mapping for 'Orion.Nodes' type and category '0'.
   at SolarWinds.AIIM.AnomalyDetection.Client.Utilities.EntityTypeMap.GetSwoEntityType(String hcoType, Int32 category)
   at SolarWinds.AIIM.AnomalyDetection.Client.Dal.AnomalyBasedAlertsDal.GetAnomalyBasedAlertSourcesAsync(CancellationToken token)

This prevents the configuration of all ABA alerts from being sent to the cloud.

Resolution

In the AIIM_AnomalyBasedAlertSources and AIIM_SourceStatus tables, you can check the category of the Node.

Once you identify all alerts with Nodes Category 0, you need to delete the alerts that are linked to the Nodes Category 0 (or edit the alert and remove these nodes from the conditions).