Symptom
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
In some cases, logs may stop being collected, or nothing might appear after login into the system or the system itself might even become inaccessible. These symptoms may be related to high space usage on disks that store logs.
A lot of metrics can be checked via Dev Tools in OpenSearch:
1. Logs may not be saved due to the high disk space usage:
- below command will show the disk space usage in logging system
| GET _cat/allocation?v&s=node:asc |
Disk space retention policy is 75%, all disks have 100Gb (one disk per elastic-data instance). In the above case the disk space usage is very high on all disks the 75% of disk usage is exceeded. On few disks the space usage increased over 90% which resulted in logs not being saved anymore.
2. Logs may not be visible due to the fact that some indexes are in yellow or red state.
| GET _cat/indices?v&s=index:desc |
The problem may be related to retention or a corrupted indexes.
Read more...
Environment
- SAP Commerce Cloud
- OpenSearch
Product
Keywords
kibana, logging system, logs, disappeared, not visible , KBA , CEC-SCC-CLA-ENV-LOM , Logging and Monitoring , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview