alerting

Bug description

netdatacli has limit for output size of 4096

Expected behavior

do we just increase this limit or make it transfer arbitrary message sizes?

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 "
    },
    {
 

Go to "Integrations" -> Create new integration with current Grafana -> The link to "contact point" is rendered like a regular text.

@Ukochka could you please check this?

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