What I like most about SolarWinds database observability is that it gives stellar visibility into what is happening inside the database. not just surface-level metrics. It helps understand why a database is slow, not just that it is slow. I really appreciate how it shows query performance in a simpler way. Slow queries, long-running queries, and blocked queries are easy to identify without digging through logs manually. Another good thing is the real-time monitoring. When something goes wrong, I can see it happening live instead of finding out later from users or alerts. From a backend developer's point of view, it helps connect application behavior with database impact. When an API suddenly becomes slow, I can quickly check if the issue is coming from the database side. I also like that it supports multiple database engines, so I don't need separate tools for different environments. Review collected by and hosted on G2.com.
One thing I don't like is that the initial setup can feel heavy. It takes some time to configure everything properly, especially in larger environments. The interface can feel too detailed at first. There is a lot of data on the screen, which can be overwhelming for new users. Another downside is cost. For small teams or startups, pricing may feel high compared to lighter monitoring tools. Some advanced features require fine-tuning to get meaningful alerts. Without running, alerts can feel noisy. Also, learning how to fully use all features takes time; it's not something you master in one day. Review collected by and hosted on G2.com.
