[Stack Monitoring] [R&D] Document how we store, query, and display shard information #125258
Labels
Feature:Stack Monitoring
R&D
Research and development ticket (not meant to produce code, but to make a decision)
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
There is an ongoing effort to reduce the amount of inefficient queries against Elasticsearch, related to retrieving information about ES shards. Stack Monitoring is one of the biggest callers of these endpoints* and we are aware of the idea that for a long time, we've been retrieving and storing shard information that we may or may not need to power the monitoring UI(s).
We need to document which endpoints we call, which documents/fields we store (related to ES shards), and whether or not we use those in the UI. If we don't, we should log an issue to remove this retrieval and storage. If we do use them, or if we determine that we should keep the retrieval in place for some reason, we should work with the ES team to determine a new API for querying this information.
*Which ES endpoints are the problematic ones we need to look into here?
Acceptance Criteria
Outstanding Questions:
The text was updated successfully, but these errors were encountered: