1 Answer
- Newest
- Most votes
- Most comments
1
Hello,
On checking the link which you have shared as per my understanding the solution cannot be implemented in case of AWS OpenSearch service. This is because in start sniffing step I can see the instructions of installing Packetbeat to the nodes of production cluster which is unfortunately not possible due to managed nature of OpenSearch service.
Unfortunately, other than slow logs currently I do not see any other AWS recommended solution for monitoring slow queries. There are metrics like searchLatency in cloudwatch metrics which in combination of slow logs may help.
[+] Monitoring OpenSearch cluster metrics with Amazon CloudWatch - https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-cloudwatchmetrics.html
Relevant content
- asked 9 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 10 months ago
Thank you. This was my suspicion as well. I might look into feasibility of adding some instrumentation on the client side and/or sending requests through a proxy server where I could install packetbeat.