We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When adding more than one graph on the /graph page, only the first one is stored in the URL. Also, when trying to open a URL like http://localhost:9090/graph?g0.range_input=1h&g0.expr=rate(node_cpu%5B1m%5D)&g0.tab=0&g1.range_input=1h&g1.expr=rate(http_request_duration_microseconds_count%5B1m%5D)&g1.tab=0, the second entry is halfway rendered, but not executed (and disappears from the URL).
/graph
According to git bisect this regression was introduced by a8ff643. @lovisas would you be able to take a look?
git bisect
The text was updated successfully, but these errors were encountered:
The bug (at least trying to open the link above) only seems to happen when "Search query history" is enabled.
Sorry, something went wrong.
Yes will do!
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Successfully merging a pull request may close this issue.
When adding more than one graph on the
/graph
page, only the first one is stored in the URL. Also, when trying to open a URL like http://localhost:9090/graph?g0.range_input=1h&g0.expr=rate(node_cpu%5B1m%5D)&g0.tab=0&g1.range_input=1h&g1.expr=rate(http_request_duration_microseconds_count%5B1m%5D)&g1.tab=0, the second entry is halfway rendered, but not executed (and disappears from the URL).According to
git bisect
this regression was introduced by a8ff643. @lovisas would you be able to take a look?The text was updated successfully, but these errors were encountered: