Troubleshooting Missing Filebeat Logs for Notification Service

🧩 Problem Overview If logs for the notification service are not appearing in the diagnostics dashboard , it may indicate an issue with the Filebeat pods or Elasticsearch ingestion settings. 📌 Symptoms ❌ No logs visible in the diagnostics dashboard for more than 24 hours 📉 Gaps in log entries specifically for the notification service ✅ Root Cause The issue was traced back to Elasticsearch rejecting logs due to request body size limits . Filebeat was attempting to push log entries that exceeded the default HTTP request size accepted by Elasticsearch. 🛠 Resolution The issue was resolved by updating the Elasticsearch pod configuration: Environment Variable Added:

• name: "http.max_content_length" value: "200mb" This change increased the maximum allowed HTTP content length for Elasticsearch requests to 200MB, which allowed larger log entries to be ingested successfully.