What is our primary use case?
My main use case for Foglight for Databases is to monitor database performance and identify issues before they affect our applications. I mainly use it to keep track of database health, check slow running queries, monitor CPU and memory usage, and identify any bottlenecks. One thing I find useful is that I can monitor multiple databases from a single dashboard instead of checking each one separately. Whenever we notice an application running slowly, I can use Foglight for Databases to check what's happening at the database level and find out whether the issue is related to queries, resource usage, or database connection. It also helps us catch performance issues early through alerts, so we don't always have to wait for users to report the problem.
One specific time when Foglight for Databases helped us catch or solve a problem before it affected users was when it alerted us to unusual high CPU usage on one of our databases. When we checked, we found that a query was taking much longer than usual and consuming a lot of resources. We were able to identify the query and work with our DBA team to fix the issue before it started affecting application performance. What I appreciated was that we didn't have to wait for someone to complain about the slow application. We could see the problem early and take action. It saved us quite a bit of troubleshooting time.
What is most valuable?
The features I value most about Foglight for Databases are its real-time monitoring, alerts, and performance dashboards. The dashboard is useful because I can quickly check how our databases are performing without going through multiple screens. Another feature I really value is the ability to identify slow queries and see what's causing the performance issue. The alerts are helpful, especially when something goes wrong outside regular working hours. I also find the historical performance data useful because I can compare current performance with previous days and figure out when an issue actually started. Overall, these features make my daily monitoring and troubleshooting work much easier.
Foglight for Databases has helped us reduce the time we spend monitoring and troubleshooting database issues. Earlier, we had to spend more time checking different databases to figure out what was causing a problem. Now, we can identify the issues much faster and fix them before they affect our applications. The alerts have also helped us avoid unnecessary downtime, and our team does not have to constantly check everything manually. It has made our daily work easier, saved considerable time, and helped us keep our database running more smoothly.
What needs improvement?
I think Foglight for Databases could improve its user interface. It can be complex to navigate sometimes, especially when you are trying to troubleshoot a specific issue. It can be overwhelming for someone using it for the first time. I would also appreciate more flexibility in customizing the dashboard and alerts based on our requirements. Sometimes we receive too many alerts, and it takes time to identify which one actually needs attention. Apart from these things, the product works well for our daily database monitoring.
The reporting could be improved. Sometimes when we need to share a performance report with our team or management, it takes extra effort to get the information in the format we want. Having more ready-made reports and easier customization would be helpful. Integration with other monitoring tools could also be simpler. When we are troubleshooting an issue, it would be beneficial to have clearer recommendations on what might be causing the problem instead of having to go through multiple metrics ourselves. These improvements would make our day-to-day work easier.
For how long have I used the solution?
I have been using Foglight for Databases for one year.
What do I think about the stability of the solution?
Foglight for Databases has been quite stable for us. We haven't faced any major issues with the tool itself, and it handles our daily monitoring well, even with multiple databases connected. Occasionally, we have noticed some delays in data collection or had to restart an agent after configuration changes. These issues haven't caused any serious problems. Once the initial setup was completed, we haven't had to spend much time maintaining it overall.
What do I think about the scalability of the solution?
Foglight for Databases has been quite scalable for our requirements. As our database environment grows, we are able to bring additional databases into monitoring without having to change our entire setup. Since we are using Azure and managing different database platforms, this flexibility is useful. Adding new databases does require some configuration, and we need to consider licensing and monitoring server capacity as the environment grows. Once everything is configured, managing the additional databases is fairly straightforward. We haven't faced any major scalability issues so far, although I feel the process of adding multiple databases at once could be simpler.
How are customer service and support?
Our experience with Foglight for Databases customer support has been generally good. Whenever we raise a technical issue, the support team has been helpful and willing to investigate it. For more complicated issues, getting a resolution can take longer, especially when multiple teams need to be involved. I feel the documentation could also be improved, as sometimes it's easier to contact the support team than to find the exact solution ourselves. Overall, I'm satisfied with the support, but faster resolution times and more practical troubleshooting guides would make the experience better.
Which solution did I use previously and why did I switch?
Before Foglight for Databases, we were mainly using the native monitoring tools available with our databases, along with some manual reporting. They worked fine for basic monitoring, but managing different database platforms separately was becoming difficult as our environment grew. We moved to Foglight for Databases because we wanted a more centralized solution with better visibility into our entire database environment. The biggest difference for us has been having historical performance data, automated reporting, and monitoring information in one place. We still use native tools occasionally for specific tasks, but Foglight for Databases has made our overall database management much more convenient.
How was the initial setup?
I feel Foglight for Databases is a bit expensive, especially when you're monitoring multiple databases, as the licensing cost can add up. The initial setup also took some planning because we had to decide which databases to monitor and configure everything according to our requirements. Since we are using Azure, we also had to consider the infrastructure costs. Once everything was set up, managing it became much easier. I think the pricing could be more flexible, especially when adding a new database or expanding our environment.
What was our ROI?
We have definitely seen some return on investment, mainly in terms of time saved and better use of our team's resources. We haven't reduced our team size, but we can now manage more databases without increasing our daily monitoring workload. One example is our monthly performance review. Earlier, collecting information from different databases and preparing the reports took considerable manual effort. Now, we can pull historical data and performance trends directly from Foglight for Databases, which makes the process much easier. I would estimate around twenty to forty percent of time savings in our monitoring and troubleshooting activities, although we haven't formally measured it. I don't have an exact figure for the money saved, but reducing manual work and avoiding unnecessary troubleshooting has definitely helped us use our resources more efficiently.
Which other solutions did I evaluate?
Before choosing Foglight for Databases, we also looked at SolarWinds Database Performance Analyzer and Redgate SQL Monitor. We wanted to understand which tool would work better for our database environment, especially since we manage different database platforms. SolarWinds had some useful performance monitoring features, while Redgate was more focused on SQL Server. Foglight for Databases offered centralized monitoring and historical reporting capabilities we were looking for. We also considered the licensing cost and the effort required for the setup before making our decision.
What other advice do I have?
I would suggest understanding your database monitoring requirements before going with Foglight for Databases because the licensing and initial setup need some planning. Don't try to configure everything at once. Start with your critical databases, get familiar with the dashboards and alerts, and then gradually add the rest. Also, spend some time understanding the reporting features because there is quite a lot you can do with them. If you're managing multiple database platforms, having everything in one place is really convenient. Just make sure your team gets proper training during the initial setup so you can get the most out of the tool. I would rate this product a nine out of ten.