What do you like best about the product?

The most significant advantage of Database Observability is the ability to monitor the long term changes in the databases’ activity. It makes it possible to identify workload changes over time and this can assist in proper allocation of resources. It is run in parallel with scheduling systems so that background processes do not interfere with peak times. This has helped to minimize disruptions and other such issues that would slow down the operations of the company.

What do you dislike about the product?

A disadvantage of Database Observability is that it produces a high number of alerts for minor fluctuations in performance. However, having many alerts for minor changes is not very useful as it makes it difficult to identify genuine issues. Also, tuning the alert settings requires some time and if not well done, it results in many distractions. These issues have at one time or another hindered our capacity to handle emergent database problems.

What problems is the product solving and how is that benefiting you?

Our team uses Database Observability to stop unnecessary resource expenditure by finding repetitive processing operations that require excessive power. Through these optimizations we achieved better work balance throughout the day for our system by optimizing queries and background processes. Observability of database operations enables us to discover inefficient patterns at the right time which helps lower operational expenses while improving time responses for critical programs. Due to our ongoing implementation of the system we could shift our attention toward business priorities instead of continuously solving system slowdowns.