We automatically place the correlation id into an HTTP header, and the name of this header is elastic-apm-traceparent. By default this should make tracing across services work out of the box.
Now, if you use something where this does not work, because it’s an unsupported technology, then we have an API for that.
Unfortunately that’s all I can say now, but let’s follow up if your question is not answered. If I get more context hopefully I’ll be able to give a more useful answer.
Hi @GregKalapos , yes I read your response for my question. Your apm solution is awesome. I want to tell to you my issue with sample. First sample is working second is not working Why?
Is this some custom property you created? I assume this reads HTTP headers, right? If so, what is the name of the header that this reads? If it's correlationid (as I'd assume that it matches the name of the property) then that is the reason why it does not work - our correlation id is stored in the HTTP header with name elastic-apm-traceparent (but keep in mind this will change in the future).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.