SolarWinds Service Desk webhook

This guide describes how to integrate Zabbix 7.0 installation with SolarWinds Service Desk using the Zabbix webhook feature. This guide provides instructions on setting up a media type, a user and an action in Zabbix.
Please note that recovery and update operations and SolarWinds Service Desk's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

1. Before setting up a SolarWinds Service Desk Webhook, it is recommended to setup the global macro "{$ZABBIX.URL}" containing an URL to the Zabbix frontend.
As an example, this macro can be used to populate SolarWinds Service Desk's custom field with URL to an event info or graph.

2. In the Administration > Media types section, import the media_solarwinds_servicedesk.yaml.

3. Open the newly added SolarWinds Service Desk media type and replace all <PLACEHOLDERS> with your values.
The following parameters are required:
samanage_url - actual URL of your SolarWinds Service Desk instance,
samanage_token - API token (see SolarWinds Service Desk tutorial for more information).

4. You can add the following parameters to customize SolarWinds Service Desk ticket:

• priority_<severity>: add this parameter for each Zabbix's severity or use only priority_default.
  priority_default is mandatary.
  Possible values of <severity>:

  • not_classified
  • information
  • warning
  • average
  • high
  • disaster

• sw_field_<fieldname>: add this to fill default SolarWinds Service Desk fields, where <fieldname> is a name of a field. The parameter can contain a simple value or a JSON string.
  Name of the field and value should be consistent with SolarWinds Service Desk API specification.
  Example:
  
  Be careful to use user macro as a value, because special symbols such as quotes can make your JSON invalid.
  

• sw_customfield_<fieldname>: add this to fill preconfigured SolarWinds Service Desk custom field. <fieldname> is a name of a field and may contain whitespaces.
  Example:
  
  

5. Create a Zabbix user and add Media with the SolarWinds Service Desk media type. Though a "Send to" field is not used in SolarWinds Service Desk webhook, it cannot be empty. To comply with frontend requirements, you can put any symbol there. Make sure this user has access to all hosts for which you would like problem notifications to be converted into SolarWinds Service Desk tickets.

For more information see Zabbix and SOLARWINDS documentations.

Supported Versions

Zabbix 7.0

SolarWinds Service Desk webhook

Overview

This guide describes how to integrate Zabbix 7.0 installation with SolarWinds Service Desk using the Zabbix webhook feature. This guide provides instructions on setting up a media type, a user and an action in Zabbix. Please note that recovery and update operations and SolarWinds Service Desk's custom fields are supported only for trigger-based events.

Requirements

Zabbix version: 7.0 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.

Internal parameters

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

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

Refer to the vendor documentation.

Zabbix configuration

1. Before setting up a SolarWinds Service Desk Webhook, it is recommended to setup the global macro "{$ZABBIX.URL}" containing an URL to the Zabbix frontend. As an example, this macro can be used to populate SolarWinds Service Desk's custom field with URL to an event info or graph.

2. In the Administration > Media types section, import the media_solarwinds_servicedesk.yaml.

3. Open the newly added SolarWinds Service Desk media type and replace all <PLACEHOLDERS> with your values. The following parameters are required: samanage_url - actual URL of your SolarWinds Service Desk instance, samanage_token - API token (see SolarWinds Service Desk tutorial for more information).

4. You can add the following parameters to customize SolarWinds Service Desk ticket:

• priority_<severity>: add this parameter for each Zabbix's severity or use only priority_default. priority_default is mandatary. Possible values of <severity>:

  • not_classified
  • information
  • warning
  • average
  • high
  • disaster

• sw_field_<fieldname>: add this to fill default SolarWinds Service Desk fields, where <fieldname> is a name of a field. The parameter can contain a simple value or a JSON string. Name of the field and value should be consistent with SolarWinds Service Desk API specification. Example: Be careful to use user macro as a value, because special symbols such as quotes can make your JSON invalid.

• sw_customfield_<fieldname>: add this to fill preconfigured SolarWinds Service Desk custom field. <fieldname> is a name of a field and may contain whitespaces. Example:

5. Create a Zabbix user and add Media with the SolarWinds Service Desk media type. Though a "Send to" field is not used in SolarWinds Service Desk webhook, it cannot be empty. To comply with frontend requirements, you can put any symbol there. Make sure this user has access to all hosts for which you would like problem notifications to be converted into SolarWinds Service Desk tickets.

For more information see Zabbix and SOLARWINDS documentations.

Feedback

Please report any issues with the media type at https://support.zabbix.com.

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

SolarWinds Service Desk webhook

This guide describes how to integrate Zabbix 6.2 installation with SolarWinds Service Desk using the Zabbix webhook feature. This guide provides instructions on setting up a media type, a user and an action in Zabbix.
Please note that recovery and update operations and SolarWinds Service Desk's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

1. Before setting up a SolarWinds Service Desk Webhook, it is recommended to setup the global macro "{$ZABBIX.URL}" containing an URL to the Zabbix frontend.
As an example, this macro can be used to populate SolarWinds Service Desk's custom field with URL to an event info or graph.

2. In the Administration > Media types section, import the media_solarwinds_servicedesk.yaml.

3. Open the newly added SolarWinds Service Desk media type and replace all <PLACEHOLDERS> with your values.
The following parameters are required:
samanage_url - actual URL of your SolarWinds Service Desk instance,
samanage_token - API token (see SolarWinds Service Desk tutorial for more information).

4. You can add the following parameters to customize SolarWinds Service Desk ticket:

• priority_<severity>: add this parameter for each Zabbix's severity or use only priority_default.
  priority_default is mandatary.
  Possible values of <severity>:

  • not_classified
  • information
  • warning
  • average
  • high
  • disaster

• sw_field_<fieldname>: add this to fill default SolarWinds Service Desk fields, where <fieldname> is a name of a field. The parameter can contain a simple value or a JSON string.
  Name of the field and value should be consistent with SolarWinds Service Desk API specification.
  Example:
  
  Be careful to use user macro as a value, because special symbols such as quotes can make your JSON invalid.
  

• sw_customfield_<fieldname>: add this to fill preconfigured SolarWinds Service Desk custom field. <fieldname> is a name of a field and may contain whitespaces.
  Example:
  
  

5. Create a Zabbix user and add Media with the SolarWinds Service Desk media type. Though a "Send to" field is not used in SolarWinds Service Desk webhook, it cannot be empty. To comply with frontend requirements, you can put any symbol there. Make sure this user has access to all hosts for which you would like problem notifications to be converted into SolarWinds Service Desk tickets.

For more information see Zabbix and SOLARWINDS documentations.

Supported Versions

Zabbix 6.2

SolarWinds Service Desk webhook

This guide describes how to integrate Zabbix 6.2 installation with SolarWinds Service Desk using the Zabbix webhook feature. This guide provides instructions on setting up a media type, a user and an action in Zabbix.
Please note that recovery and update operations and SolarWinds Service Desk's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

1. Before setting up a SolarWinds Service Desk Webhook, it is recommended to setup the global macro "{$ZABBIX.URL}" containing an URL to the Zabbix frontend.
As an example, this macro can be used to populate SolarWinds Service Desk's custom field with URL to an event info or graph.

2. In the Administration > Media types section, import the media_solarwinds_servicedesk.yaml.

3. Open the newly added SolarWinds Service Desk media type and replace all <PLACEHOLDERS> with your values.
The following parameters are required:
samanage_url - actual URL of your SolarWinds Service Desk instance,
samanage_token - API token (see SolarWinds Service Desk tutorial for more information).

4. You can add the following parameters to customize SolarWinds Service Desk ticket:

• priority_<severity>: add this parameter for each Zabbix's severity or use only priority_default.
  priority_default is mandatary.
  Possible values of <severity>:

  • not_classified
  • information
  • warning
  • average
  • high
  • disaster

• sw_field_<fieldname>: add this to fill default SolarWinds Service Desk fields, where <fieldname> is a name of a field. The parameter can contain a simple value or a JSON string.
  Name of the field and value should be consistent with SolarWinds Service Desk API specification.
  Example:
  
  Be careful to use user macro as a value, because special symbols such as quotes can make your JSON invalid.
  

• sw_customfield_<fieldname>: add this to fill preconfigured SolarWinds Service Desk custom field. <fieldname> is a name of a field and may contain whitespaces.
  Example:
  
  

5. Create a Zabbix user and add Media with the SolarWinds Service Desk media type. Though a "Send to" field is not used in SolarWinds Service Desk webhook, it cannot be empty. To comply with frontend requirements, you can put any symbol there. Make sure this user has access to all hosts for which you would like problem notifications to be converted into SolarWinds Service Desk tickets.

For more information see Zabbix and SOLARWINDS documentations.

Supported Versions

Zabbix 6.2

SolarWinds Service Desk webhook

This guide describes how to integrate Zabbix 5.0 installation with SolarWinds Service Desk using the Zabbix webhook feature. This guide provides instructions on setting up a media type, a user and an action in Zabbix.
Please note that recovery and update operations and SolarWinds Service Desk's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

1. Before setting up a SolarWinds Service Desk Webhook, it is recommended to setup the global macro "{$ZABBIX.URL}" containing an URL to the Zabbix frontend.
As an example, this macro can be used to populate SolarWinds Service Desk's custom field with URL to an event info or graph.

2. In the Administration > Media types section, import the media_solarwinds_servicedesk.yaml.

3. Open the newly added SolarWinds Service Desk media type and replace all <PLACEHOLDERS> with your values.
The following parameters are required:
samanage_url - actual URL of your SolarWinds Service Desk instance,
samanage_token - API token (see SolarWinds Service Desk tutorial for more information).

4. You can add the following parameters to customize SolarWinds Service Desk ticket:

• priority_<severity>: add this parameter for each Zabbix's severity or use only priority_default.
  priority_default is mandatary.
  Possible values of <severity>:

  • not_classified
  • information
  • warning
  • average
  • high
  • disaster

• sw_field_<fieldname>: add this to fill default SolarWinds Service Desk fields, where <fieldname> is a name of a field. The parameter can contain a simple value or a JSON string.
  Name of the field and value should be consistent with SolarWinds Service Desk API specification.
  Example:
  
  Be careful to use user macro as a value, because special symbols such as quotes can make your JSON invalid.
  

• sw_customfield_<fieldname>: add this to fill preconfigured SolarWinds Service Desk custom field. <fieldname> is a name of a field and may contain whitespaces.
  Example:
  
  

5. Create a Zabbix user and add Media with the SolarWinds Service Desk media type. Though a "Send to" field is not used in SolarWinds Service Desk webhook, it cannot be empty. To comply with frontend requirements, you can put any symbol there. Make sure this user has access to all hosts for which you would like problem notifications to be converted into SolarWinds Service Desk tickets.

For more information see Zabbix and SOLARWINDS documentations.

Supported Versions

Zabbix 5.0

SolarWinds Service Desk webhook

This guide describes how to integrate Zabbix 5.0 installation with SolarWinds Service Desk using the Zabbix webhook feature. This guide provides instructions on setting up a media type, a user and an action in Zabbix.
Please note that recovery and update operations and SolarWinds Service Desk's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

1. Before setting up a SolarWinds Service Desk Webhook, it is recommended to setup the global macro "{$ZABBIX.URL}" containing an URL to the Zabbix frontend.
As an example, this macro can be used to populate SolarWinds Service Desk's custom field with URL to an event info or graph.

2. In the Administration > Media types section, import the media_solarwinds_servicedesk.yaml.

3. Open the newly added SolarWinds Service Desk media type and replace all <PLACEHOLDERS> with your values.
The following parameters are required:
samanage_url - actual URL of your SolarWinds Service Desk instance,
samanage_token - API token (see SolarWinds Service Desk tutorial for more information).

4. You can add the following parameters to customize SolarWinds Service Desk ticket:

• priority_<severity>: add this parameter for each Zabbix's severity or use only priority_default.
  priority_default is mandatary.
  Possible values of <severity>:

  • not_classified
  • information
  • warning
  • average
  • high
  • disaster

• sw_field_<fieldname>: add this to fill default SolarWinds Service Desk fields, where <fieldname> is a name of a field. The parameter can contain a simple value or a JSON string.
  Name of the field and value should be consistent with SolarWinds Service Desk API specification.
  Example:
  
  Be careful to use user macro as a value, because special symbols such as quotes can make your JSON invalid.
  

• sw_customfield_<fieldname>: add this to fill preconfigured SolarWinds Service Desk custom field. <fieldname> is a name of a field and may contain whitespaces.
  Example:
  
  

5. Create a Zabbix user and add Media with the SolarWinds Service Desk media type. Though a "Send to" field is not used in SolarWinds Service Desk webhook, it cannot be empty. To comply with frontend requirements, you can put any symbol there. Make sure this user has access to all hosts for which you would like problem notifications to be converted into SolarWinds Service Desk tickets.

For more information see Zabbix and SOLARWINDS documentations.

Supported Versions

Zabbix 5.0

SolarWinds Service Desk webhook

This guide describes how to integrate Zabbix 5.0 installation with SolarWinds Service Desk using the Zabbix webhook feature. This guide provides instructions on setting up a media type, a user and an action in Zabbix.
Please note that recovery and update operations and SolarWinds Service Desk's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

1. Before setting up a SolarWinds Service Desk Webhook, it is recommended to setup the global macro "{$ZABBIX.URL}" containing an URL to the Zabbix frontend.
As an example, this macro can be used to populate SolarWinds Service Desk's custom field with URL to an event info or graph.

2. In the Administration > Media types section, import the media_solarwinds_servicedesk.xml.

3. Open the newly added SolarWinds Service Desk media type and replace all <PLACEHOLDERS> with your values.
The following parameters are required:
samanage_url - actual URL of your SolarWinds Service Desk instance,
samanage_token - API token (see SolarWinds Service Desk tutorial for more information).

4. You can add the following parameters to customize SolarWinds Service Desk ticket:

• priority_<severity>: add this parameter for each Zabbix's severity or use only priority_default.
  priority_default is mandatary.
  Possible values of <severity>:

  • not_classified
  • information
  • warning
  • average
  • high
  • disaster

• sw_field_<fieldname>: add this to fill default SolarWinds Service Desk fields, where <fieldname> is a name of a field. The parameter can contain a simple value or a JSON string.
  Name of the field and value should be consistent with SolarWinds Service Desk API specification.
  Example:
  
  Be careful to use user macro as a value, because special symbols such as quotes can make your JSON invalid.
  

• sw_customfield_<fieldname>: add this to fill preconfigured SolarWinds Service Desk custom field. <fieldname> is a name of a field and may contain whitespaces.
  Example:
  
  

5. Create a Zabbix user and add Media with the SolarWinds Service Desk media type. Though a "Send to" field is not used in SolarWinds Service Desk webhook, it cannot be empty. To comply with frontend requirements, you can put any symbol there. Make sure this user has access to all hosts for which you would like problem notifications to be converted into SolarWinds Service Desk tickets.

For more information see Zabbix and SOLARWINDS documentations.

Supported Versions

Zabbix 5.0