Jaeger Intake on Elastic Cloud

[graphaelli]

The APM 7.6.0 release introduced jaeger intake support, except on Elastic Cloud.

Subscribe to this issue to receive notification when that is available.

[pieterhumphrey]

@graphaelli Is this the case for both ESS and ECE/ECK?

[graphaelli]

This is the case for both ESS and ECE currently. It is possible to ingest the Jaeger events through apm-server under ECK.

[pieterhumphrey]

Thanks @graphaelli !

[vmarchaud]

Any news ?

[axw]

No updates yet I'm afraid. We will make sure to update the issue when there's something to share.

[LukasTomalla]

Any news/roadmap for supporting Elastic Cloud?

[cmario]

Hi team, would be really great to know if there are any progresses or at least any plan, just to have an idea on when more or less we could expect something.

Thank you
Best,
Mario

[axw]

Apologies for the radio silence. The latest news is that we have been investigating serving both the Elastic APM Agent HTTP protocol and Jaeger gRPC protocol on the same port: elastic/apm-server#3984. The idea behind that is primarily to simplify support for Jaeger on Elastic Cloud.

We've more or less confirmed that this is possible, we now need to prioritise the work. At the moment I cannot comment on when we can expect it to be available, but it won't be before APM Server 7.11 is released.

[wtrTom]

Is there a further update on this now 7.11 has been released?

[graphaelli]

There is no update at this time but we expect to have news on this soon.

[graphaelli]

As a number of users have discovered already, OpenTelemetry and Jaeger are both accepted by APM on Elastic Cloud. We're still tuning configs and updating docs to ensure a good experience but those watching this issue are welcome to give it a spin and report back with results.

[nayan81]

HI Team,
what type of intake span format apm-server is supporting. Does it support zipkin span format.

[axw]

@nayan81 we support the Jaeger protobuf format (gRPC). We do currently also have support for Jaeger Thrift, but not on Elastic Cloud, and that is deprecated and will be removed in a future release. We do not support the Zipkin span format.

[shahargl]

Any estimation on when Jaeger will be supported on Elastic Cloud?

[axw]

@shahargl see #212 (comment): both OpenTelemetry and Jaeger are now accepted in Elastic Cloud. For Jaeger, only the gRPC protocol is supported.

Probably the simplest way to get things working is to run jaeger-agent locally and point it at the APM Server running in your deployment. You can do this by passing the following flags to jaeger-agent:

• --reporter.grpc.host-port=<apm-server-host:8200>
• --reporter.grpc.tls.enabled
• --agent.tags="elastic-apm-auth=Bearer <secret-token>"

[axw]

With the release of 7.13, support for Jaeger (and OTLP) over gRPC are now available in Elastic Cloud.

The docs at https://www.elastic.co/guide/en/apm/server/current/jaeger.html are a little out of date -- we'll update them soon. You don't need to configure apm-server; you can point Jaeger at the server's main port. You will need to set an agent tag in jaeger-agent in order to send Jaeger data to APM Server running in Elastic Cloud, using the deployment's secret token. See #212 (comment) above for instructions.

If you have any feedback or questions about this or any other feature, please create a topic at https://discuss.elastic.co/c/apm. Thanks for your patience!

[Aaronontheweb]

FYI, I am having no success getting agent.tags to propagate my Elastic Cloud bearer token correctly - I filed an issue on the Jaeger project but someone on the Elastic team might want to take a look jaegertracing/jaeger#3351