In this guide, we’ll show you how you can build up your advanced application performance monitoring skills. You’ll gain a better understanding of the features of APM—which is now found within our Full-Stack Observability offering—and how these can benefit your business.
We will examine best practices through three stages of the APM maturity curve:
- Early stage
- Stability stage
- Innovation stage
As a note, the tips and tricks found in this article are summarized from our recently published white paper. Let’s get started.
Understanding the APM maturity curve
If you already know the basics of APM, it’s time to focus your efforts on areas that’ll drive real results for your team and organization.
Our APM capability offers the most comprehensive instrumentation available on the market, allowing you to configure deep, customized error and tracing analytics and flexible instrumentation solutions.
Getting the most out of APM is a gradual learning process. We’ve organized the information in this guide into three stages:
- Early stage: Quick-win areas that you can act on immediately.
- Stability stage: Practices that help you further strengthen your overall visibility.
- Innovation stage: Put everything you’ve learned together to tailor your experience through dashboards, instrumentation, and more.
Mastering application performance monitoring: early stage
Tip 1: Improve Performance with APM Transactions
The APM transactions overview page allows you to identify transactions that could be improved or optimized. On the page, you’ll find the following information about the selected app:
- Transaction requests
- Top transactions by percent of wall-clock time
- Relevant throughput (requests per minute)
For non-web transactions (such as message processing, background tasks, and other processes and jobs that do not handle web requests), the transaction page gives an overview of CPU and memory usage.
Tip 2: Identify and Troubleshoot App Errors
An accurate overview of errors allows teams to focus their efforts to resolve issues faster. The New Relic APM error analytics feature automatically groups errors by class. You can apply filters manually to identify specific underlying problems or patterns that are causing recurring performance dips.
Tip 3: Understand Connections and Dependencies
Using APM Service Maps, you can view a quick snapshot of your app architecture, including connections and dependencies. You can then use this information to troubleshoot issues between services.
Service Maps are particularly useful for apps and services that are:
- Closely monitored: apps your team are most interested in
- Central: apps with a lot of connections
- High-traffic: apps with the highest throughput
Mastering application performance monitoring: stability stage
Tip 1: Catch Problems Fast
With Alerts, you can access full-stack alerting over your application environment. This helps you resolve issues before they become critical. You can also set up policies relating to the metrics that are most meaningful to your organization.
Tip 2: Keep Watch on Your Most Important Transactions
New Relic APM allows you to identify any transaction as a key transaction. Key transactions have a custom level of monitoring and can be designated their own alert policy.
Tip 3: Diagnose Errors in Distributed Systems
With distributed tracing, you can track the path of every request through your microservices. You can follow the chain of events from start to finish, pinpointing the latency of the full request and identifying the steps that could create a bottleneck.
Mastering application performance monitoring: innovation stage
Tip 1: Track Real-Time Performance
Software deployments are risky, especially if you don’t have complete visibility over the changes they instigate. With New Relic deployment markers, you can see how the performance of your software ebbs and flows following a deployment. If issues arise, you can respond quickly and effectively.
Tip 2: Uncover Bottlenecks in Production
New Relic’s low-impact production thread profiler collects stack traces during a specified time period and aggregates and displays them in a call tree. From there, you can undertake a fine-grained diagnosis to uncover the bottlenecks limiting your production performance.
Tip 3: Custom Instrumentation
Using custom instrumentation, you can get detail into facets of your code that aren't automatically captured by APM. Custom instrumentation is effective when:
- Ignoring a select transaction that you don’t want to be instrumented
- Adding custom attributes to transactions for quicker troubleshooting
Tip 4: Flexible Dashboards
New Relic One dashboards make it easy to mix and match data from across the platform to build customized, user-friendly, interactive visualizations. This allows you to grasp the state of your system and application in real time with one easy view.
Hopefully, you now feel more confident in mastering Application Performance Monitoring with New Relic. Check out the full white paper or head to the New Relic Explorers Hub. If you’re brand-new to New Relic, sign up for your free account to see the platform in action today.
The views expressed on this blog are those of the author and do not necessarily reflect the views of New Relic. Any solutions offered by the author are environment-specific and not part of the commercial solutions or support offered by New Relic. Please join us exclusively at the Explorers Hub (discuss.newrelic.com) for questions and support related to this blog post. This blog may contain links to content on third-party sites. By providing such links, New Relic does not adopt, guarantee, approve or endorse the information, views or products available on such sites.