ABA Docs Say SaaS license Not Required But Support Now Says It Is (Case 02034044, 2-Month Delay)

rajasekar

Hi THWACK Community,

We ran into a serious mismatch between SolarWinds documentation and real product behavior for Anomaly-Based Alerting (ABA).

Docs say: SaaS license is not required after Platform Connect.
Based on this, we committed the design to our customer.

Reality per Support & Account Team: ABA stops working unless a SolarWinds Observability SaaS tenant remains active.

This contradiction created confusion and a poor customer experience.

Additional details:

• Case 02034044 was opened on 31 Oct 2025
• After multiple follow-ups, SolarWinds finally confirmed the SaaS dependency on 2 Jan 2026
• Support stated this is not a misconfiguration
• Engineering logged it internally as INFODEV-11636

This has real impact on architecture decisions, licensing discussions, and customer trust.

Can SolarWinds confirm:

1. The official licensing requirement for ABA today?
2. Whether INFODEV-11636 has an ETA?
3. When documentation will be corrected so others don’t face the same issue?

bmrad

ABA is included with OSH Advanced, there is no additional licensing required. It does require a tenant in our SaaS and we've seen some instances where the tenant entitlement expiration is out of sync with the OSH license. Recently we've made some changes so I expect this issue is resolved for you. If you are still seeing a licensing error, open a support case and post the number back here.