OpenTelemetry offers a versality ecoststem for instrumentation and telemetry, which can be integrated seamlessly with New Relic through the OpenTelemetry Protocol (OTLP). This guide provides an overview of how New Relic processes and ingests OTLP data to help you to efficiently monitor and observe your systems.
Get started
To learn more about integrating OpenTelemetry with New Relic, see Get started with OpenTelemetry and New Relic. This page covers common integration patterns and best practices.
Configure OTLP for New Relic
For detailed OTLP configuration requirements and troubleshooting guidance, visit the following pages:
- New Relic OTLP endpoint walks you through the essential configuration steps for integrating OpenTelemetry data into New Relic.
- New Relic OTLP troubleshooting helps you fix common issues with data ingestion, such as checking logs, API keys, and connection problems.
Signal types in OpenTelemetry
OTLP is divided into trace, metric, and log signals, all of which include the concept of resources. The following pages provide details on how each metric is processed and ingested in New Relic:
- OpenTelemetry traces in New Relic
- OpenTelemetry metrics in New Relic
- OpenTelemetry logs in New Relic
- OpenTelemetry resources in New Relic
Manage data volume
To manage OpenTelemetry data volume and control ingestion costs, see Manage OpenTelemetry data ingest volume. This page covers strategies for optimizing data volume to ensure efficient resource usage.
Use New Relic's platform
Once OpenTelemetry data is ingested into the New Relic platform, you can take advantage of some of these observability tools:
- Alerts: Get informed when a signal exceeds a threshold.
- Custom queries: Write custom NRQL queries for adhoc data analysis and exploration.
- Dashboards: Create custom data visualizations reflecting the unique requirements of your applications.