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
A clear and concise description of what the problem is, e.g. I'm always frustrated when [...].
We can consider tracking the following queries as part of Query Insights:
Queries that error out
Queries that do not complete due to timeout
Its hard for OpenSearch customers to figure out these queries in-case they want to modify them or retry in the future.
Additionally, With this approach when we integrate WLM and QI we can figure out tenants that are running erroneous or rogue queries.
For starters, we can probably enhance slow logs with an errorlogs feature to capture details about queries that error out and in the future think about how QI can help.
However, in QI this might entail keeping track of all the in-progress queries - not sure if we want to do this and if it will be scalable. We can also have a callback to QI on query failure if possible to make this easier.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
A clear and concise description of what the problem is, e.g. I'm always frustrated when [...].
We can consider tracking the following queries as part of Query Insights:
Its hard for OpenSearch customers to figure out these queries in-case they want to modify them or retry in the future.
Additionally, With this approach when we integrate WLM and QI we can figure out tenants that are running erroneous or rogue queries.
For starters, we can probably enhance slow logs with an errorlogs feature to capture details about queries that error out and in the future think about how QI can help.
However, in QI this might entail keeping track of all the in-progress queries - not sure if we want to do this and if it will be scalable. We can also have a callback to QI on query failure if possible to make this easier.
The text was updated successfully, but these errors were encountered: