You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
ballerinax/prometheus - Use remote_write_url method to publish metrics to New Relic.
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
The text was updated successfully, but these errors were encountered:
Description
Currently we doesn't have an extension to directly publish observability data to New Relic. We use our existing extensions
ballerinax/prometheus
andballerinax/zipkin
to publish observability data to New Relic.remote_write_url
method to publish metrics to New Relic.reporterEndpointURL
configuration to set New RelicTrace API
In publishing traces, the Zipkin uses
HTTP
protocol which is much slower thanGRPC
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
The text was updated successfully, but these errors were encountered: