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
Yeah... that's to be expected 😕 , however, how would you solve this? Simply checking for 127.0.0.1 or localhost is not an answer since someone could a proxy in front and then we would be back to square one. We could print a message at best in such situations, IMHO. Also, Having something like "correlation IDs" on top of the queries would be nice however that would probably incur a heavy performance penalty and bring more harm than good.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Thanos:
0.5.0
go:
go version go1.11.2 darwin/amd64
What happened
If thanos query is added itself as a store then it takes high cpu after running any query.
What you expected to happen
It should give warning about adding self or shouldn't allow adding itself
How to reproduce it (as minimally and precisely as possible):
up
kill -9
Full logs to relevant components
Uncomment if you would like to post collapsible logs:
Anything else we need to know
The text was updated successfully, but these errors were encountered: