Does anyone know of a method to identify the fields that are eating up most of the disk space in ES ?
Such information would be very useful to be able to drop the useless fields (which, at the same time are disk space hungry) via a pipeline, thus saving much needed storage.
I havent seen fields fill up storage but I had a client sending every log/event to my graylog server. Messages were reduced from the client side configuration.
How are you ingesting the logs?
This post may have what you need Message size per stream. I’ll note the value is in bytes, but that should help.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.