Custom Metrics Stackdriver Adapter vs New Relic Infrastructure

Developers should use this adapter when running Kubernetes workloads on Google Kubernetes Engine (GKE) or other platforms that need to send custom metrics to Stackdriver for centralized monitoring meets developers should use new relic infrastructure when they need comprehensive monitoring for complex, distributed systems, especially in cloud-native or hybrid environments. Here's our take.

Custom Metrics Stackdriver Adapter

Nice Pick

Developers should use this adapter when running Kubernetes workloads on Google Kubernetes Engine (GKE) or other platforms that need to send custom metrics to Stackdriver for centralized monitoring

Pros

• It is particularly useful for applications that expose metrics in Prometheus format but require integration with Google Cloud's tools for dashboards, alerts, and analysis
• Related to: google-kubernetes-engine, prometheus

Cons

• Specific tradeoffs depend on your use case

New Relic Infrastructure

Developers should use New Relic Infrastructure when they need comprehensive monitoring for complex, distributed systems, especially in cloud-native or hybrid environments

Pros

• It is valuable for troubleshooting performance bottlenecks, ensuring high availability, and automating infrastructure management through integrations with tools like Kubernetes, AWS, and Azure
• Related to: new-relic-apm, prometheus

Cons

• Specific tradeoffs depend on your use case

The Verdict

These tools serve different purposes. Custom Metrics Stackdriver Adapter is a tool while New Relic Infrastructure is a platform. We picked Custom Metrics Stackdriver Adapter based on overall popularity, but your choice depends on what you're building.

The Bottom Line

Custom Metrics Stackdriver Adapter wins

Based on overall popularity. Custom Metrics Stackdriver Adapter is more widely used, but New Relic Infrastructure excels in its own space.