legacy endpoint 400s metric queries #1541
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fix short-circuits metric queries to the legacy
/api/prom/query
endpoint. Previously it would return 5xx status codes and now it 400s upon seeing metric queries. As a small optimization it doesn't actually run the query anymore either./api/prom/query
handler would not handle POST requests./api/prom/query
route incorrectly 500s when passed a metric query #1537Examples
Allows regular log queries
Fails metric queries