Compose file for elasticsearch+jaeger

[brunolnetto]

I tried to compose elasticsearch and jaeger. The containers sucessfully are up. However, the requests on app hotrod are not registered on jarger UI, and I also receive warning 🛑 WARNING: End-of-life Notice for Jaeger v1. Any help is appreciated

services:
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.9.3
    networks:
      - elastic-jaeger
    ports:
      - "127.0.0.1:9200:9200"
      - "127.0.0.1:9300:9300"
    restart: on-failure
    environment:
      - cluster.name=jaeger-cluster
      - discovery.type=single-node
      - http.host=0.0.0.0
      - transport.host=127.0.0.1
      - ES_JAVA_OPTS=-Xms512m -Xmx512m
      - xpack.security.enabled=false
    volumes:
      - esdata:/usr/share/elasticsearch/data

  jaeger-collector:
    image: jaegertracing/jaeger-collector
    ports:
      - "14269:14269"
      - "14268:14268"
      - "14267:14267"
      - "14250:14250"
      - "9411:9411"
    networks:
      - elastic-jaeger
    restart: on-failure
    environment:
      - SPAN_STORAGE_TYPE=elasticsearch
    command: [
      "--es.server-urls=http://elasticsearch:9200",
      "--es.num-shards=1",
      "--es.num-replicas=0",
      "--log-level=error"
    ]
    depends_on:
      - elasticsearch
    # Use a volume to store Jaeger data (optional)
    volumes:
      - jaeger-data:/jaeger-collector/data

  jaeger-agent:
    image: jaegertracing/jaeger-agent
    hostname: jaeger-agent
    command: ["--reporter.grpc.host-port=jaeger-collector:14250"]
    ports:
      - "5775:5775/udp"
      - "6831:6831/udp"
      - "6832:6832/udp"
      - "5778:5778"
    networks:
      - elastic-jaeger
    restart: on-failure
    environment:
      - SPAN_STORAGE_TYPE=elasticsearch
    depends_on:
      - jaeger-collector

  jaeger-query:
    image: jaegertracing/jaeger-query
    environment:
      - SPAN_STORAGE_TYPE=elasticsearch
      - no_proxy=localhost
    ports:
      - "16686:16686"
      - "16687:16687"
    networks:
      - elastic-jaeger
    restart: on-failure
    command: [
      "--es.server-urls=http://elasticsearch:9200",
      "--span-storage.type=elasticsearch",
      "--log-level=debug"
    ]
    depends_on:
      - jaeger-agent

  hotrod:
    image: jaegertracing/example-hotrod:latest
    ports: 
      - "8080:8080"
    command: ["all"]
    environment:
      - JAEGER_AGENT_HOST=jaeger-agent
      - JAEGER_AGENT_PORT=6831
    networks:
      - elastic-jaeger
    depends_on:
      - jaeger-agent

volumes:
  esdata:
    driver: local
  jaeger-data:
    driver: local

networks:
  elastic-jaeger:
    driver: bridge

[dosubot[bot]]

Hey @brunolnetto! I'm here to help with any issues or questions you have. Let's figure this out together!

I found a similar discussion titled Help? Having trouble under Docker Compose getting trace information from my app into jaeger, which is still open and might provide some insights ^[1].

Regarding the warning 🛑 WARNING: End-of-life Notice for Jaeger v1, this indicates that Jaeger version 1 is deprecated and will reach its end-of-life on December 31st, 2025. It is recommended to migrate to Jaeger v2 for continued support and access to new features ^[2].

For the issue of traces not appearing in the Jaeger UI, here are some steps you can take to troubleshoot:

1. Verify Sampling Strategy: Ensure that the sampling strategy is set to sample every trace. You can set the environment variables JAEGER_SAMPLER_TYPE=const and JAEGER_SAMPLER_PARAM=1 in the hotrod service to ensure all traces are captured.

2. Check Network Configuration: Make sure that the hotrod service can communicate with the jaeger-agent. The JAEGER_AGENT_HOST and JAEGER_AGENT_PORT environment variables seem correctly set, but ensure that the network configuration allows for this communication.

3. Use the Logging Reporter: Enable logging of spans by setting the environment variable JAEGER_REPORTER_LOG_SPANS=true in the hotrod service. This will help verify if spans are being generated and reported.

4. Directly Send Spans to Collector: Consider configuring the hotrod service to send spans directly to the jaeger-collector by setting the JAEGER_ENDPOINT=http://jaeger-collector:14268/api/traces. This can help avoid issues with UDP packet loss.

5. Increase Logging Level: Set the log level to debug for the Jaeger components to get more detailed logs of received and processed spans. This can be done by adjusting the --log-level parameter in the command section of the Jaeger services.

6. Check the /metrics Endpoint: Use the /metrics endpoint of the Jaeger Collector to verify if spans and traces are being received and processed.

These steps should help identify and resolve the issue with traces not appearing in the Jaeger UI.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}