AWS R3M11: Cloud Watch OS-Search Containers Log Are Not Registered
From R3M11 container insight map, I can see os-search and the relevant metric. However, there are 2 issues observed:
-
When running search API from Postman I dont see any graph spike movement from Network/Memory/CPU metrices shown. During previous test cases in R3M10 and R3M9 those spikes can be observed from the graph metric whenever I run the search API from Postman
-
Checking the related logs and run log query using following sql no logs were captured:
fields @timestamp, @log, @logStream, @message
| filter ispresent(kubernetes.pod_name) and kubernetes.pod_name like /elasticsearch-es-default-0|elasticsearch-es-default-2|os-search-654dd6dc8c-w7rmz|os-search-654dd6dc8c-rjrbz|os-search-654dd6dc8c-bftbr/
| sort @timestamp desc
| limit 50
This only happens for search service API while doing audit trail and log monitoring from osdu-ingest container the logs are clearly visible.
Note: My AWS console is pointing towards US-West1