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

• Add .mdx documentation
• Add support for controls

Use Button as an example

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

To Reproduce
Steps to reproduce the behavior:
N/A

Expected Behavior
fix following issues found by Coverity Scan in taosdump.c

1. String not null terminated High TDengine/src/kit/taos-tools/src/benchUtil.c postProceSql
2. Resource leak High TDengine/src/kit/taos-tools/src/taosdump.c parse_json_to_recordschema
   3

示例

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

Describe the bug

See attachment:

What do you see?

Although the hostname got redacted. But the API key in the URI are not.

What do you expect to see?

The whole endpoint should be redacted. Or just add an option

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