-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Improve coverage of aggregations by circuit breakers #88373
Copy link
Copy link
Closed
Labels
:Analytics/AggregationsAggregationsAggregations>enhancementSupportabilityImprove our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Team:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)
Metadata
Metadata
Assignees
Labels
:Analytics/AggregationsAggregationsAggregations>enhancementSupportabilityImprove our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Team:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)
Type
Fields
Give feedbackNo fields configured for issues without a type.
Our recent discussions about supportability identified that improving the coverage of aggregations by the circuit breaker framework would help a significant proportion of users help themselves without needing to escalate questions to the support or development teams. We did not go into much depth on what that might mean in practice, but I'm opening this issue to record the need for further discussions in this area. Feel free to take this issue forwards as you see fit, for instance by filling it out into a full meta-issue or by closing it in favour of some other more specific action items.