jaegertracing / jaeger

CNCF Jaeger, a Distributed Tracing Platform
https://www.jaegertracing.io/
Apache License 2.0
20.41k stars 2.44k forks source link

[Q]: The es index is too large created by jaeger each index 200G+ #4376

Closed yunduansing closed 1 year ago

yunduansing commented 1 year ago

What happened?

It will create an huge index everyday (200G+,we have 8 services)

Steps to reproduce

once.Do(func() { exp, err := jaeger.New(jaeger.WithCollectorEndpoint(jaeger.WithEndpoint(url))) if err != nil { applog.Error("jaeger init fail:", err.Error()) return } otel.SetTracerProvider(tracesdk.NewTracerProvider( // Always be sure to batch in production. tracesdk.WithBatcher(exp, tracesdk.WithBatchTimeout(time.Second)), // Record information about this application in an Resource. tracesdk.WithResource(resource.NewWithAttributes( semconv.SchemaURL, semconv.ServiceNameKey.String(name), )), )) })

Expected behavior

How to change it ?

Relevant log output

No response

Screenshot

No response

Additional context

No response

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

No response

yurishkuro commented 1 year ago

you can use ILM to control for the size of the index https://www.jaegertracing.io/docs/1.43/deployment/#elasticsearch-ilm-support