3670234 - How to identify which loggers consume the most storage in OpenSearch

It is necessary to determine which OpenSearch logs consume the most storage and to identify the specific loggers responsible for generating them. Removing or reconfiguring non-essential, high-volume or high-footprint loggers can significantly reduce index storage usage.

Existing guidance, such as 3607491 - How to get the doc counts for logger in OpenSearch, describes methods to identify loggers that produce the largest number of log documents. However, the logger with the highest document count is not always the one consuming the most storage. Document size varies by message content (e.g., long stack traces, large structured payloads), so a smaller number of large documents may occupy more space than a larger number of small documents.

Therefore, it is important to measure both:

• the number of documents produced per logger, and
• the aggregate storage footprint of those documents.

This article explains how to determine per-logger document size in order to pinpoint loggers that contribute most to storage consumption.

SAP Commerce Cloud

SAP Commerce Cloud, logging retention, logs storage limit, logs storage, log storage, OpenSearch storage, OpenSearch, storage, logging size, logs size, log size, docs size, doc size, log, docs, doc, size, logging and monitoring, logging, retention policy, excessive loggers, loggers, logger, loggerName, log analysis , KBA , CEC-SCC-CLA-ENV-LOM , Logging and Monitoring , How To