Where this offering fits
SolarWinds Observability SaaS is a hosted-service selection for the monitoring outcomes in scope. Compare it with self-hosting through operational responsibility, supported integrations and approved data processing, rather than assuming both models have identical administration and recovery requirements.
Architecture and rollout decisions
Confirm the subscription, collection components and information sent to the service. Pilot representative cloud and site sources, checking network reachability and data context. Define notification routing and what remains observable during a collection interruption. The customer should approve service-region, retention and access arrangements for the telemetry before production use.
An evaluation scenario for this offering
Onboard one permitted site source and one supported hosted workload to the proposed SaaS subscription. Record the collection components and exactly what telemetry leaves each environment. Generate a harmless known fault and follow its notification to the agreed operator. Then interrupt a test collector’s service connection and examine how the hosted view represents the resulting gap. Restore it and reconcile the timeline. The review should distinguish provider service operation from customer collector, integration and alert administration, with approved processing and retention recorded. A hosted console being reachable should not be mistaken for proof that every source is still reporting.
Evidence to request for this scope
- List subscribed capabilities and required collectors.
- Validate hosted-service and source connectivity requirements.
- Record retention, access and source-loss handling.