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

[New Feature]: Implement module-ballerinax-newrelic extension #41759

Closed
NipunaMadhushan opened this issue Nov 23, 2023 · 0 comments · Fixed by ballerina-platform/module-ballerinax-newrelic#1
Assignees
Labels
Team/Observability Observability in general, Metrics, Tracing & Logging Type/NewFeature

Comments

@NipunaMadhushan
Copy link
Contributor

Description

Currently we doesn't have an extension to directly publish observability data to New Relic. We use our existing extensions ballerinax/prometheus and ballerinax/zipkin to publish observability data to New Relic.

  1. ballerinax/prometheus - Use remote_write_url method to publish metrics to New Relic.
  2. ballerinax/zipkin - Use reporterEndpointURL configuration to set New Relic Trace API

In publishing traces, the Zipkin uses HTTP protocol which is much slower than GRPC protocol. We also converts OpenTelemetry trace data into Zipkin format which is unnecessary since New Relic supports OpenTelemetry format.
In publishing metrics, We use prometheus as an intermediate server which is completely unnecessary while we can publish data directly via their Metric API.

Therefore we need a separate extension for New Relic which publishes both metrics and traces to New Relic.

Describe your problem(s)

No response

Describe your solution(s)

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team/Observability Observability in general, Metrics, Tracing & Logging Type/NewFeature
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants