Recommendations to others considering Foglight for Databases:
If installing on-premise, be sure to spend time upfront understanding the size of your infrastructure and the necessary server footprint for Foglight to function in a performant way. Use Linux systems for your FMS servers and dedicate resources if VMs. If including cloud-based applications in addition to on-premise, be sure to configure Foglight Agent Managers in the same cloud location and then allow those to communicate back to your on-premise. This will improve performance greatly. By all means, take advantage of the Synthetic transactions capabilities and set up FAMs to house these in cloud providers in the regions your users are located. This will help you understand the global performance of your application for your most common processes (logins, account updates, carts/purchases, etc). Review collected by and hosted on G2.com.
What problems is Foglight for Databases solving and how is that benefiting you?
This solution enabled us to monitor all of our applications and their underlying infrastructure components. This was achieved by the system's ability to group applications into what are known as Foglight "Services" and then define the various components of the applications along with the rule-sets needed to determine the overall health of the service. By doing this, we were able to group and roll-up applications into categories and expose dashboards denoting the health of these categories with various degrees of detail to specific users based on their need to see more or less details. Management and colleagues could see the overall health of high-level services, while service managers could see deep details into their particular services, while admins and developers could dive much deeper into the inner workings of the applications/systems and see all events and take actions. Review collected by and hosted on G2.com.