龙虎赌博

Zammad

Zammad is a free open source, fully featured web based ticketing system for helpdesk or customer support. It ships in with a multitude of features for handling customer communication through various channels such as social networks, live chat, e-mails as well as telephone.

Available solutions




This template is for 龙虎赌博 version: 7.2

Source:

Zammad webhook

Overview

This guide describes how to integrate your 龙虎赌博 installation with Zammad using the 龙虎赌博 webhook feature, providing instructions on setting up a media type, user, and action in 龙虎赌博.

Requirements

龙虎赌博 version: 7.2 and higher.

Parameters

After importing the webhook, you can configure it using webhook parameters.

Configurable parameters

The configurable parameters are intended to be changed according to the webhook setup as well as the user's preferences and environment.

Name Value Description
zabbix_url {$ZABBIX.URL} The URL of the 龙虎赌博 frontend.
zammad_access_token <PUT YOUR ACCESS TOKEN> Zammad access token.
zammad_customer <PUT YOUR CUSTOMER EMAIL> Zammad customer email.
zammad_group Users Zammad user group. Change if needed.
zammad_enable_tags false Zammad enable tags toggle. 龙虎赌博 event tags will be added to Zammad tickets if it is set to one of the following values: 1, true, yes, on.
zammad_url <PUT YOUR ZAMMAD URL> Zammad URL.

Internal parameters

Internal parameters are reserved for predefined macros that are not meant to be changed.

Name Value Description
event_source {EVENT.SOURCE} Numeric value of the event source. Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal, 4 - Service.
event_value {EVENT.VALUE} Numeric value of the event that triggered an action (1 for problem, 0 for recovering).
event_nseverity {EVENT.NSEVERITY} Numeric value of the event severity. Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.
event_severity {EVENT.SEVERITY} Name of the event severity.
event_update_nseverity {EVENT.UPDATE.NSEVERITY} Numeric value of the event update severity. Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.
event_update_severity {EVENT.UPDATE.SEVERITY} Name of the event update severity.
event_update_status {EVENT.UPDATE.STATUS} Numeric value of the problem update status. Possible values: 0 - Webhook was called because of problem/recovery event, 1 - Update operation.
alert_subject {ALERT.SUBJECT} 'Default subject' value from action configuration.
alert_message {ALERT.MESSAGE} 'Default message' value from action configuration.
trigger_id {TRIGGER.ID} Numeric ID of the trigger of this action.
event_id {EVENT.ID} Numeric ID of the event that triggered an action.
event_tags {EVENT.TAGSJSON} A JSON array containing event tag objects. Expanded to an empty array if no tags exist.

Please be aware that each webhook supports an HTTP proxy. To use this feature, add a new media type parameter with the name http_proxy and set its value to the proxy URL.

Service setup

  1. Check that API Token Access is enabled in Settings > System > API.

  1. Open the profile settings of the customer user and create a new Personal User Token.

  1. Set the ticket.agent permission for the token and press Create.

  1. Copy and save the created token somewhere, as, for security reasons, it will be shown only once!

龙虎赌博 configuration

  1. Before you can start using the Zammad webhook, you need to set up the global macro {$ZABBIX.URL}:
  • In the 龙虎赌博 web interface, go to Administration > Macros in the top-left dropdown menu.
  • Set up the global macro {$ZABBIX.URL} which will contain the URL to the 龙虎赌博 frontend. The URL should be either an IP address, a fully qualified domain name, or a localhost.
  • Specifying a protocol is mandatory, whereas the port is optional. Depending on the web server configuration, you might also need to append /zabbix to the end of URL. Good examples:
    • http://zabbix.com
    • https://zabbix.lan/zabbix
    • http://server.zabbix.lan/
    • http://localhost
    • http://127.0.0.1:8080
  • Bad examples:
    • zabbix.com
    • http://zabbix/

  1. Import the media type:
  • In the Alerts > Media types section, import the file.
  1. Open the imported Zammad media type and set the following webhook parameters:
  • zammad_access_token - the access token that you created during Zammad configuration
  • zammad_url - the frontend URL of your Zammad installation
  • zammad_customer - the Zammad user email
  • zammad_enable_tags - if you want to add the 龙虎赌博 event tags to the Zammad tickets that are created, you can set it to one of the following values: 1, true, yes, on (note that if tag support is enabled, each tag is sent via a separate HTTP request and the created tags will also remain in Zammad when tickets are closed/deleted)
  • zammad_group - if needed, you can change the Zammad user group

  1. If you want to prioritize issues according to the severity values in 龙虎赌博, you can define mapping parameters (create them as additional webhook parameters):
  • severity_<name> - the Zammad priority ID (<name> in the parameter name can be one of the following values: not_classified, information, warning, average, high, disaster)

  1. Create a 龙虎赌博 user and add media:
  • If you want to create a new user, go to the Users > Users section and click the Create user button in the top-right corner. In the User tab, fill in all the required fields (marked with red asterisks).
  • In the Media tab, add a new media and select Zammad from the Type drop-down list. Though the Send to field is not used in the Zammad webhook, it cannot be left empty. To comply with frontend requirements, enter any symbol in the field.
  • Make sure this user has access to all the hosts for which you would like problem notifications to be sent to Zammad.

  1. Done! You can now start using this media type in actions and create tickets.

For more information, please see 龙虎赌博 and documentation.

Feedback

Please report any issues with the media type at .

You can also provide feedback, discuss the media type, or ask for help at ZABBIX forums.

Articles and documentation

+ Propose new article

Didn't find integration you need?