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

What happened:

The current preview endpoint (/api/v1/rule/test/<grafana | datasourceUID>) does not return a very structured response that enables us to visualize labels and values during the preview step in the alert creation.

The JSON response below encode this information in a stringified format.

This would enable us to move forward with grafana/grafana#4

Bug Description
fix issues found by Coverity Scan in syncMain.c

To Reproduce
N/A

Expected Behavior
fix following issues:
| issue type | category | file path | function | line number |
| -------------------------- | -------------------------- | -------------------------- | -------------------------- |

示例

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

I am attempting to parse an array.

{
  "servers": [
    {
      "servername": "server1",
      "serveractiveconn": 0,
      "servertotalconn": 20,
      "serverconnections": [],
      "serverssl": 1,
      "serversslinfo": "",
      "serveractive": true,
      "servererror": "",
      "serverpriority": 0,
      "serveroptional": 0,
      "serverbps": "0 "
    },
    {
 

https://github.com/brotandgames/ciao

Btw native integrations are stored here: https://github.com/grafana/oncall/tree/dev/engine/config_integrations

If you use ciao and need templates, please let us know!

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