Is your feature request related to a problem? Please describe.
Currently we using three different backpressure mechanisms to reject write requests from users [Shard Indexing backpressure, Segment Replication backpressure, Remote Storage backpressure]. And we have three different API's to fetch the metrics related to each mechanism individually.
With the consolidating of all backpressure metrics in one place like node/_stats it would be easy for the user to just call one API to know why write requests are getting rejected instead of calling each backpressure mechanisms API individually.
This will not replace existing backpressure mechanisms individual API as those are needed for more deep level granular details.
Describe the solution you'd like
Combine the backpressure rejection stats and put it in _node/stats API.
ashking94
commented
1 year ago
Is your feature request related to a problem? Please describe. Currently we using three different backpressure mechanisms to reject write requests from users [Shard Indexing backpressure, Segment Replication backpressure, Remote Storage backpressure]. And we have three different API's to fetch the metrics related to each mechanism individually.
With the consolidating of all backpressure metrics in one place like node/_stats it would be easy for the user to just call one API to know why write requests are getting rejected instead of calling each backpressure mechanisms API individually.
This will not replace existing backpressure mechanisms individual API as those are needed for more deep level granular details.
Describe the solution you'd like Combine the backpressure rejection stats and put it in _node/stats API.
Describe alternatives you've considered NA
Additional context No