What metrics would you use to evaluate New Relic's Infrastructure Monitoring feature?

Introduction

Evaluating New Relic's Infrastructure Monitoring feature requires a comprehensive approach to product success metrics. To address this challenge effectively, I'll follow a structured framework that covers core metrics, supporting indicators, and risk factors while considering all key stakeholders. This approach will help us gain a holistic understanding of the feature's performance and impact.

Step 1

Product Context

New Relic's Infrastructure Monitoring is a critical feature within their observability platform, designed to provide real-time insights into the health and performance of an organization's IT infrastructure. This feature allows DevOps teams, SREs, and IT managers to monitor servers, containers, and cloud services across various environments.

Key stakeholders include:

1. DevOps teams: Seeking to maintain system reliability and performance
2. IT managers: Aiming to optimize resource allocation and reduce downtime
3. Business leaders: Focused on ensuring operational efficiency and cost-effectiveness
4. End-users: Expecting consistent, high-quality service delivery

The user flow typically involves:

1. Setting up monitoring agents on infrastructure components
2. Configuring alerts and dashboards
3. Analyzing performance data and trends
4. Troubleshooting issues and optimizing infrastructure

Infrastructure Monitoring fits into New Relic's broader strategy of providing a comprehensive observability platform, enabling customers to have a single source of truth for their entire tech stack. Compared to competitors like Datadog or Dynatrace, New Relic emphasizes ease of use and integration with their full-stack observability suite.

In terms of product lifecycle, Infrastructure Monitoring is in the growth stage. It's a well-established feature but continues to evolve with new capabilities and integrations to meet emerging customer needs.