Guest author Sahil Khanna is a product marketing manager at Moogsoft, which provides Unified Event Analytics that allow customers to detect situations from millions of application, infrastructure, and network events.
As a leading cloud-based APM solution, New Relic is in high demand by Moogsoft customers. That’s why our engineering team has created an out-of-the-box integration that allows New Relic events to be analyzed by Moogsoft and correlated with other infrastructure or monitoring events in your environment. This gives our customers what we call “360° Situational Awareness” of their production stack when problems occur.
When the application is the issue
Here’s an example of how it works: Let’s say that a JVM runs out of memory. In this situation, New Relic will note events relating to the JVM’s health, along with any impact this failure had on the user experience, via Apdex. Using New Relic, the user will have all of the information they need to identify, fix, and restore the application.
However, the application isn’t always the root cause of an application-related incident. Sometimes New Relic will note events related to the symptoms of a problem that isn’t related to application logic.
When the application isn’t the issue
When a severity one incident occurs, like an outage, customers may get thousands of events and alerts—some may be from New Relic, and some may be from the other tools in their environment. The question is, what do all these events or alerts mean? And what application, server, or device is causing the problem?
Imagine that there is a network device failure between your application servers and the database, and as a result your end user and application response times slow down and you start to receive a storm of alerts every minute.
New Relic can detect failed transactions for users and slow response times on the application because transactions can no longer reach the database. It can show numerous errors within the application and connections to the database, and it will appear that the application is the problem. New Relic knows response time between components, but it can’t break them down to network response time and server processing time because the database server is unreachable. You would have to look at all of the application events to piece together the problem. You might ask yourself, Did the database server go down?
Moogsoft integration makes the process much easier. By looking at New Relic application alerts alongside all the other infrastructure alerts that Moogsoft identified as related, you can see precisely how the problem unfolded and the cascade effect that led to symptoms being shown in the application. Moogsoft is designed to be able to indicate that there was a failure in a network device, causing connectivity to the database to fail, which caused application requests to the database to time out, and ultimately led to the failure of end-user transactions.
Gain a more complete view
When severity one incidents strike, you need a complete view of your application infrastructure health so that you can find the root cause of problems fast. Integrating Moogsoft and New Relic enables you to correlate application and infrastructure events across your entire production stack.
If you would like to integrate Moogsoft with New Relic, check out New Relic’s Moogsoft integration page and Moogsoft’s Installation and Configuration Guide. To learn more about Moogsoft, go to www.moogsoft.com.