Where this offering fits
Self-hosted observability is relevant when the organisation needs to operate the monitoring platform within its own infrastructure boundary. The decision includes server resources, platform maintenance and recovery, not only monitored devices. Confirm which SolarWinds capabilities the selected edition combines.
Architecture and rollout decisions
Inventory monitoring targets and the required network access. Size the deployment from the proposed supported design and retention needs. Pilot discovery, credentials and representative alerts. Assign ownership for platform patching, backups and capacity. For restricted UAE environments, the customer should approve collection permissions and any external service dependencies before onboarding production systems.
An evaluation scenario for this offering
Install the proposed self-hosted configuration in an approved test environment with representative monitoring targets and documented resource assumptions. Establish a small set of useful alerts, then have another administrator follow the platform backup and recovery instructions within the supported procedure. Include a collector or polling interruption to examine whether target health becomes clearly unknown. Review who maintains the platform operating system, software and credentials after handover. Acceptance should demonstrate that monitoring can be operated and restored by the assigned team, not merely that initial discovery worked on the installer’s account or that the dashboard currently contains live values.
Evidence to request for this scope
- Obtain a current edition and sizing proposal.
- Validate polling or collection for representative targets.
- Test platform recovery and notification delivery.