-
Notifications
You must be signed in to change notification settings - Fork 126
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
Monitor stop working after some time #11
Comments
Hi, is that the full stack trace? It doesn't have the error which would help a lot to debug the issue. Thanks |
Hi, This error keeps repeating over and over so I thought it was the full stack trace. I will try to go back further and see if there is an error on top of the logs. |
Ah you were right ! There is a top level error:
So it seems one of my service returns HTML content as a 401 error. Would you see it should be fixed upstream of this should be handled by |
Seems like you don’t use the API key or have set the wrong one |
As @craftbyte pointed out, its an authentication failure for the Cachet API.
I think this should be caught by |
I will take a look at this API key but what worries me is that it worked fine for a while |
It did because it didn’t contact the API until an incident happened. This won’t happen once we release the email notifications for cachet-monitor. Best, |
It successfully reported some incidents before. Thanks for your help, I'll try to keep this issue up to date if I manage to make it work. |
Ok my bad... Sorry for the troubles for nothing ! Thanks a lot again |
Hi !
I was using cachet-monitor for about a day or so and noticed that is wasn't properly reporting incident to Cachet.
When I looked at the logs, here what I found:
Does it mean anything to you?
My configuration contains around 7 endpoints to check so maybe that doesn't help (Maybe I should have more than one instance of the monitor I mean)
Thanks,
Aurélien
The text was updated successfully, but these errors were encountered: