Sreevani K V S
Any update on this error. Facing a similar issue.
> Can you try settings es_send_get_body_as from GET to POST in elastalert.yaml file Updated es_send_get_body_as: POST. Still the same error is coming. Error screenshot
Any help here @dbbaughe ? One more issue is with the **delay** field in rollup job configuration, When I configured the job with continuous field set true and delay field...
Encountering OOM issues while fetching traces from jaeger-UI. **Details :** Backend Storage: Elasticsearch Instance RAM: 4 GB(~3.7 GB Free Memory) Instance vCPU:2 We are encountering OOM kill upon fetching 20...
@yurishkuro Any specific reason for fetching all info in **FindTraces** call itself from UI?
> @Sreevani871 yes, we even had tickets somewhere for that, but no volunteers to implement it. Can you share the tickets will have a look?
@yurishkuro Any progress on this?
To overcome frequent OOM kills of jaeger-query service (Due to traces having a large number of spans), we need to avoid fetching of all spans data of respective TopN traces....
Using _json.Unmarshal()_ func instead of _json.Decode()_ func here https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/spanstore/reader.go#L233 shows improvement on memory usage because json.Decode() func is buffering entire json value in memory again. Since here the data passed...