Details
-
Bug
-
Status: Closed
-
Medium
-
Resolution: Won't Do
-
Dublin Release
-
None
Description
While working on adding missing filebeat sidecars, it appears that very few of them successfully are delivering the logs to the Logging ELK stack. When running test calls, only search-data-service appeared to reliably be publishing logs.
The filebeat.yml configuration for these pods appears correct to me, so I expect the logs are getting shipped to logstash successfully, but they're getting dropped from there.
NOTE: It's possible this is a broader issue, as other components in my deployment also didn't seem to be publishing their expected logs to the ELK stack either, although I lacked the ability to run test calls to verify this.
Attachments
Issue Links
- blocks
-
LOG-487 LOG Pipeline Integrity: Docker to Filebeat to Logstash to ElasticSearch to Kibana
-
- Closed
-
-
LOG-1041 Dublin pairwise testing for logging/pomba
-
- Closed
-
-
LOG-1042 POMBA 2 of 7 healthchecks failing - see LOG-1018
-
- Closed
-
-
LOG-852 POMBA: Some pods do not ship with filebeat
-
- Closed
-
- relates to
-
LOG-230 Pairwise integration testing - verify single log makes it through ELK into Kibana
-
- Closed
-
-
LOG-707 Logging El-Alto (moved from) Dublin Scope
-
- Closed
-