jaeger | CNCF Jaeger , a Distributed Tracing Platform | Analytics library

You have to think of a container as an individual minimal host. And in that case, when you say to your ticket_service app to call localhost it will call itself, which is not what we want.

Whenever using docker-compose, a docker network is created and the containers are configured to use it.
You can use that network to make your containers communicate with each other by their names.

In your case, as the Jaeger container is called jaeger, you have to configure the endpoint of your JaegerExporter as follows:

One way would be to use walk.

Assuming $host holds the desired value, the jq filter would be:

The solution I came up with is in parts. My first issue was the casing, I need everything to be in lowercase. So after I appended items to employeeList, I added this code:

I've had a bit more time to dig into this and created this class to overcome the issue:

I did not realize that "?" marks the end of a URL and everything after that are query parameters. Istio provides matching of query parameters as well. The following code worked in my case -

You can always write your own exporter. it should be fairly simple to implement, you can use the console exporter as a template and just write to a file instead of the console.

https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.Console/ConsoleActivityExporter.cs

What you're doing in the docker run command is the following mounting:

${PWD}/local/otel-config.yaml on the local host to /otel-local-config.yaml from inside the docker

You can achieve same behavior with volumes option from docker compose:

volumes:

• "${PWD}/local/otel-config.yaml":/otel-local-config.yaml

The resource attributes to metrics label conversion is disabled by default. Please update the otel config to following to see the resource attribute is prom UI.

As we saw here, jaegar backend interprets OTEL exceptions in way where the contents of the exception are put in as Logs in the associated span.

Now, exceptions are a form of events, and it seems jaegar backend interprets OTEL events as Logs. So we can replicate this behavior by:

1. Creating a custom log appender
2. Inside, create an OTEL event and populate logging details in it.
3. Add the event to the current span.

This span will be interpreted by jaegar backend in a way where all the events are put in as individual log items in that span.

Below is a basic LogAppender i wrote based on SpanLogsAppender.java from the spring-cloud project.