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
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
The queries were genrated by an automated tool. After running the tool again and capturing the queries sent, this was the result (some field-names have been redacted):
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
The queries were genrated by an automated tool. After running the tool again and capturing the queries sent, this was the result (some field-names have been redacted):
The second query is repeated multiple times with difference start/stop times.
These are the the entries in our Nginx reverse-proxy logs:
Expected behavior:
Return queried data.
Actual behavior:
Return a 500 HTTP error code and log a null-reference error
Environment info:
Running in a VM with 80GB of RAM and using about 19TB of time-series data on disk.
Config:
Running with the following command-line:
Logs:
The text was updated successfully, but these errors were encountered: