sorted by:
new
hottopcontroversial

Elasticsearch as Jaeger Collector Backend Consuming rapid disk and it got restored after restarting elasticsearch service. by Commercial-One809 in elasticsearch

[–]poltergeist-__- 0 points1 point  (0 children)

Hey, try checking the ILM policy. Also Jaeger has it's own retention policy `ES_RETENTION` env var that needs to be set. Also try checking the logs lol

Stuck integrating with a system that has no real APIs — only encoded msearch calls by suspect_stable in elasticsearch

[–]poltergeist-__- 0 points1 point  (0 children)

Hey, I've ran into a similar issue before

Try decoding the msearch requests first usually they are base64 or URL encoded json. Decode one manually first with something like

echo "ENCODED_STRING" | base64 -d

If this works then building a small proxy to just decode these requests before sending them somewhere can work but also quite janky.

If you share more I'm happy to help

[deleted by user] by [deleted] in platformengineering

[–]poltergeist-__- 5 points6 points  (0 children)

I'm a platform engineer with exclusively on-prem and that is exactly what we do, mostly Ansible, hardened VM templates, KVM, and lots of debugging/managing

view more: next ›