How to limit file size when using Jaeger-all-in-one and Badger in docker composer

[fernando-viegas]

I have a docker compose file that runs a Jaeger + Badger with disk storage:

services:
  jaeger:
    image: jaegertracing/all-in-one:latest
    container_name: jaeger
    restart: always
    ports:
      - "4317:4317"
      - "16686:16686"
      - "14268:14268"
      - "14269:14269"
      - "14250:14250"
    environment:
      - SPAN_STORAGE_TYPE=badger
      - BADGER_EPHEMERAL=false
      - BADGER_DIRECTORY_VALUE=/badger_data
      - BADGER_DIRECTORY_KEY=/badger_data
      - BADGER_MAINTENANCE_INTERVAL=24h
      - BADGER_SPAN_STORE_TTL=120h
      - BADGER_TRUNCATE=true
    volumes:
      - ./jaeger:/badger_data
    mem_limit: "512M"
    mem_reservation: "512M"

It is mandatory that I set the file size to control disk space. I have searched a lot to find a solution, but no information!

I would really appreciate solutions to solve this problem.

[dosubot[bot]]

Hey there, @fernando-viegas! I'm here to help you with that issue. Let's work together to find a solution while you wait for a human maintainer.

I found a similar unsolved discussion regarding controlling Badger file size in a Jaeger Docker image. You can view it here ^[1].

Regarding your question, the Jaeger documentation does not provide specific guidance on limiting Badger file size directly. However, it does suggest managing storage constraints by setting a time-to-live (TTL) for stored spans, which you are already doing with BADGER_SPAN_STORE_TTL=120h. This approach helps control the amount of data stored by automatically removing older data.

For more precise control over disk usage, you might need to explore Badger's own configuration options or consider using a different storage backend that offers more granular disk usage controls. Unfortunately, specific environment variables or command-line flags for controlling Badger's disk usage in Jaeger are not documented in the available resources.

To continue talking to Dosu, mention @dosu.