Hi @Olu,
I have successfully set NewRelic via Instrumentation, but I wonder if I could get more traces and insights by configuring distributed tracing like explained here.
Thanks
Hi @Olu,
I have successfully set NewRelic via Instrumentation, but I wonder if I could get more traces and insights by configuring distributed tracing like explained here.
Thanks
hi @scelentano and welcome to the community!
is there any specific information you are looking to get from the traces?
In general, I would recommend to wait for our September release. As we will release support for OpenTelemetry and the OpenTelemetry traces will contain much more insights.
Sonja
Hello Team,
Is there any news about the OpenTelemetry September release?
hi! yes - it’s here: OpenTelemetry Integration with Tyk Gateway
Available since Tyk 5.2 - release notes
Just a word of caution: please wait for the 5.2.1 release coming soon to use in production, as we have found (and fixed) a performance issue linked to the OTel support, see here: Increasing memory usage after 5.2 upgrade - #16 by scelentano
UPDATE: 5.2.1 has been released: Tyk Gateway 5.2 Release Notes
Let us know what you think!
Dears,
do you have any other open-source solution that is supported by open telemetry?
As Jaeger is deprecated last July we only have Dynatrace, Datadog, and New Relic which are closed source.
hi @mohamed.hamdy!
Jaeger hasn’t been de-supported, only the Jaeger exporter. I have noticed we need to update our Jaeger documentation.
Here are the information you need:
Jaeger exporter has been deprecated on otel collector v0.85.0 (latest).
If you have your collector config with something like
exporters:
jaeger:
endpoint: jaeger-all-in-one:14250
tls:
insecure: true
you need to replace the exporter type to otlp since Jaeger supports the protocol by default
exporters:
otlp:
endpoint: jaeger-all-in-one:4317
tls:
insecure: true
Hope this help, I will make sure we update our documentation as well!
Sonja