shwetathareja

This is an interesting proposal. We have seen in the past in managed service when customer's cluster experiencing high error rate. They want to know which APIs are impacted and...

Thanks @itiyama for clarifying. @dblock : yes for long term, we should build the metrics framework which publishes event with time to pluggable sink and users can write their consumer...

@dhwanilpatel need a task in here for integ tests as well.

> The details around exact structure of predicate will be published separately as a separate github issue. @RS146BIJAY : We should also explore if the predicate can be deduced from...

Thanks @jainankitk for reporting this issue. Agreed, there are other such APIs like _cluster/stats which also queries ShardStats which can be huge for a large cluster with several 10s of...

Thanks @Bukhtawar for the proposal. I definitely see the value of storing _source field in a data format (considering it is just document blob) which is not bound to lucene...

https://github.com/opensearch-project/OpenSearch/pull/10670#issuecomment-1776629574

Thanks @rlevytskyi for reporting the issue. did you try a heap dump? It will help us debug further here. (You can try with smaller heap, the issue might generate faster...

@CaptainDredge explore _nodes/usage API to expose these API level success and failure count as usage API already provides api count. It would make sense to keep all these counts at...

This would be a breaking change. To start with we can update the OpenSearch documentation to warn users about the implication of sorting on fields with high cardinality including _id....