Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new OTEL reference architecture diagram #6553

Merged
merged 6 commits into from Mar 11, 2022
Merged
Show file tree
Hide file tree
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Expand Up @@ -185,7 +185,7 @@ one–and only one–that best fits your needs.

New Relic supports the native OpenTelemetry Protocol (OTLP) for exporting telemetry data. This allows you to use the vendor neutral components developed by the OpenTelemetry community to export your data to New Relic.

The following tables show the supported features for each telemetry signal. If you have questions about these or have an unsupported use case, please contact us in our [CNCF Slack channel](https://cloud-native.slack.com/archives/C024DRQ63UP), and watch this page for future updates.
The tables in the sections below show the supported features for each telemetry signal. If you have any questions about details in the sections below or unsupported use cases, please contact us in our [CNCF Slack channel](https://cloud-native.slack.com/archives/C024DRQ63UP), and watch this page for future updates. If you prefer to get the big picture of an implementation with New Relic, see our [reference architecture](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-ref-architecture).

<Callout variant="important">
[New Relic's exporters](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-legacy-new-relic-exporters) for OpenTelemetry are now deprecated in favor of exporting data to New Relic using OTLP.
Expand Down
@@ -0,0 +1,24 @@
---
title: Reference architecture for OpenTelemetry with New Relic
tags:
- Integrations
- Open source telemetry integrations
- OpenTelemetry
metaDescription: Use this OpenTelemetry reference architecture to discuss implementation with your team.
---
If you need guidance implementing OpenTelemetry with New Relic One, this reference architecture should help your software developers, DevOps, enterprise architects, and technology managers collaborate on the project. It is a template showing a bird's-eye view of common ways to implement OpenTelemetry with New Relic.

The diagram shows a New Relic One implementation that ingests telemetry from OpenTelemetry, Prometheus, Jaeger, and a New Relic APM agent. The three services (A, B, and C) are instrumented to send metrics, traces, and logs.
rhetoric101 marked this conversation as resolved.
Show resolved Hide resolved

For data collected by OpenTelemetry, you can either send it directly to New Relic via the OTLP endpoint, or you can send it first to an optional OpenTelemetry collector. If you use the collector, it aggregates and enhances data pipelines before the telemetry is sent over to back-ends (Kafka for data analytics and New Relic One for end-to-end observability).

Click on the diagram to enlarge it:

![Diagram showing a reference architecture for OpenTelemetry and New Relic One](./images/otel-ref-arch.png "Diagram showing a reference architecture for OpenTelemetry and New Relic One")


What's next?

* If you need more details about how OpenTelemetry works with New Relic, see our [best practices](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-concepts).
* To begin your setup, see our [quick start](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-quick-start).

2 changes: 2 additions & 0 deletions src/nav/integrations.yml
Expand Up @@ -15,6 +15,8 @@ pages:
path: /docs/more-integrations/open-source-telemetry-integrations/opentelemetry/view-your-opentelemetry-data-new-relic
- title: Best practices
path: /docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-concepts
- title: Reference architecture
path: /docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-ref-architecture
- title: Troubleshooting
path: /docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-troubleshooting
- title: Legacy New Relic Exporters
Expand Down