Overview
The article discusses the importance of monitoring services using New Relic and addresses a common issue known as Metric Grouping Issue (MGI) or 'metric explosion'. It provides insights on how to manage metrics effectively to avoid overwhelming the dashboard and degrading user experience.
What You'll Learn
1
How to identify and mitigate Metric Grouping Issues in New Relic
2
Why managing metrics in groups improves dashboard performance
3
When to take action if an MGI is detected in your service
Key Questions Answered
What is a Metric Grouping Issue in New Relic?
A Metric Grouping Issue (MGI) occurs when a service sends many unique individual metrics instead of managing them in groups. This can slow down the overall user experience and overwhelm the dashboard, making it difficult to identify problem areas.
How can you identify if an MGI is occurring?
You can identify an MGI by observing if you see '/*' in your transaction names. If this persists, New Relic may halt the account from creating additional metric names for the service causing the issue.
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Key Actionable Insights
1Group similar metrics together to avoid metric explosion in New Relic.By managing metrics in groups, you can enhance the performance of your New Relic dashboard, making it easier to identify issues and improving overall user experience.
2Monitor transaction names for signs of MGI.Regularly checking for '/*' in transaction names can help you catch potential issues early, allowing for timely adjustments before New Relic takes action.
Common Pitfalls
1
Failing to group metrics can lead to a Metric Grouping Issue, overwhelming the New Relic dashboard.
This happens when services send too many unique metrics, making it difficult to analyze data and identify problems effectively.