Jaeger: WIll jaeger care about removing old spans?

Created on 16 Apr 2018  路  5Comments  路  Source: jaegertracing/jaeger

My question is: will removing old spans upset any operations of jaeger?

For context: I've been setting up jaeger in production and want to add a curator job for removing old elasticsearch indexes -- I'm just wondering how jaeger will react.

Specifically for elasticsearch: should corresponding span and service entries be removed? Say jaeger-span-2018-03-17, should I also remove jaeger-service-2018-03-17?

PS. I'm not sure if this is the best place to ask this. Let me know if it's not :sweat_smile:

Most helpful comment

This is fine and expected. We even have an existing script that uses curator to purge older data: https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/esCleaner.py

All 5 comments

This is fine and expected. We even have an existing script that uses curator to purge older data: https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/esCleaner.py

@black-adder could you please add a paragraph to the docs about this?

@yurishkuro is the esCleaner docker image built and pushed to the Docker hub? I can't seem to find it under the jaegertracing organization.

@black-adder thanks! Don't know how I missed that.

Was this page helpful?
0 / 5 - 0 ratings