falcon message

falcon-message

open-falcon alarm sends a message component. Note that this is customized based on the im function added in version 2.0.

DingTalk group messaging and WeChat messaging are now implemented

Note that you need to modify the user table in the uic library in mysql and change the size of the im field to 4000 (to prevent DingTalk token overflow and truncation, which will not take effect)

WeChat

You need to configure the WeChat name in the IM configuration in the person list of the address book. Please refer to https://github.com/Yanjunhui/chat for configuration instructions. The code is also copied and pasted from here, and appropriately modified to adapt to the current program.

DingTalk group

1. DingTalk messages are sent to a group, not to a single person, so you need to set up a robot in this group. When defining, select a custom robot, and then copy the value of access_token in the webhook link for later use. use.
2. Create a new user in the falcon dashaboar user management center, fill in the email, and then fill in [ding]:access_token at IM. The access_token here is the access_token above. If the same message is to be sent to multiple robots, use an English semicolon between the access_tokens. ; separated to save user information.
3. Create a new group in the group management center of the dashboard and add the user above to this group.
4. Just add the above group where you want to alert.
5. Modify api in the alarm component and add the configuration: "im": "http://localhost:23329/api/v1/message" . The port is modified according to the configuration file of this project.
6. Just start this project.

template

The default template file is message-template.md , and the parameters that can be used are as follows:

• Alarm level: {{.Level}}
• Alarm type: {{.Type}}
• Alarm indicators: {{.Condition}}
• Alarm host: {{.Endpoint}}
• Alarm time: {{.Time}}
• Alarm description: {{.Desc}}
• Number of times: {{.Count}}
• Number of consecutive times in an expression {{.TriggerCount}}

If the parameter configuration is incorrect, the template rendering will fail and cannot be sent.

The default template has the following expressions:

 {{with elapse .Count 60 .TriggerCount 300}}{{divide . 60}}{{end}}

Among them, 60 is the data reporting period, and the default is 60s. If the default value is modified, the value here needs to be modified.

300 is the delay time between alarms, the default is 5 minutes.

{{divide . 60}} is divided by 60s to get minutes