So, you've managed to ingest data into New Relic. You've got access to visualizations, began managing your logs, and found and corrected errors with your applications. But where do you go from here? What can you do to help bring everything together? We've compiled a series of tutorials to help you use your data to provide measurable value to your organization that we refer to as Observability maturity practices.
In a nutshell, Observability maturity is about making you successful in one or more of the value drivers shown in the diagram on the above. It aims to identify common customer needs, articulate them, and define a path forward to meet them. These tutorials include use case implementation guides that define KPIs to measure and improve on as well as how to improve them. They also contain reference guides which explain industry concepts in greater detail or cover how to do something, such as improve a specific KPI.
You can use observability practices to create positive business outcomes in many different ways. The progression outlined here represents the typical observability journey, though yours may take a different path depending on your needs. Take a look at our resources to get started and discover which guides can help you make the most improvements using New Relic!
Operational efficiency
The Operational efficiency value driver is about improving and optimizing your observability costs. To meet that goal, you'll want to ensure your you've set up your observability tools and use them efficiently.
- Observability Center of Excellence (OCoE): create a team within your organization that focuses on observability best practices.
- Service characterization (SC): capture the right web telemetry to resolve poor customer experiences.
- Data ingest governance (DG): ensure overall value for the telemetry data you collect with New Relic.
- Observability as code (OaC): automate the configuration of your tools for consistency and value.
Uptime, performance, and reliability
The Uptime, performance, and reliability value driver is about improving reliability. To optimize your observability practice, you'll need to have a strong understanding of the performance of your system and its baseline behavior.
Alert quality management (AQM): manage the volume and usefulness of your alerts.
Service level management (SLM): translate your data into language that all stakeholders can understand.
Reliability engineering diagnostics (RED): diagnose customer-impacting issues more reliably.
Error tracking optimization: improve your error rates, error detection, and overall customer experience.
Self-paced training and labs:
Customer experience
The Customer experience value driver is about improving and optimizing your end user experiences.
Quality foundation (QF): measure and improve the performance of your customers' digital experience.
Bottom-of-the-funnel analysis (BotFA): improve your conversions by focusing on the end of user journey performance.
Related reference docs:
Innovation and growth
The Innovation and growth value driver is about setting up processes to ensure you're consistently improving your observability practices.
- Development quality: improve the quality of your code base.
- Release quality: improve the quality of your releases.