You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current APM integration in the operator does track requests to Elasticsearch but it does not track requests made to the Kubernetes API server.
#5450 uncovered that we do too many unnecessary requests to the API server. Part of the problem why this went unnoticed is that gap in our observation of the operator. Adding this capability to the operator creates the necessary visibility that will allow us to set up automated alerts if the number of requests goes above a baseline for individual test cases we run (e.g. a ES cluster creation).
The text was updated successfully, but these errors were encountered:
The current APM integration in the operator does track requests to Elasticsearch but it does not track requests made to the Kubernetes API server.
#5450 uncovered that we do too many unnecessary requests to the API server. Part of the problem why this went unnoticed is that gap in our observation of the operator. Adding this capability to the operator creates the necessary visibility that will allow us to set up automated alerts if the number of requests goes above a baseline for individual test cases we run (e.g. a ES cluster creation).
The text was updated successfully, but these errors were encountered: