Zabbix integration

1. Media type is a transport channel used for sending notifications and alerts in Zabbix. Enter the terminal and download the complete configuration using the following command:
   wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/zabbix/zbx_mediatype_flashcat_v7.yml
   
   
2. Log in to the Zabbix console, select Alert > Media Types, click the Import button in the top right corner, enter the editing page, select the configuration file downloaded above, and click Import to complete the import
3. Return to the Media Types page to see the imported media type. Click the name to enter the editing page, complete the URL, zabbix_url, and HTTPProxy content:
   • URL: the webhook push URL. Paste the integration push URL.
   • zabbix_url: the Zabbix console address. If your console sits behind a Tomcat or NGINX forwarding path, include the path. Flashduty appends parameters such as trigger_id to build alert detail links.
   • HTTPProxy: if your Zabbix server can’t reach Flashduty directly, set this parameter to a proxy address.
   
4. Click Update to save the configuration

​

Step 2: Associate media type with user

1. Log in to the Zabbix console, select Users > Users, select Admin user, select media, select Add to enter the editing window:
   • Type: Select the Flashduty media type created above
   • Send To: Fill in Flashduty
   • Keep other configurations unchanged using default settings
   
2. Click Add button to exit the add media window
3. Click Update button to exit the edit user page

​

Step 3: Create action

1. Click Create action to enter the action editing page
   • Name: Fill in “Send To Flashduty”
2. Select Operations, add notification sending configurations for three scenarios respectively:

• In the Operations configuration item, click Add button to enter the configuration window
• Send to users: Select the user newly created or configured above
• Send only to: Select Flashduty media type
• Keep other configurations as default
• Click Add button to complete this configuration item
• Repeat the above steps to complete the configuration of Recovery operations and Update operations

​

Step 4: Send events to Flashduty

1. Click Actions, you can see the message notification results in the popup
2. Find the Flashduty corresponding log, if the Status is Sent, it means the notification was successful. Otherwise, troubleshoot according to the prompts
3. Return to the integration list. If the integration shows a latest event time, the setup works

​

Version 5.x~6.x

​

Step 1: Define Flashduty Media type

1. Media type is a transport channel used for sending notifications and alerts in Zabbix. Enter the terminal and download the complete configuration using the following command:
   // 5.x version XML configuration:
   wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/zabbix/zbx_mediatype_flashcat_v5.xml
   
   // 6.x version YAML configuration:
   wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/zabbix/zbx_mediatype_flashcat_v6.yml
   
2. Log in to the Zabbix console, select Administration > Media Types, click the Import button in the top right corner, enter the editing page, select the configuration file downloaded above, and click Import to complete the import
3. Return to the Media Types page to see the imported media type. Click the name to enter the editing page, complete the URL, zabbix_url, and HTTPProxy content:
   • URL: the webhook push URL. Paste the integration push URL.
   • zabbix_url: the Zabbix console address. If your console sits behind a Tomcat or NGINX forwarding path, include the path. Flashduty appends parameters such as trigger_id to build alert detail links.
   • HTTPProxy: if your Zabbix server can’t reach Flashduty directly, set this parameter to a proxy address.
   
4. Click Update to save the configuration

​

Step 2: Associate media type with user

1. Log in to the Zabbix console, select Administration > Users, select Admin user, select media, select Add to enter the editing window:
   • Type: Select the Flashduty media type created above
   • Send To: Fill in N/A
   • Keep other configurations unchanged using default settings
   
2. Click Add button to exit the add media window
3. Click Update button to exit the edit user page

​

Step 3: Create action

1. Click Create action to enter the action editing page
   • Name: Fill in “Send To Flashduty”
2. Select Operations, add notification sending configurations for three scenarios respectively:

• In the Operations configuration item, click Add button to enter the configuration window
• Send to users: Select the user newly created or configured above
• Send only to: Select Flashduty media type
• Keep other configurations as default
• Click Add button to complete this configuration item
• Repeat the above steps to complete the configuration of Recovery operations and Update operations

​

Step 4: Send events to Flashduty

1. Click Actions, you can see the message notification results in the popup
2. Find the Flashduty corresponding log, if the Status is Sent, it means the notification was successful. Otherwise, troubleshoot according to the prompts
3. Return to the integration list. If the integration shows a latest event time, the setup works

​

Version 3.x~4.x

​

Step 1: Define Flashduty Media type

1. Log in to the Zabbix console, select Administration > Media Types, click Create media type button in the top right corner to enter the editing page
2. On the editing page, select Script for Type, then add the following parameters in this order. The script reads parameters by position, so don’t change the order, and leave a parameter empty if it has no value:
   • {ALERT.SUBJECT}: Alert title, keep as first parameter
   • {ALERT.MESSAGE}: Alert message, keep as second parameter
   • Flashduty webhook push URL: the integration push URL. Keep it as the third parameter.
   • Zabbix console address: used to build alert detail links. Include the Tomcat or NGINX forwarding path if you use one. Leave it empty if you don’t need links, and keep it as the fourth parameter.
   • HTTPProxy: if your Zabbix server can’t reach Flashduty directly, set this parameter to a proxy address.. Leave empty if none, keep as fifth parameter
   
3. Fill in send-to-flashduty.sh for Script name
4. Click Update to save the configuration
5. Log in to the Zabbix server host, execute the following commands:
   #1. Enter alert script loading directory (specific address configured in Zabbix Server configuration file `AlertScriptsPath` variable, usually `/usr/lib/zabbix/alertscripts`)
   cd /usr/lib/zabbix/alertscripts
   
   #2. Download script
   wget --header="Referer: https://console.flashcat.cloud" https://download.flashcat.cloud/flashduty/integration/zabbix/send-to-flashduty.sh
   
   #3. Change script to executable status
   chmod +x send-to-flashduty.sh
   
6. Note that the script uses curl and jq commands, ensure that the Zabbix server process can find and execute these two commands, if not you need to install them as needed

​

Step 2: Associate media type with user

1. Log in to the Zabbix console, select Administration > Users, select Admin user, select media, select Add to enter the editing window:
   • Type: Select the Flashduty media type created above
   • Send To: Fill in N/A
   • Keep other configurations unchanged using default settings
2. Click Add button to exit the add media window
3. Click Update button to exit the edit user page

​

Step 3: Create action

1. Click Create action to enter the action editing page
   • Name: Fill in “Send To Flashduty”
2. Select Operations, update notification user configurations for three scenarios respectively:
   • In the Operations configuration item, click Add button to enter the configuration window
   • Send to users: Select the user newly created or configured above
   • Send only to: Select Flashduty media type
   • Keep other configurations as default
   • Click Add button to complete this configuration item
   • Repeat the above steps to complete the configuration of Recovery operations and Update operations
3. Select Operations, update notification content configurations for three scenarios respectively:
   • In the Default Message configuration item, completely copy the following content and paste it after the default content. Flashduty will parse corresponding text after receiving events to find alert attribute information:

-----Flashduty Required Starts-----event_severity={TRIGGER.SEVERITY}||event_name={TRIGGER.NAME}||event_id={EVENT.ID}||event_tags={EVENT.TAGS}||event_ack={EVENT.ACK.STATUS}||event_value={EVENT.VALUE}||trigger_id={TRIGGER.ID}||trigger_desc={TRIGGER.DESCRIPTION}||trigger_expr={TRIGGER.EXPRESSION}||host_group={TRIGGER.HOSTGROUP.NAME}||host_ip={HOST.IP}||host_name={HOST.NAME}||item_name={ITEM.NAME}||item_value={ITEM.VALUE}-----Flashduty Required Ends-----

• Repeat the above steps to complete the configuration of Recovery operations and Update operations

​

Step 4: Send events to Flashduty

1. Click Actions, you can see the message notification results in the popup
2. Find the Flashduty corresponding log, if the Status is Sent, it means the notification was successful. Otherwise, troubleshoot according to the prompts
3. Return to the integration list. If the integration shows a latest event time, the setup works

​

Status mapping