Hello,
We are currently having an internal discussion about the best path to evolve from traditional monitoring to an observability approach using SWOSH.
Monitoring individual components such as CPU, memory, availability, network interfaces, databases, services, and applications is relatively straightforward. The bigger challenge is moving beyond component-level monitoring toward an end-to-end, service-oriented observability model.
Our initial approach is to select a few critical services as a pilot and gradually build dependency mapping, health indicators, alerting, and correlation capabilities around them.
For those who have already gone through this journey with SWOSH:
How did you approach the first steps?
Can SWOSH alone provide the capabilities required for end-to-end observability?
Did you start with infrastructure monitoring or with business/service-level visibility?
How did you map dependencies between applications, servers, databases, networks, and other components?
Which SolarWinds capabilities delivered the most value in the early stages?
How did you design service-oriented dashboards and alerts?
At what stage did AIOps and event correlation become part of your observability strategy?
I would really appreciate hearing about real-world experiences, lessons learned, recommended approaches, and best practices from the community.
Thank you.