-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Weekly Emails - generating reports is sometimes broken #2472
Comments
oy! who is working on deciphering it? @guyfedwards @foot while @fbarl is on vacation next week |
FYI running the same queries as weekly reporter on our Weave Cloud (Dev) instance notebooks does result in the same errors for the period of last week: https://frontend.dev.weave.works/proud-wind-05/monitor/notebook/931f18f1-5516-4f40-bdd9-a03aa3f24f60?timestamp=2019-01-14T00:00:00Z The same query passes if we shift the window 3 days later (https://frontend.dev.weave.works/proud-wind-05/monitor/notebook/931f18f1-5516-4f40-bdd9-a03aa3f24f60?timestamp=2019-01-17T00:00:00Z), so I wonder if some sort of outage or corrupted data is to blame. In any case, we should probably edit the queries to make them more robust (after we pin down the exact issue). |
Yep, I can have a look on Monday! |
Didn't mean to close this.. |
This seems to be the worst point, where you cannot get a table of first query: https://frontend.dev.weave.works/proud-wind-05/monitor/notebook/39882902-c2f5-4030-af6c-92aeda4f7e1d?timestamp=2019-01-07T18:00:00Z |
I'm not getting very far w/ this. Comparing the @dlespiau any ideas about making this query more robust? We could still roll this out. Some users might not get an error report one week... |
Some more poking around here: https://frontend.dev.weave.works/proud-wind-05/monitor/notebook/ddd09f7e-17e4-4ca2-8017-043d3f463353?range=15m×tamp=2019-01-07T17:42:49Z I can make it work by excluding a particular container ( |
@bboreham any thoughts on where the Error: multiple matches for labels: grouping labels must ensure unique matches message might be coming from in the above notebook? My next step would be to try and dump out that time block into a local prom instance that I could perhaps adds additional debugging code into. I will read about exporting in a bit.. |
Alrighty updated notebook again w/ another variation that works down the very bottom:
Will job always be |
View this after a weekly email run to see if there were any hits: |
Opened an issue in cortexproject/cortex#1245 |
I just tried to generate a report preview in https://frontend.dev.weave.works/admin/users/weeklyreports for our Weave Cloud (Dev) instance and got
{"errors":[{"message":"An internal server error occurred"}]}
in the browser.A closer inspection into the
users
service shows:The error seems to occur with Prometheus queries and points at this line of code: https://github.com/prometheus/prometheus/blob/a1f34bec2e6584a2fee9aec901f3157e3e12cbaa/promql/engine.go#L1498
It probably somehow links to:
service/users/weeklyreports/report.go
Line 47 in 3c32621
The scope of the issue is unclear.
The text was updated successfully, but these errors were encountered: