After you send OpenTelemetry data to New Relic, you can use a variety of UI pages to analyze it. Take a look at these options:
- Find entities and data: Find your entities and drill in to the most relevant data
- Summary: See overall service health and begin troubleshooting
- Distributed tracing: Follow requests through your distributed system that involve this service
- Transactions: Tune performance of requests to a service's endpoints and diagnose latency problems
- Databases: Monitor your database calls
- External services: See how requests between your service and others are performing, down to the endpoints involved
- JVMs: Monitor your JVM performance
- Logs: Diagnose problems with application logs
- Errors page: See which errors users of your service are experiencing
- Errors inbox: Triage and resolve errors
- Metrics explorer: Look at specific metrics
- Create custom queries: Try out these do-it-yourself tools to drill into your data
- Events: Query the events emitted by your application
Conventions for OpenTelemetry data
The OpenTelemetry project specifies semantic conventions for metrics, traces, logs and events so that telemetry can be interpreted consistently by observability tools. New Relic relies on these conventions to present telemetry data in the UI.
OpenTelemetry auto-instrumentation agents and SDKs generally follow the semantic conventions, but as the project is in rapid development, it's possible you may have to adjust your instrumentation to match the conventions.
If data is not showing up how you'd expect in the UI, look in the relevant UI page's documentation, where you can find a reference for the semantic conventions used on that page.