Invoke external webhook when there are health issues and/or /health
url listener to return HTTP 500 when there are health problems
#1293
ramonsmits
started this conversation in
Ideas
Replies: 1 comment
-
In this example, restarting the container wouldn't achieve anything, right? The "Healthcheck failed" message refers solely to the fact that communication with the Tesla servers is not possible. Be it because your server is offline or because there are problems with the Tesla API. If you want to be notified immediately when this is the case, MQTT could perhaps be an option (topic: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
For some unknown reason, TeslaMate was not able to retrieve car data. I restarted the container which resolved the problem but now I have a 2-day gap in my data. I wish I
On the dashboard it showed "Healthcheck failed" but I wish I was somehow notified by the failing check.
For example, can a query be done at
/health
or/healthcheck
or to invoke a webhook to a service like PushOver to signal any health issues.The original health issue was related to these reoccurring logs:
For example, in release 2.21.2 the token will expire. The health check could return 500 in advance, knowing that the token requires a refresh.
Environment
Beta Was this translation helpful? Give feedback.
All reactions