alerting

Problem

My notification services is not available

Description

ntfy (pronounce: notify) is a simple HTTP-based pub-sub notification service. It allows you to send notifications to your phone or desktop via scripts from any computer, entirely without signup, cost or setup. It's also [open source](https://github.com/b

Currently, in provisioning, we always update structs if they already exist. This introduces some load to the database. In the future, we would like to have a function that compares the internal state with the external state.

• Alert rules
• Contact points
• Templates
• Mute timings

Bug Description
fix issues found by Coverity Scan in TDengine/src/query/src/qFilter.c

To Reproduce
N/A

Expected Behavior
fix following issues:

可以通过在当前 issue 登记您的使用情况，并分享您使用夜莺监控的经验，将会自动进入 END USERS 列表，并获得社区的 VIP Support。

示例

• 企业或者组织: 夜莺
• 地点：北京
• 联系方式：contact-us at xxx.com
• 使用场景和经验分享：你们最看重夜莺的哪些功能，解决一个什么样的问题，以及使用规模和范围，使用夜莺监控构建企业级监控体系的过程中，有哪些好的经验分享。
• 需求建议：希望哪些点上夜莺监控能做的更好，更契合您的使用场景。

Describe the feature request

I'd like to create an alerting provider for binwiederhier/ntfy.

For other examples, see https://github.com/TwiN/gatus/tree/master/alerting/provider

Documentation should also be added in https://github.com/TwiN/gatus/blob/master/README.md#alerting

Here's an example of a similar past pull request: #299

Wh

The codebase seems to be needing some good old search and replace:

{
    "state": "alerting",
    "title": "Webhook heartbeat is missing",
    "message": "Amixr was waiting for a heartbeat from Webhook. Heartbeat is missing. That could happen because Webhook stopped or there are connectivity issues between Amixr and Webhook. Read more in Amixr docs: https://grafana.com/#/integrations/he

Has anyone done this safely?

Today we try to write Robusta actions that can be re-used in multiple scenarios. For example, an action that fetches logs should be usable both in the case of a crashing pod and a prometheus alert.

In the past, we sometimes wrote actions that included triggering logic too. For example, the restart_loop_reporter action is connected to the trigger on_pod_update. This fires very frequently and