[AI Gateway] Add New Relic to common OTEL backends - #33091
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KybsFC28cLtu6pCdwdwBBw
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
|
Should this be here too? https://developers.cloudflare.com/workers/observability/exporting-opentelemetry-data/ |
|
@irvinebroque Good call. New Relic is already in the destinations table on that Workers page (added in #29084), pointing at the same New Relic OTLP docs. It does not have a dedicated "Export to New Relic" guide like the Honeycomb and Sentry pages do. Happy to write one as a follow-up PR if that would be useful. I merged @ethulia @nevikashah whenever one of you has a minute, could you take a look? It is a one-line addition. |
|
@adjohn I approved! Looks like you'll have to rebase with current production again before merging. |
|
@ethulia Thanks! Updated the branch from current production. Both checks are green again, so it should be mergeable now. |
Summary
Adds New Relic to the list of common OTEL backends on the AI Gateway OpenTelemetry integration page. New Relic ingests OTLP natively over HTTP in both JSON and protobuf with an
api-keyheader, so it works with AI Gateway's OTEL exporter as configured on this page. The bullet links to New Relic's OTLP configuration docs, matching the pattern of the Braintrust, Langfuse, and Datadog entries.Documentation checklist