alerting

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

提问题？
请把问题现象、相关日志、初步排查结果写清楚，即提供尽量多的线索，这样方便我们定位问题。

提建议？
请写明白建议原因，即为何有此建议。

提修复PR？
请说明为何做此修改，需要做好测试。

提Feature？
建议先将想法提出，不着急写代码，与社区同道沟通，大家觉得OK再做代码实现

---

另外，我们是在做开源软件，不是服务于您的企业，做您的乙方，您一分钱没付，就不要颐指气使了，认同我们这个社区，则参与进来，不认同，就不参与，谢谢理解

Please can you add Pushover alerting to gatus (which is great BTW!)

Details on how to send pushover alerts can be found here - https://pushover.net/api

I have managed to get this working using the custom alert, but it's quite clunky and requires encoding the user key, api key, message, etc. in the custom alert body text.

Thanks

Has anyone done this safely?

If we can't open port, then lets do something like:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Addr