Available solutions

Jira webhook
Jira Service Desk webhook
Jira Data Center by JMX
3rd party solutions

This template is for Zabbix version: 7.4

Also available for: 7.2 7.0 6.4 6.2 6.0 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira?at=release/7.4

Jira webhook

Overview

This guide describes how to integrate your Zabbix installation with Jira using the Zabbix webhook feature, providing instructions on setting up a media type, user, and action in Zabbix.

Requirements

Zabbix version: 7.4 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
jira_issue_type	<PLACE ISSUETYPE NAME>	Name of issue type to be used when creating new issues.
jira_password	<PLACE PASSWORD OR TOKEN>	Password or token of Jira user.
jira_project_key	<PLACE PROJECT KEY>	Text key of Jira project.
jira_url	<PLACE YOUR JIRA URL>	URL of Jira instance.
jira_user	<PLACE LOGIN>	Username of Jira user.
jira_priority_autoregistration	Low	String value of Jira priority to assign to autoregistration event tickets.
jira_priority_discovery	Low	String value of Jira priority to assign to discovery event tickets.
jira_priority_internal	Low	String value of Jira priority to assign to internal event tickets.
severity_not_classified	Lowest	Jira priority to assign to tickets when event has Zabbix severity "Not classified".
severity_information	Lowest	Jira priority to assign to tickets when event has Zabbix severity "Information".
severity_warning	Low	Jira priority to assign to tickets when event has Zabbix severity "Warning".
severity_average	Medium	Jira priority to assign to tickets when event has Zabbix severity "Average".
severity_high	High	Jira priority to assign to tickets when event has Zabbix severity "High".
severity_disaster	Highest	Jira priority to assign to tickets when event has Zabbix severity "Disaster".
zabbix_url	{$ZABBIX.URL}	Current Zabbix URL.

Internal parameters

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

Name	Value	Description
trigger_description	{TRIGGER.DESCRIPTION}	Trigger description.
alert_message	{ALERT.MESSAGE}	'Default message' value from action configuration.
alert_subject	{ALERT.SUBJECT}	'Default subject' value from action configuration.
event_id	{EVENT.ID}	Numeric ID of the event that triggered an action.
event_recovery_value	{EVENT.RECOVERY.VALUE}	Numeric value of the recovery event.
event_source	{EVENT.SOURCE}	Numeric value of the event source. Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal, 4 - Service.
event_tags_json	{EVENT.TAGSJSON}	A JSON array containing event tag objects. Expanded to an empty array if no tags exist.
event_update_action	{EVENT.UPDATE.ACTION}	Human-readable name of the action(s) performed during a problem update.
event_update_message	{EVENT.UPDATE.MESSAGE}	Problem update message.
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.
event_update_user	{USER.FULLNAME}	Name, surname, and username of the user who added an event acknowledgment or started the script.
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.
trigger_id	{TRIGGER.ID}	Numeric ID of the trigger of this action.

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 you can start using the Jira webhook, you need to set up the global macro {$ZABBIX.URL} containing an URL to the Zabbix frontend.

The global macro can also be used, for example, to populate a custom field in Jira with a URL linking to event information or a graph.

2. In the Zabbix frontend Alerts > Media types section, import the file media_jira.yaml.

3. Open the newly added Jira media type and, under Parameters, replace all <PLACEHOLDERS> with your values. The following parameters are required:

jira_url - actual URL of your Jira instance,
jira_user - Jira user login,
jira_password - password or API token (for Jira Cloud installations, an API token can be obtained at https://id.atlassian.com/manage/api-tokens),
jira_project_key - text key of the Jira project (not to be mistaken with the ID!),
jira_issue_type - name of the issue type to be used when creating new issues from Zabbix notifications.

4. It is also possible to set Jira ticket priorities by parameters. Predefined parameter values are already in place; however, be aware that they use the default Jira priorities. Please, adjust these values to suit your Jira environment.

The following parameters are for events in Zabbix that support severities:

severity_not_classified - for "Not Classified" Zabbix severity
severity_information - for "Information" Zabbix severity
severity_warning - for "Warning" Zabbix severity
severity_average - for "Average" Zabbix severity
severity_high - for "High" Zabbix severity
severity_disaster - for "Disaster" Zabbix severity

And the following for Zabbix events that do not have severities:

jira_priority_internal - for Zabbix internal events
jira_priority_discovery - for Zabbix discovery events
jira_priority_autoregistration - for Zabbix autoregistration events

5. You can customize Jira issues with custom fields.

By default, the webhook does not use Jira custom fields. In order to populate a Jira custom field via webhook, you must add a parameter to the Jira media type configuration where the custom field ID is used as the key (Name). For details on finding custom field IDs, see Jira documentation.

The following custom field types are supported:

String
URL
Number
Date
DateTime
Single-select
Multi-select
Checkbox
Radio button

Note that you can enter only one value per custom field, except in the multi-select and checkbox field types where multiple values can be entered, using a comma as a separator (option1,option2,option3).

Examples:

URL custom fields can be configured in different ways.

If you want a Zabbix URL to appear in the Jira custom URL field, set the field to zabbix_url. By default, the value of zabbix_url is the {$ZABBIX.URL} macro. The script will then use the value of zabbix_url for your custom field, formatting it to the action being run:

for trigger actions, the script will append a path to your Zabbix URL leading directly to the problem event;
for service actions, the script will append a path to your Zabbix URL leading to service actions;
for the rest of the actions, it will leave the URL as is.

If you don't need to use the Zabbix URL in the custom field and want to link to something else (another service), you can manually enter the URL, and the script won’t modify it.

For the DateTime custom field, you can combine parameter values using the format {EVENT.DATE}T{EVENT.TIME}.

Note that the date and time must be provided in the ISO 8601 format with the timezone of Zabbix server (2020-01-01T23:59:59+0200). If server time is set to UTC, there is no need to add the timezone at the end of the parameter value.

6. This webhook also supports components, but they’re not used by default. To include a component, add a new parameter to the Jira media type for each one. The parameter key (Name) should start with component_ and end with a unique identifier. In the Value field, enter the component name from Jira.

IMPORTANT! Compass components are not supported!

7. Create a Zabbix user and add Media with the Jira media type. Though the Send to field is not used in the Jira 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 converted into Jira tasks.

For more information, please see Zabbix and Jira documentation.

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.

This template is for Zabbix version: 7.2

Also available for: 7.4 7.0 6.4 6.2 6.0 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira?at=release/7.2

Jira webhook

Overview

This guide describes how to integrate your Zabbix installation with Jira using the Zabbix webhook feature, providing instructions on setting up a media type, user, and action in Zabbix.

Requirements

Zabbix 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
jira_issue_type	<PLACE ISSUETYPE NAME>	Name of issue type to be used when creating new issues.
jira_password	<PLACE PASSWORD OR TOKEN>	Password or token of Jira user.
jira_project_key	<PLACE PROJECT KEY>	Text key of Jira project.
jira_url	<PLACE YOUR JIRA URL>	URL of Jira instance.
jira_user	<PLACE LOGIN>	Username of Jira user.
jira_priority_autoregistration	Low	String value of Jira priority to assign to autoregistration event tickets.
jira_priority_discovery	Low	String value of Jira priority to assign to discovery event tickets.
jira_priority_internal	Low	String value of Jira priority to assign to internal event tickets.
severity_not_classified	Lowest	Jira priority to assign to tickets when event has Zabbix severity "Not classified".
severity_information	Lowest	Jira priority to assign to tickets when event has Zabbix severity "Information".
severity_warning	Low	Jira priority to assign to tickets when event has Zabbix severity "Warning".
severity_average	Medium	Jira priority to assign to tickets when event has Zabbix severity "Average".
severity_high	High	Jira priority to assign to tickets when event has Zabbix severity "High".
severity_disaster	Highest	Jira priority to assign to tickets when event has Zabbix severity "Disaster".
zabbix_url	{$ZABBIX.URL}	Current Zabbix URL.

Internal parameters

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

Name	Value	Description
trigger_description	{TRIGGER.DESCRIPTION}	Trigger description.
alert_message	{ALERT.MESSAGE}	'Default message' value from action configuration.
alert_subject	{ALERT.SUBJECT}	'Default subject' value from action configuration.
event_id	{EVENT.ID}	Numeric ID of the event that triggered an action.
event_recovery_value	{EVENT.RECOVERY.VALUE}	Numeric value of the recovery event.
event_source	{EVENT.SOURCE}	Numeric value of the event source. Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal, 4 - Service.
event_tags_json	{EVENT.TAGSJSON}	A JSON array containing event tag objects. Expanded to an empty array if no tags exist.
event_update_action	{EVENT.UPDATE.ACTION}	Human-readable name of the action(s) performed during a problem update.
event_update_message	{EVENT.UPDATE.MESSAGE}	Problem update message.
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.
event_update_user	{USER.FULLNAME}	Name, surname, and username of the user who added an event acknowledgment or started the script.
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.
trigger_id	{TRIGGER.ID}	Numeric ID of the trigger of this action.

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 you can start using the Jira webhook, you need to set up the global macro {$ZABBIX.URL} containing an URL to the Zabbix frontend.

The global macro can also be used, for example, to populate a custom field in Jira with a URL linking to event information or a graph.

2. In the Zabbix frontend Alerts > Media types section, import the file media_jira.yaml.

3. Open the newly added Jira media type and, under Parameters, replace all <PLACEHOLDERS> with your values. The following parameters are required:

jira_url - actual URL of your Jira instance,
jira_user - Jira user login,
jira_password - password or API token (for Jira Cloud installations, an API token can be obtained at https://id.atlassian.com/manage/api-tokens),
jira_project_key - text key of the Jira project (not to be mistaken with the ID!),
jira_issue_type - name of the issue type to be used when creating new issues from Zabbix notifications.

The following parameters are for events in Zabbix that support severities:

severity_not_classified - for "Not Classified" Zabbix severity
severity_information - for "Information" Zabbix severity
severity_warning - for "Warning" Zabbix severity
severity_average - for "Average" Zabbix severity
severity_high - for "High" Zabbix severity
severity_disaster - for "Disaster" Zabbix severity

And the following for Zabbix events that do not have severities:

jira_priority_internal - for Zabbix internal events
jira_priority_discovery - for Zabbix discovery events
jira_priority_autoregistration - for Zabbix autoregistration events

5. You can customize Jira issues with custom fields.

The following custom field types are supported:

String
URL
Number
Date
DateTime
Single-select
Multi-select
Checkbox
Radio button

Examples:

URL custom fields can be configured in different ways.

for trigger actions, the script will append a path to your Zabbix URL leading directly to the problem event;
for service actions, the script will append a path to your Zabbix URL leading to service actions;
for the rest of the actions, it will leave the URL as is.

If you don't need to use the Zabbix URL in the custom field and want to link to something else (another service), you can manually enter the URL, and the script won’t modify it.

For the DateTime custom field, you can combine parameter values using the format {EVENT.DATE}T{EVENT.TIME}.

IMPORTANT! Compass components are not supported!

Make sure this user has access to all the hosts for which you would like problem notifications to be converted into Jira tasks.

For more information, please see Zabbix and Jira documentation.

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.

This template is for Zabbix version: 7.0

Also available for: 7.4 7.2 6.4 6.2 6.0 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira?at=release/7.0

Jira webhook

Overview

This guide describes how to integrate your Zabbix installation with Jira using the Zabbix webhook feature, providing instructions on setting up a media type, user, and action in Zabbix.

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.

Name	Value	Description
jira_issue_type	<PLACE ISSUETYPE NAME>	Name of issue type to be used when creating new issues.
jira_password	<PLACE PASSWORD OR TOKEN>	Password or token of Jira user.
jira_project_key	<PLACE PROJECT KEY>	Text key of Jira project.
jira_url	<PLACE YOUR JIRA URL>	URL of Jira instance.
jira_user	<PLACE LOGIN>	Username of Jira user.
jira_priority_autoregistration	Low	String value of Jira priority to assign to autoregistration event tickets.
jira_priority_discovery	Low	String value of Jira priority to assign to discovery event tickets.
jira_priority_internal	Low	String value of Jira priority to assign to internal event tickets.
severity_not_classified	Lowest	Jira priority to assign to tickets when event has Zabbix severity "Not classified".
severity_information	Lowest	Jira priority to assign to tickets when event has Zabbix severity "Information".
severity_warning	Low	Jira priority to assign to tickets when event has Zabbix severity "Warning".
severity_average	Medium	Jira priority to assign to tickets when event has Zabbix severity "Average".
severity_high	High	Jira priority to assign to tickets when event has Zabbix severity "High".
severity_disaster	Highest	Jira priority to assign to tickets when event has Zabbix severity "Disaster".
zabbix_url	{$ZABBIX.URL}	Current Zabbix URL.

Internal parameters

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

Name	Value	Description
trigger_description	{TRIGGER.DESCRIPTION}	Trigger description.
alert_message	{ALERT.MESSAGE}	'Default message' value from action configuration.
alert_subject	{ALERT.SUBJECT}	'Default subject' value from action configuration.
event_id	{EVENT.ID}	Numeric ID of the event that triggered an action.
event_recovery_value	{EVENT.RECOVERY.VALUE}	Numeric value of the recovery event.
event_source	{EVENT.SOURCE}	Numeric value of the event source. Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal, 4 - Service.
event_tags_json	{EVENT.TAGSJSON}	A JSON array containing event tag objects. Expanded to an empty array if no tags exist.
event_update_action	{EVENT.UPDATE.ACTION}	Human-readable name of the action(s) performed during a problem update.
event_update_message	{EVENT.UPDATE.MESSAGE}	Problem update message.
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.
event_update_user	{USER.FULLNAME}	Name, surname, and username of the user who added an event acknowledgment or started the script.
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.
trigger_id	{TRIGGER.ID}	Numeric ID of the trigger of this action.

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 you can start using the Jira webhook, you need to set up the global macro {$ZABBIX.URL} containing an URL to the Zabbix frontend.

The global macro can also be used, for example, to populate a custom field in Jira with a URL linking to event information or a graph.

2. In the Zabbix frontend Alerts > Media types section, import the file media_jira.yaml.

3. Open the newly added Jira media type and, under Parameters, replace all <PLACEHOLDERS> with your values. The following parameters are required:

jira_url - actual URL of your Jira instance,
jira_user - Jira user login,
jira_password - password or API token (for Jira Cloud installations, an API token can be obtained at https://id.atlassian.com/manage/api-tokens),
jira_project_key - text key of the Jira project (not to be mistaken with the ID!),
jira_issue_type - name of the issue type to be used when creating new issues from Zabbix notifications.

The following parameters are for events in Zabbix that support severities:

severity_not_classified - for "Not Classified" Zabbix severity
severity_information - for "Information" Zabbix severity
severity_warning - for "Warning" Zabbix severity
severity_average - for "Average" Zabbix severity
severity_high - for "High" Zabbix severity
severity_disaster - for "Disaster" Zabbix severity

And the following for Zabbix events that do not have severities:

jira_priority_internal - for Zabbix internal events
jira_priority_discovery - for Zabbix discovery events
jira_priority_autoregistration - for Zabbix autoregistration events

5. You can customize Jira issues with custom fields.

The following custom field types are supported:

String
URL
Number
Date
DateTime
Single-select
Multi-select
Checkbox
Radio button

Examples:

URL custom fields can be configured in different ways.

for trigger actions, the script will append a path to your Zabbix URL leading directly to the problem event;
for service actions, the script will append a path to your Zabbix URL leading to service actions;
for the rest of the actions, it will leave the URL as is.

If you don't need to use the Zabbix URL in the custom field and want to link to something else (another service), you can manually enter the URL, and the script won’t modify it.

For the DateTime custom field, you can combine parameter values using the format {EVENT.DATE}T{EVENT.TIME}.

IMPORTANT! Compass components are not supported!

Make sure this user has access to all the hosts for which you would like problem notifications to be converted into Jira tasks.

For more information, please see Zabbix and Jira documentation.

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.

This template is for Zabbix version: 6.4

Also available for: 7.4 7.2 7.0 6.2 6.0 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira?at=release/6.4

Jira webhook

This guide describes how to integrate Zabbix 6.2 installation with Jira 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 Jira's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

1. Before setting up a Jira 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 Jira's custom field with URL to an event info or graph.

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

3. Open the newly added Jira media type and replace all <PLACEHOLDERS> with your values.
The following parameters are required:
jira_url - actual URL of your Jira instance,
jira_user - Jira user login,
jira_password - password or API token (for Jira Cloud installations an API token can be obtained at https://id.atlassian.com/manage/api-tokens),
jira_project_key - text key of the Jira project (not to be mistaken with an ID!),
jira_issue_type - name of the issue type to be used when creating new issues from Zabbix notifications.

4. You can customize Jira issue by export information into Jira custom fields.
By default the webhook does not use Jira custom fields and {ALERT.MESSAGE} is used as an issue description.

To export information into your Jira custom field, add a parameter with custom field ID as key (if you need help finding custom field ID, see this page in Jira documentation). If at least one parameter starting with "customfield_" is configured for the media type, the webhook will use {TRIGGER.DESCRIPTION} as an issue description instead of {ALERT.MESSAGE} to avoid duplication of information in description and custom fields.
We recommend creating custom fields for all of {ALERT.MESSAGE} fields like "Host", "Link to event info", "Trigger ID", "Event date", etc.

Jira webhook supports the following custom fields types:

String
URL
Number
Datetime
Single-select
Multi-select
Checkbox
Radio button

Examples:

You can use combined parameter value as {$ZABBIX.URL}/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID} or {EVENT.DATE}T{EVENT.TIME}.

Note, that you can pass only one value for each custom field including multi-select and checkbox.

Date and time must be in ISO 8601 format with timezone of the Zabbix server (2020-01-01T23:59:59+0200). If server time is set to UTC, there is no need to add timezone at the end of parameter value.

5. Create a Zabbix user and add Media with the Jira media type. Though a "Send to" field is not used in Jira 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 Jira tasks.

For more information see Zabbix and Jira documentations.

Supported Versions

Zabbix 6.2

This template is for Zabbix version: 6.2

Also available for: 7.4 7.2 7.0 6.4 6.0 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira?at=release/6.2

Jira webhook

Setting up webhook in Zabbix

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

4. You can customize Jira issue by export information into Jira custom fields.
By default the webhook does not use Jira custom fields and {ALERT.MESSAGE} is used as an issue description.

Jira webhook supports the following custom fields types:

String
URL
Number
Datetime
Single-select
Multi-select
Checkbox
Radio button

Examples:

You can use combined parameter value as {$ZABBIX.URL}/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID} or {EVENT.DATE}T{EVENT.TIME}.

Note, that you can pass only one value for each custom field including multi-select and checkbox.

Date and time must be in ISO 8601 format with timezone of the Zabbix server (2020-01-01T23:59:59+0200). If server time is set to UTC, there is no need to add timezone at the end of parameter value.

For more information see Zabbix and Jira documentations.

Supported Versions

Zabbix 6.2

This template is for Zabbix version: 6.0

Also available for: 7.4 7.2 7.0 6.4 6.2 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira?at=release/6.0

Jira webhook

This guide describes how to integrate Zabbix 5.0 installation with Jira 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 Jira's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

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

4. You can customize Jira issue by export information into Jira custom fields.
By default the webhook does not use Jira custom fields and {ALERT.MESSAGE} is used as an issue description.

Jira webhook supports the following custom fields types:

String
URL
Number
Datetime
Single-select
Multi-select
Checkbox
Radio button

Examples:

You can use combined parameter value as {$ZABBIX.URL}/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID} or {EVENT.DATE}T{EVENT.TIME}.

Note, that you can pass only one value for each custom field including multi-select and checkbox.

Date and time must be in ISO 8601 format with timezone of the Zabbix server (2020-01-01T23:59:59+0200). If server time is set to UTC, there is no need to add timezone at the end of parameter value.

For more information see Zabbix and Jira documentations.

Supported Versions

Zabbix 5.0

This template is for Zabbix version: 5.4

Also available for: 7.4 7.2 7.0 6.4 6.2 6.0 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira?at=release/5.4

Jira webhook

Setting up webhook in Zabbix

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

4. You can customize Jira issue by export information into Jira custom fields.
By default the webhook does not use Jira custom fields and {ALERT.MESSAGE} is used as an issue description.

Jira webhook supports the following custom fields types:

String
URL
Number
Datetime
Single-select
Multi-select
Checkbox
Radio button

Examples:

You can use combined parameter value as {$ZABBIX.URL}/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID} or {EVENT.DATE}T{EVENT.TIME}.

Note, that you can pass only one value for each custom field including multi-select and checkbox.

Date and time must be in ISO 8601 format with timezone of the Zabbix server (2020-01-01T23:59:59+0200). If server time is set to UTC, there is no need to add timezone at the end of parameter value.

For more information see Zabbix and Jira documentations.

Supported Versions

Zabbix 5.0

This template is for Zabbix version: 5.0

Also available for: 7.4 7.2 7.0 6.4 6.2 6.0 5.4

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira?at=release/5.0

Jira webhook

Setting up webhook in Zabbix

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

4. You can customize Jira issue by export information into Jira custom fields.
By default the webhook does not use Jira custom fields and {ALERT.MESSAGE} is used as an issue description.

Jira webhook supports the following custom fields types:

String
URL
Number
Datetime
Single-select
Multi-select
Checkbox
Radio button

Examples:

You can use combined parameter value as {$ZABBIX.URL}/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID} or {EVENT.DATE}T{EVENT.TIME}.

Note, that you can pass only one value for each custom field including multi-select and checkbox.

Date and time must be in ISO 8601 format with timezone of the Zabbix server (2020-01-01T23:59:59+0200). If server time is set to UTC, there is no need to add timezone at the end of parameter value.

For more information see Zabbix and Jira documentations.

Supported Versions

Zabbix 5.0

This template is for Zabbix version: 6.4

Also available for: 6.2 6.0 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira_servicedesk?at=release/6.4

Jira Service Desk webhook

This guide describes how to integrate Zabbix 6.2 installation with Jira 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 Jira Service Desk's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

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

2. In the "Administration -> Media types" section, import the media_jira_servicedesk.yaml

3. Open the newly added Jira Service Desk media type and replace all <PLACEHOLDERS> with your values.
The following parameters are required:
jira_url - actual URL of your Jira Service Desk instance,
jira_user - Jira Service Desk user login,
jira_password - password or API token (for Jira Service Desk Cloud installations an API token can be obtained at https://id.atlassian.com/manage/api-tokens),
jira_servicedesk_id - numerical ID of your Jira Service Desk (not to be mistaken with a project ID or a Service Desk key!),
jira_request_type_id - numerical ID of your Jira Service Desk RequestType.

By default, the webhook does not use Jira Service Desk custom fields. To export information into your Jira Service Desk custom field, add a parameter with custom field ID as a key (if you need help finding custom field ID, see this page in Jira Service Desk documentation).

Notes:

All custom fields should not be hidden from the request form.
Jira Service Desk webhook supports string, URL, number, and datetime fields for now.
Date and time must be in ISO 8601 format with the timezone of the Zabbix server (yyyy-MM-ddTHH:mm:ss+hhmm). You can use "{EVENT.DATE}T{EVENT.TIME}" pattern, all dots from Zabbix yyyy.MM.dd format will be replaced by dashes.
If the server time is set to UTC, there is no need to add a timezone at the end of the parameter value.

4. Create a Zabbix user and add Media with the Jira Service Desk media type. Though a "Send to" field is not used in the Jira 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 Jira Service Desk tasks.

For more information see Zabbix and Jira Service Desk documentations.

Supported Versions

Zabbix 6.2

This template is for Zabbix version: 6.2

Also available for: 6.4 6.0 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira_servicedesk?at=release/6.2

Jira Service Desk webhook

Setting up webhook in Zabbix

2. In the "Administration -> Media types" section, import the media_jira_servicedesk.yaml

Notes:

All custom fields should not be hidden from the request form.
Jira Service Desk webhook supports string, URL, number, and datetime fields for now.
Date and time must be in ISO 8601 format with the timezone of the Zabbix server (yyyy-MM-ddTHH:mm:ss+hhmm). You can use "{EVENT.DATE}T{EVENT.TIME}" pattern, all dots from Zabbix yyyy.MM.dd format will be replaced by dashes.
If the server time is set to UTC, there is no need to add a timezone at the end of the parameter value.

For more information see Zabbix and Jira Service Desk documentations.

Supported Versions

Zabbix 6.2

This template is for Zabbix version: 6.0

Also available for: 6.4 6.2 5.4 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira_servicedesk?at=release/6.0

Jira Service Desk webhook

This guide describes how to integrate Zabbix 5.0 installation with Jira 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 Jira Service Desk's custom fields are supported only for trigger-based events.

Setting up webhook in Zabbix

2. In the "Administration -> Media types" section, import the media_jira_servicedesk.yaml

Notes:

All custom fields should not be hidden from the request form.
Jira Service Desk webhook supports string, URL, number, and datetime fields for now.
Date and time must be in ISO 8601 format with the timezone of the Zabbix server (yyyy-MM-ddTHH:mm:ss+hhmm). You can use "{EVENT.DATE}T{EVENT.TIME}" pattern, all dots from Zabbix yyyy.MM.dd format will be replaced by dashes.
If the server time is set to UTC, there is no need to add a timezone at the end of the parameter value.

For more information see Zabbix and Jira Service Desk documentations.

Supported Versions

Zabbix 5.0

This template is for Zabbix version: 5.4

Also available for: 6.4 6.2 6.0 5.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira_servicedesk?at=release/5.4

Jira Service Desk webhook

Setting up webhook in Zabbix

2. In the "Administration -> Media types" section, import the media_jira_servicedesk.yaml

Notes:

All custom fields should not be hidden from the request form.
Jira Service Desk webhook supports string, URL, number, and datetime fields for now.
Date and time must be in ISO 8601 format with the timezone of the Zabbix server (yyyy-MM-ddTHH:mm:ss+hhmm). You can use "{EVENT.DATE}T{EVENT.TIME}" pattern, all dots from Zabbix yyyy.MM.dd format will be replaced by dashes.
If the server time is set to UTC, there is no need to add a timezone at the end of the parameter value.

For more information see Zabbix and Jira Service Desk documentations.

Supported Versions

Zabbix 5.0

This template is for Zabbix version: 5.0

Also available for: 6.4 6.2 6.0 5.4

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira_servicedesk?at=release/5.0

Jira Service Desk webhook

Setting up webhook in Zabbix

2. In the "Administration -> Media types" section, import the media_jira_servicedesk.xml

Notes:

All custom fields should not be hidden from the request form.
Jira Service Desk webhook supports string, URL, number, and datetime fields for now.
Date and time must be in ISO 8601 format with the timezone of the Zabbix server (yyyy-MM-ddTHH:mm:ss+hhmm). You can use "{EVENT.DATE}T{EVENT.TIME}" pattern, all dots from Zabbix yyyy.MM.dd format will be replaced by dashes.
If the server time is set to UTC, there is no need to add a timezone at the end of the parameter value.

For more information see Zabbix and Jira Service Desk documentations.

Supported Versions

Zabbix 5.0

This template is for Zabbix version: 7.4

Also available for: 7.2 7.0 6.4 6.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/jira_datacenter_jmx?at=release/7.4

Jira Data Center by JMX

Overview

This template is used for monitoring Jira Data Center health. It is designed for standalone operation for on-premises Jira installations.

This template uses a single data source, JMX, which requires JMX RMI setup of your Jira application and Java Gateway setup on the Zabbix side. If you need "Garbage collector" and "Web server" monitoring, add "Generic Java JMX" and "Apache Tomcat by JMX" templates on the same host.

Requirements

Zabbix version: 7.4 and higher.

Tested versions

This template has been tested on:

Jira Data Center 9.14.1
Jira Data Center 9.12.4

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Metrics are collected by JMX. 0. Deploy the Zabbix Java Gateway component (instructions).

Enable and configure JMX access to Jira Data Center. See documentation for instructions.
Assign the "Jira Data Center by JMX" template to the host with a JMX interface.
If your Jira installation requires authentication for JMX, set the values in the host macros {$JMX.USERNAME} and {$JMX.PASSWORD}.
(Optional) Set custom macro values and add macros with context for specific metrics following the macro description.
(Optional) Assign the "Generic Java JMX" template for garbage collector monitoring.
(Optional) Assign the "Apache Tomcat by JMX" template for web server monitoring.

Macros used

Name	Description	Default
{$JMX.USER}	User for JMX.
{$JMX.PASSWORD}	Password for JMX.
{$JIRA_DC.LICENSE.USER.CAPACITY.WARN}	User capacity warning threshold (%).	`80`
{$JIRA_DC.DB.CONNECTION.USAGE.WARN}	Warning threshold for database connections usage (%).	`80`
{$JIRA_DC.ISSUE.LATENCY.WARN}	Warning threshold for issue operation latency (in seconds).	`5`
{$JIRA_DC.STORAGE.LATENCY.WARN}	Warning threshold for storage write operation latency (in seconds).	`5`
{$JIRA_DC.INDEXING.LATENCY.WARN}	Warning threshold for indexing operation latency (in seconds).	`5`
{$JIRA_DC.LLD.FILTER.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`local\|share`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.INDEXING}	Used for indexing metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.INDEXING}	Used for indexing metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.ISSUE}	Used for issue discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.ISSUE}	Used for issue discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.MAIL}	Used for mail server connection metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.MAIL}	Used for mail server connection metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.LICENSE}	Used for license discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.LICENSE}	Used for license discovery.	`NO MATCH`

Items

Name	Description	Type	Key and additional info
DB: Connections: State	The state of the database connection.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value]
DB: Connections: Failed per minute	The count of database connection failures registered in one minute. Units: fpm - fails per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=failures,name=counter",Count] Preprocessing Simple change:
DB: Pool: Connections: Idle	Idle connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value]
DB: Pool: Connections: Active	Active connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numActive,name=value",Value]
DB: Reads	Database read operations from Jira per second. Units: rps - read operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.reads",invocation.count] Preprocessing Change per second:
DB: Writes	Database write operations from Jira per second. Units: wps - write operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.writes",invocation.count] Preprocessing Change per second:
DB: Connections: Limit	Total allowed database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal]
DB: Connections: Active	Active database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive]
DB: Connections: Latency	The latest measure of latency when querying the database.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=latency,name=value",Value]
License: Users: Get	License data for the discovery rule.	JMX agent	jmx.discovery[attributes,"com.atlassian.jira:type=jira.license"] Preprocessing JavaScript: `The text is too long. Please see the template.`
HTTP: Pool: Connections: Active	The latest measure of the number of active connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numActive,name=value",Value]
HTTP: Pool: Connections: Idle	The latest measure of the number of idle connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value]
HTTP: Sessions: Active	The latest measure of the number of active user sessions.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=sessions,category03=active,name=value",Value]
HTTP: Requests per minute	The latest measure of the total number of HTTP requests per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=requests,name=value",Value]
Mail: Queue	The latest measure of the number of items in a mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value]
Mail: Queue: Error	The latest measure of the number of items in an error mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value]
Mail: Sent per minute	The latest measure of the number of emails sent by the SMTP server per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numEmailsSentPerMin,name=value",Value]
Mail: Processed per minute	The latest measure of the number of items processed by a mail queue per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItemsProcessedPerMin,name=value",Value]
Mail: Queue: Processing state	The latest indicator of the state of a mail queue job.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value]
Entity: Issues	The number of issues.	JMX agent	jmx["com.atlassian.jira:type=entity.issues.total",Value]
Entity: Attachments	The number of attachments.	JMX agent	jmx["com.atlassian.jira:type=entity.attachments.total",Value]
Entity: Components	The number of components.	JMX agent	jmx["com.atlassian.jira:type=entity.components.total",Value]
Entity: Custom fields	The number of custom fields.	JMX agent	jmx["com.atlassian.jira:type=entity.customfields.total",Value]
Entity: Filters	The number of filters.	JMX agent	jmx["com.atlassian.jira:type=entity.filters.total",Value]
Entity: Versions created	The number of versions created.	JMX agent	jmx["com.atlassian.jira:type=entity.versions.total",Value]
Issue: Search per minute	Issue searches performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.search.count",Value] Preprocessing Simple change:
Issue: Created per minute	Issues created per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.created.count",Value] Preprocessing Simple change:
Issue: Updates per minute	Issue updates performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.updated.count",Value] Preprocessing Simple change:
Quicksearch: Concurrent searches	The number of concurrent searches that are being performed in real-time by using the quick search.	JMX agent	jmx["com.atlassian.jira:type=quicksearch.concurrent.search",Value] Preprocessing Simple change:

Triggers

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: DB: Connection lost	Database connection lost	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value],3m)=0`	Average	Manual close: Yes
Jira Data Center: DB: Pool: Out of idle connections	Fires when out of idle connections in database pool for 5 minutes.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
Jira Data Center: DB: Connection usage is near the limit		`100*min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)/last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])>{$JIRA_DC.DB.CONNECTION.USAGE.WARN}`	Warning	Manual close: Yes
Jira Data Center: DB: Connection limit reached		`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)=last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])`	Warning	Manual close: Yes
Jira Data Center: HTTP: Pool: Out of idle connections	All available connections are utilized. It can cause outages for users as the system is unable to serve their requests.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
Jira Data Center: Mail: Queue: Doesn’t empty over an extended period	Might indicate SMTP performance or connection problems.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],30m)>0`	Warning	Manual close: Yes Depends on: Jira Data Center: Mail: Queue job is not running
Jira Data Center: Mail: Error queue contains one or more items	A mail queue attempts to resend items up to 10 times. If the operation fails for the 11th time, the items are put into an error mail queue. You can remove items from the error mail queue in one of the following ways: - Manually clear the whole error queue. - Manually resend all items from the error queue to a mail queue. You should pay attention to the cases where an error mail queue item gets back to an error mail queue after you resend the items manually. These cases might indicate permanent performance issues.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value],5m)>0`	Warning	Manual close: Yes
Jira Data Center: Mail: Queue job is not running	It should be running when its queue is not empty. Might indicate SMTP server connection problems.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value],15m)=0 and min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],15m)>0`	Average	Manual close: Yes

LLD rule Storage discovery

Name	Description	Type	Key and additional info
Storage discovery	Discovery of the Jira storage metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=home,category01=,category02=write,category03=latency,,name=value"]

Item prototypes for Storage discovery

Name Description Type Key and additional info

Storage [{#JMXCATEGORY01}]: Latency

Name	Description	Type	Key and additional info
Storage [{#JMXCATEGORY01}]: Latency	The median latency of writing a small file (~30 bytes) to `{#JMXCATEGORY01}`.	JMX agent	jmx["{#JMXOBJ}",Value] Preprocessing Custom multiplier: `0.001`

The median latency of writing a small file (~30 bytes) to {#JMXCATEGORY01}.

JMX agent

jmx["{#JMXOBJ}",Value]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Storage discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Storage [{#JMXCATEGORY01}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Value],5m)>{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`	Warning	Manual close: Yes

LLD rule Mail server discovery

Name	Description	Type	Key and additional info
Mail server discovery	Discovery of the Jira connected mail servers.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=mail,category01=,category02=connection,category03=state,name="]

Item prototypes for Mail server discovery

Name Description Type Key and additional info

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Connection state

Name	Description	Type	Key and additional info
Mail [{#JMXCATEGORY01},{#JMXNAME}]: Connection state	Shows connection state of Jira to discovered mail server: `{#JMXCATEGORY01}-{#JMXNAME}`	JMX agent	jmx["{#JMXOBJ}",Connected] Preprocessing Boolean to decimal:
Mail [{#JMXCATEGORY01},{#JMXNAME}]: Failures per minute	Count of failed connections to discovered mail server `{#JMXCATEGORY01}-{#JMXNAME}` per minute	JMX agent	jmx["{#JMXOBJ}",TotalFailures] Preprocessing Simple change:

Shows connection state of Jira to discovered mail server: {#JMXCATEGORY01}-{#JMXNAME}

JMX agent

jmx["{#JMXOBJ}",Connected]

Preprocessing

Boolean to decimal:

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Failures per minute

Count of failed connections to discovered mail server {#JMXCATEGORY01}-{#JMXNAME} per minute

JMX agent

jmx["{#JMXOBJ}",TotalFailures]

Preprocessing

Simple change:

Trigger prototypes for Mail server discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Mail [{#JMXCATEGORY01}-{#JMXNAME}]: Server disconnected	Trigger is fired when discovered mail server `{#JMXCATEGORY01}-{#JMXNAME}` becomes unavailable	`max(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Connected],5m)=0`	Average	Manual close: Yes

LLD rule Indexing latency discovery

Name	Description	Type	Key and additional info
Indexing latency discovery	Discovery of the Jira indexing metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=indexing,name=*"]

Item prototypes for Indexing latency discovery

Name Description Type Key and additional info

Indexing [{#JMXNAME}]: Latency

Name	Description	Type	Key and additional info
Indexing [{#JMXNAME}]: Latency	Average time spent on indexing operations.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean] Preprocessing Custom multiplier: `0.001`

Average time spent on indexing operations.

JMX agent

jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Indexing latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Indexing [{#JMXNAME}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean],5m)>{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule Issue latency discovery

Name	Description	Type	Key and additional info
Issue latency discovery	Discovery of the Jira issue latency metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=issue,name=*"]

Item prototypes for Issue latency discovery

Name Description Type Key and additional info

Issue [{#JMXNAME}]: Latency

Name	Description	Type	Key and additional info
Issue [{#JMXNAME}]: Latency	Average time spent on issue `{#JMXNAME}` operations.	JMX agent	jmx["{#JMXOBJ}",Mean] Preprocessing Custom multiplier: `0.001`

Average time spent on issue {#JMXNAME} operations.

JMX agent

jmx["{#JMXOBJ}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Issue latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Issue [{#JMXNAME}]: Slow operations	Fires when latency grows above the threshold: `{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Mean],5m)>{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule License discovery

Name Description Type Key and additional info

License discovery

Name	Description	Type	Key and additional info
License discovery	Discovery of the Jira licenses.	Dependent item	jmx.license.discovery Preprocessing JavaScript: `The text is too long. Please see the template.` Discard unchanged with heartbeat: `1h`

Discovery of the Jira licenses.

Dependent item

jmx.license.discovery

Preprocessing

JavaScript: The text is too long. Please see the template.
Discard unchanged with heartbeat: 1h

Item prototypes for License discovery

Name Description Type Key and additional info

License [{#LICENSE.TYPE}]: Users: Current

Name	Description	Type	Key and additional info
License [{#LICENSE.TYPE}]: Users: Current	Current user count for `{#LICENSE.TYPE}`.	Dependent item	jmx.license.get.user.current["{#LICENSE.TYPE}"] Preprocessing JSON Path: `$.{#LICENSE.TYPE}.properties.current_user_count`
License [{#LICENSE.TYPE}]: Users: Maximum	User count limit for `{#LICENSE.TYPE}`. `-1` = No limits for the license type.	Dependent item	jmx.license.get.user.max["{#LICENSE.TYPE}"] Preprocessing JSON Path: `$.{#LICENSE.TYPE}.properties.max_user_count`

Current user count for {#LICENSE.TYPE}.

Dependent item

jmx.license.get.user.current["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.current_user_count

License [{#LICENSE.TYPE}]: Users: Maximum

User count limit for {#LICENSE.TYPE}.

-1 = No limits for the license type.

Dependent item

jmx.license.get.user.max["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.max_user_count

Trigger prototypes for License discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: License [{#LICENSE.TYPE}]: Low user capacity	Fires when relative user quantity grows above the threshold: `{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"}`%	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * (100*last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"])/last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"})`	Warning	Manual close: Yes Depends on: Jira Data Center: License [{#LICENSE.TYPE}]: User count reached the limit
Jira Data Center: License [{#LICENSE.TYPE}]: User count reached the limit	Fires when user quantity reaches the limit. It won't fire if the limit is disabled (set to `-1`).	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * ((last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])-last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"]))<=0)`	Average	Manual close: Yes

Feedback

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

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

This template is for Zabbix version: 7.2

Also available for: 7.4 7.0 6.4 6.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/jira_datacenter_jmx?at=release/7.2

Jira Data Center by JMX

Overview

This template is used for monitoring Jira Data Center health. It is designed for standalone operation for on-premises Jira installations.

Requirements

Zabbix version: 7.2 and higher.

Tested versions

This template has been tested on:

Jira Data Center 9.14.1
Jira Data Center 9.12.4

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Metrics are collected by JMX. 0. Deploy the Zabbix Java Gateway component (instructions).

Enable and configure JMX access to Jira Data Center. See documentation for instructions.
Assign the "Jira Data Center by JMX" template to the host with a JMX interface.
If your Jira installation requires authentication for JMX, set the values in the host macros {$JMX.USERNAME} and {$JMX.PASSWORD}.
(Optional) Set custom macro values and add macros with context for specific metrics following the macro description.
(Optional) Assign the "Generic Java JMX" template for garbage collector monitoring.
(Optional) Assign the "Apache Tomcat by JMX" template for web server monitoring.

Macros used

Name	Description	Default
{$JMX.USER}	User for JMX.
{$JMX.PASSWORD}	Password for JMX.
{$JIRA_DC.LICENSE.USER.CAPACITY.WARN}	User capacity warning threshold (%).	`80`
{$JIRA_DC.DB.CONNECTION.USAGE.WARN}	Warning threshold for database connections usage (%).	`80`
{$JIRA_DC.ISSUE.LATENCY.WARN}	Warning threshold for issue operation latency (in seconds).	`5`
{$JIRA_DC.STORAGE.LATENCY.WARN}	Warning threshold for storage write operation latency (in seconds).	`5`
{$JIRA_DC.INDEXING.LATENCY.WARN}	Warning threshold for indexing operation latency (in seconds).	`5`
{$JIRA_DC.LLD.FILTER.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`local\|share`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.INDEXING}	Used for indexing metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.INDEXING}	Used for indexing metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.ISSUE}	Used for issue discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.ISSUE}	Used for issue discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.MAIL}	Used for mail server connection metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.MAIL}	Used for mail server connection metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.LICENSE}	Used for license discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.LICENSE}	Used for license discovery.	`NO MATCH`

Items

Name	Description	Type	Key and additional info
DB: Connections: State	The state of the database connection.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value]
DB: Connections: Failed per minute	The count of database connection failures registered in one minute. Units: fpm - fails per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=failures,name=counter",Count] Preprocessing Simple change:
DB: Pool: Connections: Idle	Idle connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value]
DB: Pool: Connections: Active	Active connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numActive,name=value",Value]
DB: Reads	Database read operations from Jira per second. Units: rps - read operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.reads",invocation.count] Preprocessing Change per second:
DB: Writes	Database write operations from Jira per second. Units: wps - write operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.writes",invocation.count] Preprocessing Change per second:
DB: Connections: Limit	Total allowed database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal]
DB: Connections: Active	Active database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive]
DB: Connections: Latency	The latest measure of latency when querying the database.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=latency,name=value",Value]
License: Users: Get	License data for the discovery rule.	JMX agent	jmx.discovery[attributes,"com.atlassian.jira:type=jira.license"] Preprocessing JavaScript: `The text is too long. Please see the template.`
HTTP: Pool: Connections: Active	The latest measure of the number of active connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numActive,name=value",Value]
HTTP: Pool: Connections: Idle	The latest measure of the number of idle connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value]
HTTP: Sessions: Active	The latest measure of the number of active user sessions.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=sessions,category03=active,name=value",Value]
HTTP: Requests per minute	The latest measure of the total number of HTTP requests per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=requests,name=value",Value]
Mail: Queue	The latest measure of the number of items in a mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value]
Mail: Queue: Error	The latest measure of the number of items in an error mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value]
Mail: Sent per minute	The latest measure of the number of emails sent by the SMTP server per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numEmailsSentPerMin,name=value",Value]
Mail: Processed per minute	The latest measure of the number of items processed by a mail queue per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItemsProcessedPerMin,name=value",Value]
Mail: Queue: Processing state	The latest indicator of the state of a mail queue job.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value]
Entity: Issues	The number of issues.	JMX agent	jmx["com.atlassian.jira:type=entity.issues.total",Value]
Entity: Attachments	The number of attachments.	JMX agent	jmx["com.atlassian.jira:type=entity.attachments.total",Value]
Entity: Components	The number of components.	JMX agent	jmx["com.atlassian.jira:type=entity.components.total",Value]
Entity: Custom fields	The number of custom fields.	JMX agent	jmx["com.atlassian.jira:type=entity.customfields.total",Value]
Entity: Filters	The number of filters.	JMX agent	jmx["com.atlassian.jira:type=entity.filters.total",Value]
Entity: Versions created	The number of versions created.	JMX agent	jmx["com.atlassian.jira:type=entity.versions.total",Value]
Issue: Search per minute	Issue searches performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.search.count",Value] Preprocessing Simple change:
Issue: Created per minute	Issues created per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.created.count",Value] Preprocessing Simple change:
Issue: Updates per minute	Issue updates performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.updated.count",Value] Preprocessing Simple change:
Quicksearch: Concurrent searches	The number of concurrent searches that are being performed in real-time by using the quick search.	JMX agent	jmx["com.atlassian.jira:type=quicksearch.concurrent.search",Value] Preprocessing Simple change:

Triggers

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: DB: Connection lost	Database connection lost	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value],3m)=0`	Average	Manual close: Yes
Jira Data Center: DB: Pool: Out of idle connections	Fires when out of idle connections in database pool for 5 minutes.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
Jira Data Center: DB: Connection usage is near the limit		`100*min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)/last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])>{$JIRA_DC.DB.CONNECTION.USAGE.WARN}`	Warning	Manual close: Yes
Jira Data Center: DB: Connection limit reached		`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)=last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])`	Warning	Manual close: Yes
Jira Data Center: HTTP: Pool: Out of idle connections	All available connections are utilized. It can cause outages for users as the system is unable to serve their requests.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
Jira Data Center: Mail: Queue: Doesn’t empty over an extended period	Might indicate SMTP performance or connection problems.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],30m)>0`	Warning	Manual close: Yes Depends on: Jira Data Center: Mail: Queue job is not running
Jira Data Center: Mail: Error queue contains one or more items	A mail queue attempts to resend items up to 10 times. If the operation fails for the 11th time, the items are put into an error mail queue. You can remove items from the error mail queue in one of the following ways: - Manually clear the whole error queue. - Manually resend all items from the error queue to a mail queue. You should pay attention to the cases where an error mail queue item gets back to an error mail queue after you resend the items manually. These cases might indicate permanent performance issues.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value],5m)>0`	Warning	Manual close: Yes
Jira Data Center: Mail: Queue job is not running	It should be running when its queue is not empty. Might indicate SMTP server connection problems.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value],15m)=0 and min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],15m)>0`	Average	Manual close: Yes

LLD rule Storage discovery

Name	Description	Type	Key and additional info
Storage discovery	Discovery of the Jira storage metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=home,category01=,category02=write,category03=latency,,name=value"]

Item prototypes for Storage discovery

Name Description Type Key and additional info

Storage [{#JMXCATEGORY01}]: Latency

Name	Description	Type	Key and additional info
Storage [{#JMXCATEGORY01}]: Latency	The median latency of writing a small file (~30 bytes) to `{#JMXCATEGORY01}`.	JMX agent	jmx["{#JMXOBJ}",Value] Preprocessing Custom multiplier: `0.001`

The median latency of writing a small file (~30 bytes) to {#JMXCATEGORY01}.

JMX agent

jmx["{#JMXOBJ}",Value]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Storage discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Storage [{#JMXCATEGORY01}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Value],5m)>{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`	Warning	Manual close: Yes

LLD rule Mail server discovery

Name	Description	Type	Key and additional info
Mail server discovery	Discovery of the Jira connected mail servers.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=mail,category01=,category02=connection,category03=state,name="]

Item prototypes for Mail server discovery

Name Description Type Key and additional info

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Connection state

Name	Description	Type	Key and additional info
Mail [{#JMXCATEGORY01},{#JMXNAME}]: Connection state	Shows connection state of Jira to discovered mail server: `{#JMXCATEGORY01}-{#JMXNAME}`	JMX agent	jmx["{#JMXOBJ}",Connected] Preprocessing Boolean to decimal:
Mail [{#JMXCATEGORY01},{#JMXNAME}]: Failures per minute	Count of failed connections to discovered mail server `{#JMXCATEGORY01}-{#JMXNAME}` per minute	JMX agent	jmx["{#JMXOBJ}",TotalFailures] Preprocessing Simple change:

Shows connection state of Jira to discovered mail server: {#JMXCATEGORY01}-{#JMXNAME}

JMX agent

jmx["{#JMXOBJ}",Connected]

Preprocessing

Boolean to decimal:

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Failures per minute

Count of failed connections to discovered mail server {#JMXCATEGORY01}-{#JMXNAME} per minute

JMX agent

jmx["{#JMXOBJ}",TotalFailures]

Preprocessing

Simple change:

Trigger prototypes for Mail server discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Mail [{#JMXCATEGORY01}-{#JMXNAME}]: Server disconnected	Trigger is fired when discovered mail server `{#JMXCATEGORY01}-{#JMXNAME}` becomes unavailable	`max(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Connected],5m)=0`	Average	Manual close: Yes

LLD rule Indexing latency discovery

Name	Description	Type	Key and additional info
Indexing latency discovery	Discovery of the Jira indexing metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=indexing,name=*"]

Item prototypes for Indexing latency discovery

Name Description Type Key and additional info

Indexing [{#JMXNAME}]: Latency

Name	Description	Type	Key and additional info
Indexing [{#JMXNAME}]: Latency	Average time spent on indexing operations.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean] Preprocessing Custom multiplier: `0.001`

Average time spent on indexing operations.

JMX agent

jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Indexing latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Indexing [{#JMXNAME}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean],5m)>{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule Issue latency discovery

Name	Description	Type	Key and additional info
Issue latency discovery	Discovery of the Jira issue latency metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=issue,name=*"]

Item prototypes for Issue latency discovery

Name Description Type Key and additional info

Issue [{#JMXNAME}]: Latency

Name	Description	Type	Key and additional info
Issue [{#JMXNAME}]: Latency	Average time spent on issue `{#JMXNAME}` operations.	JMX agent	jmx["{#JMXOBJ}",Mean] Preprocessing Custom multiplier: `0.001`

Average time spent on issue {#JMXNAME} operations.

JMX agent

jmx["{#JMXOBJ}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Issue latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Issue [{#JMXNAME}]: Slow operations	Fires when latency grows above the threshold: `{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Mean],5m)>{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule License discovery

Name Description Type Key and additional info

License discovery

Name	Description	Type	Key and additional info
License discovery	Discovery of the Jira licenses.	Dependent item	jmx.license.discovery Preprocessing JavaScript: `The text is too long. Please see the template.` Discard unchanged with heartbeat: `1h`

Discovery of the Jira licenses.

Dependent item

jmx.license.discovery

Preprocessing

JavaScript: The text is too long. Please see the template.
Discard unchanged with heartbeat: 1h

Item prototypes for License discovery

Name Description Type Key and additional info

License [{#LICENSE.TYPE}]: Users: Current

Name	Description	Type	Key and additional info
License [{#LICENSE.TYPE}]: Users: Current	Current user count for `{#LICENSE.TYPE}`.	Dependent item	jmx.license.get.user.current["{#LICENSE.TYPE}"] Preprocessing JSON Path: `$.{#LICENSE.TYPE}.properties.current_user_count`
License [{#LICENSE.TYPE}]: Users: Maximum	User count limit for `{#LICENSE.TYPE}`. `-1` = No limits for the license type.	Dependent item	jmx.license.get.user.max["{#LICENSE.TYPE}"] Preprocessing JSON Path: `$.{#LICENSE.TYPE}.properties.max_user_count`

Current user count for {#LICENSE.TYPE}.

Dependent item

jmx.license.get.user.current["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.current_user_count

License [{#LICENSE.TYPE}]: Users: Maximum

User count limit for {#LICENSE.TYPE}.

-1 = No limits for the license type.

Dependent item

jmx.license.get.user.max["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.max_user_count

Trigger prototypes for License discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: License [{#LICENSE.TYPE}]: Low user capacity	Fires when relative user quantity grows above the threshold: `{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"}`%	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * (100*last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"])/last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"})`	Warning	Manual close: Yes Depends on: Jira Data Center: License [{#LICENSE.TYPE}]: User count reached the limit
Jira Data Center: License [{#LICENSE.TYPE}]: User count reached the limit	Fires when user quantity reaches the limit. It won't fire if the limit is disabled (set to `-1`).	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * ((last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])-last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"]))<=0)`	Average	Manual close: Yes

Feedback

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

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

This template is for Zabbix version: 7.0

Also available for: 7.4 7.2 6.4 6.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/jira_datacenter_jmx?at=release/7.0

Jira Data Center by JMX

Overview

This template is used for monitoring Jira Data Center health. It is designed for standalone operation for on-premises Jira installations.

Requirements

Zabbix version: 7.0 and higher.

Tested versions

This template has been tested on:

Jira Data Center 9.14.1
Jira Data Center 9.12.4

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Metrics are collected by JMX. 0. Deploy the Zabbix Java Gateway component (instructions).

Enable and configure JMX access to Jira Data Center. See documentation for instructions.
Assign the "Jira Data Center by JMX" template to the host with a JMX interface.
If your Jira installation requires authentication for JMX, set the values in the host macros {$JMX.USERNAME} and {$JMX.PASSWORD}.
(Optional) Set custom macro values and add macros with context for specific metrics following the macro description.
(Optional) Assign the "Generic Java JMX" template for garbage collector monitoring.
(Optional) Assign the "Apache Tomcat by JMX" template for web server monitoring.

Macros used

Name	Description	Default
{$JMX.USER}	User for JMX.
{$JMX.PASSWORD}	Password for JMX.
{$JIRA_DC.LICENSE.USER.CAPACITY.WARN}	User capacity warning threshold (%).	`80`
{$JIRA_DC.DB.CONNECTION.USAGE.WARN}	Warning threshold for database connections usage (%).	`80`
{$JIRA_DC.ISSUE.LATENCY.WARN}	Warning threshold for issue operation latency (in seconds).	`5`
{$JIRA_DC.STORAGE.LATENCY.WARN}	Warning threshold for storage write operation latency (in seconds).	`5`
{$JIRA_DC.INDEXING.LATENCY.WARN}	Warning threshold for indexing operation latency (in seconds).	`5`
{$JIRA_DC.LLD.FILTER.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`local\|share`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.INDEXING}	Used for indexing metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.INDEXING}	Used for indexing metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.ISSUE}	Used for issue discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.ISSUE}	Used for issue discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.MAIL}	Used for mail server connection metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.MAIL}	Used for mail server connection metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.LICENSE}	Used for license discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.LICENSE}	Used for license discovery.	`NO MATCH`

Items

Name	Description	Type	Key and additional info
DB: Connections: State	The state of the database connection.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value]
DB: Connections: Failed per minute	The count of database connection failures registered in one minute. Units: fpm - fails per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=failures,name=counter",Count] Preprocessing Simple change:
DB: Pool: Connections: Idle	Idle connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value]
DB: Pool: Connections: Active	Active connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numActive,name=value",Value]
DB: Reads	Database read operations from Jira per second. Units: rps - read operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.reads",invocation.count] Preprocessing Change per second:
DB: Writes	Database write operations from Jira per second. Units: wps - write operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.writes",invocation.count] Preprocessing Change per second:
DB: Connections: Limit	Total allowed database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal]
DB: Connections: Active	Active database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive]
DB: Connections: Latency	The latest measure of latency when querying the database.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=latency,name=value",Value]
License: Users: Get	License data for the discovery rule.	JMX agent	jmx.discovery[attributes,"com.atlassian.jira:type=jira.license"] Preprocessing JavaScript: `The text is too long. Please see the template.`
HTTP: Pool: Connections: Active	The latest measure of the number of active connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numActive,name=value",Value]
HTTP: Pool: Connections: Idle	The latest measure of the number of idle connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value]
HTTP: Sessions: Active	The latest measure of the number of active user sessions.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=sessions,category03=active,name=value",Value]
HTTP: Requests per minute	The latest measure of the total number of HTTP requests per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=requests,name=value",Value]
Mail: Queue	The latest measure of the number of items in a mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value]
Mail: Queue: Error	The latest measure of the number of items in an error mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value]
Mail: Sent per minute	The latest measure of the number of emails sent by the SMTP server per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numEmailsSentPerMin,name=value",Value]
Mail: Processed per minute	The latest measure of the number of items processed by a mail queue per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItemsProcessedPerMin,name=value",Value]
Mail: Queue: Processing state	The latest indicator of the state of a mail queue job.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value]
Entity: Issues	The number of issues.	JMX agent	jmx["com.atlassian.jira:type=entity.issues.total",Value]
Entity: Attachments	The number of attachments.	JMX agent	jmx["com.atlassian.jira:type=entity.attachments.total",Value]
Entity: Components	The number of components.	JMX agent	jmx["com.atlassian.jira:type=entity.components.total",Value]
Entity: Custom fields	The number of custom fields.	JMX agent	jmx["com.atlassian.jira:type=entity.customfields.total",Value]
Entity: Filters	The number of filters.	JMX agent	jmx["com.atlassian.jira:type=entity.filters.total",Value]
Entity: Versions created	The number of versions created.	JMX agent	jmx["com.atlassian.jira:type=entity.versions.total",Value]
Issue: Search per minute	Issue searches performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.search.count",Value] Preprocessing Simple change:
Issue: Created per minute	Issues created per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.created.count",Value] Preprocessing Simple change:
Issue: Updates per minute	Issue updates performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.updated.count",Value] Preprocessing Simple change:
Quicksearch: Concurrent searches	The number of concurrent searches that are being performed in real-time by using the quick search.	JMX agent	jmx["com.atlassian.jira:type=quicksearch.concurrent.search",Value] Preprocessing Simple change:

Triggers

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: DB: Connection lost	Database connection lost	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value],3m)=0`	Average	Manual close: Yes
Jira Data Center: DB: Pool: Out of idle connections	Fires when out of idle connections in database pool for 5 minutes.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
Jira Data Center: DB: Connection usage is near the limit		`100*min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)/last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])>{$JIRA_DC.DB.CONNECTION.USAGE.WARN}`	Warning	Manual close: Yes
Jira Data Center: DB: Connection limit reached		`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)=last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])`	Warning	Manual close: Yes
Jira Data Center: HTTP: Pool: Out of idle connections	All available connections are utilized. It can cause outages for users as the system is unable to serve their requests.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
Jira Data Center: Mail: Queue: Doesn’t empty over an extended period	Might indicate SMTP performance or connection problems.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],30m)>0`	Warning	Manual close: Yes Depends on: Jira Data Center: Mail: Queue job is not running
Jira Data Center: Mail: Error queue contains one or more items	A mail queue attempts to resend items up to 10 times. If the operation fails for the 11th time, the items are put into an error mail queue. You can remove items from the error mail queue in one of the following ways: - Manually clear the whole error queue. - Manually resend all items from the error queue to a mail queue. You should pay attention to the cases where an error mail queue item gets back to an error mail queue after you resend the items manually. These cases might indicate permanent performance issues.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value],5m)>0`	Warning	Manual close: Yes
Jira Data Center: Mail: Queue job is not running	It should be running when its queue is not empty. Might indicate SMTP server connection problems.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value],15m)=0 and min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],15m)>0`	Average	Manual close: Yes

LLD rule Storage discovery

Name	Description	Type	Key and additional info
Storage discovery	Discovery of the Jira storage metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=home,category01=,category02=write,category03=latency,,name=value"]

Item prototypes for Storage discovery

Name Description Type Key and additional info

Storage [{#JMXCATEGORY01}]: Latency

Name	Description	Type	Key and additional info
Storage [{#JMXCATEGORY01}]: Latency	The median latency of writing a small file (~30 bytes) to `{#JMXCATEGORY01}`.	JMX agent	jmx["{#JMXOBJ}",Value] Preprocessing Custom multiplier: `0.001`

The median latency of writing a small file (~30 bytes) to {#JMXCATEGORY01}.

JMX agent

jmx["{#JMXOBJ}",Value]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Storage discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Storage [{#JMXCATEGORY01}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Value],5m)>{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`	Warning	Manual close: Yes

LLD rule Mail server discovery

Name	Description	Type	Key and additional info
Mail server discovery	Discovery of the Jira connected mail servers.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=mail,category01=,category02=connection,category03=state,name="]

Item prototypes for Mail server discovery

Name Description Type Key and additional info

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Connection state

Name	Description	Type	Key and additional info
Mail [{#JMXCATEGORY01},{#JMXNAME}]: Connection state	Shows connection state of Jira to discovered mail server: `{#JMXCATEGORY01}-{#JMXNAME}`	JMX agent	jmx["{#JMXOBJ}",Connected] Preprocessing Boolean to decimal:
Mail [{#JMXCATEGORY01},{#JMXNAME}]: Failures per minute	Count of failed connections to discovered mail server `{#JMXCATEGORY01}-{#JMXNAME}` per minute	JMX agent	jmx["{#JMXOBJ}",TotalFailures] Preprocessing Simple change:

Shows connection state of Jira to discovered mail server: {#JMXCATEGORY01}-{#JMXNAME}

JMX agent

jmx["{#JMXOBJ}",Connected]

Preprocessing

Boolean to decimal:

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Failures per minute

Count of failed connections to discovered mail server {#JMXCATEGORY01}-{#JMXNAME} per minute

JMX agent

jmx["{#JMXOBJ}",TotalFailures]

Preprocessing

Simple change:

Trigger prototypes for Mail server discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Mail [{#JMXCATEGORY01}-{#JMXNAME}]: Server disconnected	Trigger is fired when discovered mail server `{#JMXCATEGORY01}-{#JMXNAME}` becomes unavailable	`max(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Connected],5m)=0`	Average	Manual close: Yes

LLD rule Indexing latency discovery

Name	Description	Type	Key and additional info
Indexing latency discovery	Discovery of the Jira indexing metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=indexing,name=*"]

Item prototypes for Indexing latency discovery

Name Description Type Key and additional info

Indexing [{#JMXNAME}]: Latency

Average time spent on indexing operations.

JMX agent

jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Indexing latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Indexing [{#JMXNAME}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean],5m)>{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule Issue latency discovery

Name	Description	Type	Key and additional info
Issue latency discovery	Discovery of the Jira issue latency metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=issue,name=*"]

Item prototypes for Issue latency discovery

Name Description Type Key and additional info

Issue [{#JMXNAME}]: Latency

Average time spent on issue {#JMXNAME} operations.

JMX agent

jmx["{#JMXOBJ}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Issue latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: Issue [{#JMXNAME}]: Slow operations	Fires when latency grows above the threshold: `{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Mean],5m)>{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule License discovery

Name Description Type Key and additional info

License discovery

Discovery of the Jira licenses.

Dependent item

jmx.license.discovery

Preprocessing

JavaScript: The text is too long. Please see the template.
Discard unchanged with heartbeat: 1h

Item prototypes for License discovery

Name Description Type Key and additional info

License [{#LICENSE.TYPE}]: Users: Current

Current user count for {#LICENSE.TYPE}.

Dependent item

jmx.license.get.user.current["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.current_user_count

License [{#LICENSE.TYPE}]: Users: Maximum

User count limit for {#LICENSE.TYPE}.

-1 = No limits for the license type.

Dependent item

jmx.license.get.user.max["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.max_user_count

Trigger prototypes for License discovery

Name	Description	Expression	Severity	Dependencies and additional info
Jira Data Center: License [{#LICENSE.TYPE}]: Low user capacity	Fires when relative user quantity grows above the threshold: `{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"}`%	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * (100*last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"])/last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"})`	Warning	Manual close: Yes Depends on: Jira Data Center: License [{#LICENSE.TYPE}]: User count reached the limit
Jira Data Center: License [{#LICENSE.TYPE}]: User count reached the limit	Fires when user quantity reaches the limit. It won't fire if the limit is disabled (set to `-1`).	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * ((last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])-last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"]))<=0)`	Average	Manual close: Yes

Feedback

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

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

This template is for Zabbix version: 6.4

Also available for: 7.4 7.2 7.0 6.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/jira_datacenter_jmx?at=release/6.4

Jira Data Center by JMX

Overview

This template is used for monitoring Jira Data Center health. It is designed for standalone operation for on-premises Jira installations.

Requirements

Zabbix version: 6.4 and higher.

Tested versions

This template has been tested on:

Jira Data Center 9.14.1
Jira Data Center 9.12.4

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Metrics are collected by JMX. 0. Deploy the Zabbix Java Gateway component (instructions).

Enable and configure JMX access to Jira Data Center. See documentation for instructions.
Assign the "Jira Data Center by JMX" template to the host with a JMX interface.
If your Jira installation requires authentication for JMX, set the values in the host macros {$JMX.USERNAME} and {$JMX.PASSWORD}.
(Optional) Set custom macro values and add macros with context for specific metrics following the macro description.
(Optional) Assign the "Generic Java JMX" template for garbage collector monitoring.
(Optional) Assign the "Apache Tomcat by JMX" template for web server monitoring.

Macros used

Name	Description	Default
{$JMX.USER}	User for JMX.
{$JMX.PASSWORD}	Password for JMX.
{$JIRA_DC.LICENSE.USER.CAPACITY.WARN}	User capacity warning threshold (%).	`80`
{$JIRA_DC.DB.CONNECTION.USAGE.WARN}	Warning threshold for database connections usage (%).	`80`
{$JIRA_DC.ISSUE.LATENCY.WARN}	Warning threshold for issue operation latency (in seconds).	`5`
{$JIRA_DC.STORAGE.LATENCY.WARN}	Warning threshold for storage write operation latency (in seconds).	`5`
{$JIRA_DC.INDEXING.LATENCY.WARN}	Warning threshold for indexing operation latency (in seconds).	`5`
{$JIRA_DC.LLD.FILTER.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`local\|share`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.INDEXING}	Used for indexing metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.INDEXING}	Used for indexing metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.ISSUE}	Used for issue discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.ISSUE}	Used for issue discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.MAIL}	Used for mail server connection metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.MAIL}	Used for mail server connection metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.LICENSE}	Used for license discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.LICENSE}	Used for license discovery.	`NO MATCH`

Items

Name	Description	Type	Key and additional info
DB: Connections: State	The state of the database connection.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value]
DB: Connections: Failed per minute	The count of database connection failures registered in one minute. Units: fpm - fails per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=failures,name=counter",Count] Preprocessing Simple change:
DB: Pool: Connections: Idle	Idle connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value]
DB: Pool: Connections: Active	Active connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numActive,name=value",Value]
DB: Reads	Database read operations from Jira per second. Units: rps - read operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.reads",invocation.count] Preprocessing Change per second:
DB: Writes	Database write operations from Jira per second. Units: wps - write operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.writes",invocation.count] Preprocessing Change per second:
DB: Connections: Limit	Total allowed database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal]
DB: Connections: Active	Active database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive]
DB: Connections: Latency	The latest measure of latency when querying the database.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=latency,name=value",Value]
License: Users: Get	License data for the discovery rule.	JMX agent	jmx.discovery[attributes,"com.atlassian.jira:type=jira.license"] Preprocessing JavaScript: `The text is too long. Please see the template.`
HTTP: Pool: Connections: Active	The latest measure of the number of active connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numActive,name=value",Value]
HTTP: Pool: Connections: Idle	The latest measure of the number of idle connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value]
HTTP: Sessions: Active	The latest measure of the number of active user sessions.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=sessions,category03=active,name=value",Value]
HTTP: Requests per minute	The latest measure of the total number of HTTP requests per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=requests,name=value",Value]
Mail: Queue	The latest measure of the number of items in a mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value]
Mail: Queue: Error	The latest measure of the number of items in an error mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value]
Mail: Sent per minute	The latest measure of the number of emails sent by the SMTP server per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numEmailsSentPerMin,name=value",Value]
Mail: Processed per minute	The latest measure of the number of items processed by a mail queue per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItemsProcessedPerMin,name=value",Value]
Mail: Queue: Processing state	The latest indicator of the state of a mail queue job.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value]
Entity: Issues	The number of issues.	JMX agent	jmx["com.atlassian.jira:type=entity.issues.total",Value]
Entity: Attachments	The number of attachments.	JMX agent	jmx["com.atlassian.jira:type=entity.attachments.total",Value]
Entity: Components	The number of components.	JMX agent	jmx["com.atlassian.jira:type=entity.components.total",Value]
Entity: Custom fields	The number of custom fields.	JMX agent	jmx["com.atlassian.jira:type=entity.customfields.total",Value]
Entity: Filters	The number of filters.	JMX agent	jmx["com.atlassian.jira:type=entity.filters.total",Value]
Entity: Versions created	The number of versions created.	JMX agent	jmx["com.atlassian.jira:type=entity.versions.total",Value]
Issue: Search per minute	Issue searches performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.search.count",Value] Preprocessing Simple change:
Issue: Created per minute	Issues created per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.created.count",Value] Preprocessing Simple change:
Issue: Updates per minute	Issue updates performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.updated.count",Value] Preprocessing Simple change:
Quicksearch: Concurrent searches	The number of concurrent searches that are being performed in real-time by using the quick search.	JMX agent	jmx["com.atlassian.jira:type=quicksearch.concurrent.search",Value] Preprocessing Simple change:

Triggers

Name	Description	Expression	Severity	Dependencies and additional info
DB: Connection lost	Database connection lost	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value],3m)=0`	Average	Manual close: Yes
DB: Pool: Out of idle connections	Fires when out of idle connections in database pool for 5 minutes.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
DB: Connection usage is near the limit		`100*min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)/last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])>{$JIRA_DC.DB.CONNECTION.USAGE.WARN}`	Warning	Manual close: Yes
DB: Connection limit reached		`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)=last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])`	Warning	Manual close: Yes
HTTP: Pool: Out of idle connections	All available connections are utilized. It can cause outages for users as the system is unable to serve their requests.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
Mail: Queue: Doesn’t empty over an extended period	Might indicate SMTP performance or connection problems.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],30m)>0`	Warning	Manual close: Yes Depends on: Mail: Queue job is not running
Mail: Error queue contains one or more items	A mail queue attempts to resend items up to 10 times. If the operation fails for the 11th time, the items are put into an error mail queue. You can remove items from the error mail queue in one of the following ways: - Manually clear the whole error queue. - Manually resend all items from the error queue to a mail queue. You should pay attention to the cases where an error mail queue item gets back to an error mail queue after you resend the items manually. These cases might indicate permanent performance issues.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value],5m)>0`	Warning	Manual close: Yes
Mail: Queue job is not running	It should be running when its queue is not empty. Might indicate SMTP server connection problems.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value],15m)=0 and min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],15m)>0`	Average	Manual close: Yes

LLD rule Storage discovery

Name	Description	Type	Key and additional info
Storage discovery	Discovery of the Jira storage metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=home,category01=,category02=write,category03=latency,,name=value"]

Item prototypes for Storage discovery

Name Description Type Key and additional info

Storage [{#JMXCATEGORY01}]: Latency

The median latency of writing a small file (~30 bytes) to {#JMXCATEGORY01}.

JMX agent

jmx["{#JMXOBJ}",Value]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Storage discovery

Name	Description	Expression	Severity	Dependencies and additional info
Storage [{#JMXCATEGORY01}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Value],5m)>{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`	Warning	Manual close: Yes

LLD rule Mail server discovery

Name	Description	Type	Key and additional info
Mail server discovery	Discovery of the Jira connected mail servers.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=mail,category01=,category02=connection,category03=state,name="]

Item prototypes for Mail server discovery

Name Description Type Key and additional info

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Connection state

Shows connection state of Jira to discovered mail server: {#JMXCATEGORY01}-{#JMXNAME}

JMX agent

jmx["{#JMXOBJ}",Connected]

Preprocessing

Boolean to decimal:

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Failures per minute

Count of failed connections to discovered mail server {#JMXCATEGORY01}-{#JMXNAME} per minute

JMX agent

jmx["{#JMXOBJ}",TotalFailures]

Preprocessing

Simple change:

Trigger prototypes for Mail server discovery

Name	Description	Expression	Severity	Dependencies and additional info
Mail [{#JMXCATEGORY01}-{#JMXNAME}]: Server disconnected	Trigger is fired when discovered mail server `{#JMXCATEGORY01}-{#JMXNAME}` becomes unavailable	`max(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Connected],5m)=0`	Average	Manual close: Yes

LLD rule Indexing latency discovery

Name	Description	Type	Key and additional info
Indexing latency discovery	Discovery of the Jira indexing metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=indexing,name=*"]

Item prototypes for Indexing latency discovery

Name Description Type Key and additional info

Indexing [{#JMXNAME}]: Latency

Average time spent on indexing operations.

JMX agent

jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Indexing latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Indexing [{#JMXNAME}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean],5m)>{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule Issue latency discovery

Name	Description	Type	Key and additional info
Issue latency discovery	Discovery of the Jira issue latency metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=issue,name=*"]

Item prototypes for Issue latency discovery

Name Description Type Key and additional info

Issue [{#JMXNAME}]: Latency

Average time spent on issue {#JMXNAME} operations.

JMX agent

jmx["{#JMXOBJ}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Issue latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Issue [{#JMXNAME}]: Slow operations	Fires when latency grows above the threshold: `{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Mean],5m)>{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule License discovery

Name Description Type Key and additional info

License discovery

Discovery of the Jira licenses.

Dependent item

jmx.license.discovery

Preprocessing

JavaScript: The text is too long. Please see the template.
Discard unchanged with heartbeat: 1h

Item prototypes for License discovery

Name Description Type Key and additional info

License [{#LICENSE.TYPE}]: Users: Current

Current user count for {#LICENSE.TYPE}.

Dependent item

jmx.license.get.user.current["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.current_user_count

License [{#LICENSE.TYPE}]: Users: Maximum

User count limit for {#LICENSE.TYPE}.

-1 = No limits for the license type.

Dependent item

jmx.license.get.user.max["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.max_user_count

Trigger prototypes for License discovery

Name	Description	Expression	Severity	Dependencies and additional info
License [{#LICENSE.TYPE}]: Low user capacity	Fires when relative user quantity grows above the threshold: `{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"}`%	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * (100*last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"])/last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"})`	Warning	Manual close: Yes Depends on: License [{#LICENSE.TYPE}]: User count reached the limit
License [{#LICENSE.TYPE}]: User count reached the limit	Fires when user quantity reaches the limit. It won't fire if the limit is disabled (set to `-1`).	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * ((last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])-last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"]))<=0)`	Average	Manual close: Yes

Feedback

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

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

This template is for Zabbix version: 6.0

Also available for: 7.4 7.2 7.0 6.4

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/jira_datacenter_jmx?at=release/6.0

Jira Data Center by JMX

Overview

This template is used for monitoring Jira Data Center health. It is designed for standalone operation for on-premises Jira installations.

Requirements

Zabbix version: 6.0 and higher.

Tested versions

This template has been tested on:

Jira Data Center 9.14.1
Jira Data Center 9.12.4

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Metrics are collected by JMX. 0. Deploy the Zabbix Java Gateway component (instructions).

Enable and configure JMX access to Jira Data Center. See documentation for instructions.
Assign the "Jira Data Center by JMX" template to the host with a JMX interface.
If your Jira installation requires authentication for JMX, set the values in the host macros {$JMX.USERNAME} and {$JMX.PASSWORD}.
(Optional) Set custom macro values and add macros with context for specific metrics following the macro description.
(Optional) Assign the "Generic Java JMX" template for garbage collector monitoring.
(Optional) Assign the "Apache Tomcat by JMX" template for web server monitoring.

Macros used

Name	Description	Default
{$JMX.USER}	User for JMX.
{$JMX.PASSWORD}	Password for JMX.
{$JIRA_DC.LICENSE.USER.CAPACITY.WARN}	User capacity warning threshold (%).	`80`
{$JIRA_DC.DB.CONNECTION.USAGE.WARN}	Warning threshold for database connections usage (%).	`80`
{$JIRA_DC.ISSUE.LATENCY.WARN}	Warning threshold for issue operation latency (in seconds).	`5`
{$JIRA_DC.STORAGE.LATENCY.WARN}	Warning threshold for storage write operation latency (in seconds).	`5`
{$JIRA_DC.INDEXING.LATENCY.WARN}	Warning threshold for indexing operation latency (in seconds).	`5`
{$JIRA_DC.LLD.FILTER.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`local\|share`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.HOMEFOLDERS}	Used for storage metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.INDEXING}	Used for indexing metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.INDEXING}	Used for indexing metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.ISSUE}	Used for issue discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.ISSUE}	Used for issue discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.MAIL}	Used for mail server connection metric discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.MAIL}	Used for mail server connection metric discovery.	`NO MATCH`
{$JIRA_DC.LLD.FILTER.MATCHES.LICENSE}	Used for license discovery.	`.*`
{$JIRA_DC.LLD.FILTER.NOT.MATCHES.LICENSE}	Used for license discovery.	`NO MATCH`

Items

Name	Description	Type	Key and additional info
DB: Connections: State	The state of the database connection.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value]
DB: Connections: Failed per minute	The count of database connection failures registered in one minute. Units: fpm - fails per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=failures,name=counter",Count] Preprocessing Simple change:
DB: Pool: Connections: Idle	Idle connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value]
DB: Pool: Connections: Active	Active connection count of the database pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numActive,name=value",Value]
DB: Reads	Database read operations from Jira per second. Units: rps - read operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.reads",invocation.count] Preprocessing Change per second:
DB: Writes	Database write operations from Jira per second. Units: wps - write operations per second.	JMX agent	jmx["com.atlassian.jira:type=db.writes",invocation.count] Preprocessing Change per second:
DB: Connections: Limit	Total allowed database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal]
DB: Connections: Active	Active database connection count.	JMX agent	jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive]
DB: Connections: Latency	The latest measure of latency when querying the database.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=latency,name=value",Value]
License: Users: Get	License data for the discovery rule.	JMX agent	jmx.discovery[attributes,"com.atlassian.jira:type=jira.license"] Preprocessing JavaScript: `The text is too long. Please see the template.`
HTTP: Pool: Connections: Active	The latest measure of the number of active connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numActive,name=value",Value]
HTTP: Pool: Connections: Idle	The latest measure of the number of idle connections in the HTTP connection pool.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value]
HTTP: Sessions: Active	The latest measure of the number of active user sessions.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=sessions,category03=active,name=value",Value]
HTTP: Requests per minute	The latest measure of the total number of HTTP requests per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=http,category01=requests,name=value",Value]
Mail: Queue	The latest measure of the number of items in a mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value]
Mail: Queue: Error	The latest measure of the number of items in an error mail queue.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value]
Mail: Sent per minute	The latest measure of the number of emails sent by the SMTP server per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numEmailsSentPerMin,name=value",Value]
Mail: Processed per minute	The latest measure of the number of items processed by a mail queue per minute.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItemsProcessedPerMin,name=value",Value]
Mail: Queue: Processing state	The latest indicator of the state of a mail queue job.	JMX agent	jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value]
Entity: Issues	The number of issues.	JMX agent	jmx["com.atlassian.jira:type=entity.issues.total",Value]
Entity: Attachments	The number of attachments.	JMX agent	jmx["com.atlassian.jira:type=entity.attachments.total",Value]
Entity: Components	The number of components.	JMX agent	jmx["com.atlassian.jira:type=entity.components.total",Value]
Entity: Custom fields	The number of custom fields.	JMX agent	jmx["com.atlassian.jira:type=entity.customfields.total",Value]
Entity: Filters	The number of filters.	JMX agent	jmx["com.atlassian.jira:type=entity.filters.total",Value]
Entity: Versions created	The number of versions created.	JMX agent	jmx["com.atlassian.jira:type=entity.versions.total",Value]
Issue: Search per minute	Issue searches performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.search.count",Value] Preprocessing Simple change:
Issue: Created per minute	Issues created per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.created.count",Value] Preprocessing Simple change:
Issue: Updates per minute	Issue updates performed per minute.	JMX agent	jmx["com.atlassian.jira:type=issue.updated.count",Value] Preprocessing Simple change:
Quicksearch: Concurrent searches	The number of concurrent searches that are being performed in real-time by using the quick search.	JMX agent	jmx["com.atlassian.jira:type=quicksearch.concurrent.search",Value] Preprocessing Simple change:

Triggers

Name	Description	Expression	Severity	Dependencies and additional info
DB: Connection lost	Database connection lost	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=state,name=value",Value],3m)=0`	Average	Manual close: Yes
DB: Pool: Out of idle connections	Fires when out of idle connections in database pool for 5 minutes.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=db,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
DB: Connection usage is near the limit		`100*min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)/last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])>{$JIRA_DC.DB.CONNECTION.USAGE.WARN}`	Warning	Manual close: Yes
DB: Connection limit reached		`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",NumActive],5m)=last(/Jira Data Center by JMX/jmx["com.atlassian.jira:name=BasicDataSource,connectionpool=connections",MaxTotal])`	Warning	Manual close: Yes
HTTP: Pool: Out of idle connections	All available connections are utilized. It can cause outages for users as the system is unable to serve their requests.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=http,category01=connection,category02=pool,category03=numIdle,name=value",Value],5m)<=0`	Warning	Manual close: Yes
Mail: Queue: Doesn’t empty over an extended period	Might indicate SMTP performance or connection problems.	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],30m)>0`	Warning	Manual close: Yes Depends on: Mail: Queue job is not running
Mail: Error queue contains one or more items	A mail queue attempts to resend items up to 10 times. If the operation fails for the 11th time, the items are put into an error mail queue. You can remove items from the error mail queue in one of the following ways: - Manually clear the whole error queue. - Manually resend all items from the error queue to a mail queue. You should pay attention to the cases where an error mail queue item gets back to an error mail queue after you resend the items manually. These cases might indicate permanent performance issues.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numErrors,name=value",Value],5m)>0`	Warning	Manual close: Yes
Mail: Queue job is not running	It should be running when its queue is not empty. Might indicate SMTP server connection problems.	`max(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=jobRunning,name=value",Value],15m)=0 and min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=mail,category01=queue,category02=numItems,name=value",Value],15m)>0`	Average	Manual close: Yes

LLD rule Storage discovery

Name	Description	Type	Key and additional info
Storage discovery	Discovery of the Jira storage metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=home,category01=,category02=write,category03=latency,,name=value"]

Item prototypes for Storage discovery

Name Description Type Key and additional info

Storage [{#JMXCATEGORY01}]: Latency

The median latency of writing a small file (~30 bytes) to {#JMXCATEGORY01}.

JMX agent

jmx["{#JMXOBJ}",Value]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Storage discovery

Name	Description	Expression	Severity	Dependencies and additional info
Storage [{#JMXCATEGORY01}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Value],5m)>{$JIRA_DC.STORAGE.LATENCY.WARN:"{#JMXCATEGORY01}"}`	Warning	Manual close: Yes

LLD rule Mail server discovery

Name	Description	Type	Key and additional info
Mail server discovery	Discovery of the Jira connected mail servers.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=mail,category01=,category02=connection,category03=state,name="]

Item prototypes for Mail server discovery

Name Description Type Key and additional info

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Connection state

Shows connection state of Jira to discovered mail server: {#JMXCATEGORY01}-{#JMXNAME}

JMX agent

jmx["{#JMXOBJ}",Connected]

Preprocessing

Boolean to decimal:

Mail [{#JMXCATEGORY01},{#JMXNAME}]: Failures per minute

Count of failed connections to discovered mail server {#JMXCATEGORY01}-{#JMXNAME} per minute

JMX agent

jmx["{#JMXOBJ}",TotalFailures]

Preprocessing

Simple change:

Trigger prototypes for Mail server discovery

Name	Description	Expression	Severity	Dependencies and additional info
Mail [{#JMXCATEGORY01}-{#JMXNAME}]: Server disconnected	Trigger is fired when discovered mail server `{#JMXCATEGORY01}-{#JMXNAME}` becomes unavailable	`max(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Connected],5m)=0`	Average	Manual close: Yes

LLD rule Indexing latency discovery

Name	Description	Type	Key and additional info
Indexing latency discovery	Discovery of the Jira indexing metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=indexing,name=*"]

Item prototypes for Indexing latency discovery

Name Description Type Key and additional info

Indexing [{#JMXNAME}]: Latency

Average time spent on indexing operations.

JMX agent

jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Indexing latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Indexing [{#JMXNAME}]: Slow performance	Fires when latency grows above the threshold: `{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["com.atlassian.jira:type=metrics,category00=indexing,name={#JMXNAME}",Mean],5m)>{$JIRA_DC.INDEXING.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule Issue latency discovery

Name	Description	Type	Key and additional info
Issue latency discovery	Discovery of the Jira issue latency metrics.	JMX agent	jmx.discovery[beans,"com.atlassian.jira:type=metrics,category00=issue,name=*"]

Item prototypes for Issue latency discovery

Name Description Type Key and additional info

Issue [{#JMXNAME}]: Latency

Average time spent on issue {#JMXNAME} operations.

JMX agent

jmx["{#JMXOBJ}",Mean]

Preprocessing

Custom multiplier: 0.001

Trigger prototypes for Issue latency discovery

Name	Description	Expression	Severity	Dependencies and additional info
Issue [{#JMXNAME}]: Slow operations	Fires when latency grows above the threshold: `{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`s	`min(/Jira Data Center by JMX/jmx["{#JMXOBJ}",Mean],5m)>{$JIRA_DC.ISSUE.LATENCY.WARN:"{#JMXNAME}"}`	Warning	Manual close: Yes

LLD rule License discovery

Name Description Type Key and additional info

License discovery

Discovery of the Jira licenses.

Dependent item

jmx.license.discovery

Preprocessing

JavaScript: The text is too long. Please see the template.
Discard unchanged with heartbeat: 1h

Item prototypes for License discovery

Name Description Type Key and additional info

License [{#LICENSE.TYPE}]: Users: Current

Current user count for {#LICENSE.TYPE}.

Dependent item

jmx.license.get.user.current["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.current_user_count

License [{#LICENSE.TYPE}]: Users: Maximum

User count limit for {#LICENSE.TYPE}.

-1 = No limits for the license type.

Dependent item

jmx.license.get.user.max["{#LICENSE.TYPE}"]

Preprocessing

JSON Path: $.{#LICENSE.TYPE}.properties.max_user_count

Trigger prototypes for License discovery

Name	Description	Expression	Severity	Dependencies and additional info
License [{#LICENSE.TYPE}]: Low user capacity	Fires when relative user quantity grows above the threshold: `{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"}`%	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * (100*last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"])/last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>{$JIRA_DC.LICENSE.USER.CAPACITY.WARN:"{#LICENSE.TYPE}"})`	Warning	Manual close: Yes Depends on: License [{#LICENSE.TYPE}]: User count reached the limit
License [{#LICENSE.TYPE}]: User count reached the limit	Fires when user quantity reaches the limit. It won't fire if the limit is disabled (set to `-1`).	`last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])>=0 * ((last(/Jira Data Center by JMX/jmx.license.get.user.max["{#LICENSE.TYPE}"])-last(/Jira Data Center by JMX/jmx.license.get.user.current["{#LICENSE.TYPE}"]))<=0)`	Average	Manual close: Yes

Feedback

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

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

Link	Source	Type, Technology	Created Updated	Rating
The same as previous row github.com/OSidorenkov/zabbix-jira	GitHub 40	script python	2017-05-31 2 y	Popular
Automate JIRA ticket creation custom alert script in zabbix github.com/abhijith0505/JIRA-ticket-creation-using-zabbix-alerts	GitHub 6	script python	2016-10-09 2 y
Create ticket in JIRA script for creating Jira ticket (can be used in actions) github.com/alexander-nesterov/zabbix_jira	GitHub 3	script Perl	2017-02-04 3 y
Zabbix - to Jira Creating JIRA tickets for PROBLEM triggers in Zabbix automatically. github.com/zkovac-devops/zabbix-to-jira	GitHub 3	script bash	2017-05-05 7 y

See all Zabbix community templates

Zabbix 7.4 - Mais poder e produtividade na sua infraestrutura.

Explore Zabbix Cloud with a free trial

Torne-se um Parceiro Zabbix

Zabbix Academy está disponível!

Junte-se à nossa equipe global!

Zabbix + Jira

Jira

Available solutions

Jira webhook

Overview

Requirements

Parameters

Configurable parameters

Internal parameters

Service setup

Zabbix configuration

Feedback

Jira webhook

Overview

Requirements

Parameters

Configurable parameters

Internal parameters

Service setup

Zabbix configuration

Feedback

Jira webhook

Overview

Requirements

Parameters

Configurable parameters

Internal parameters

Service setup

Zabbix configuration

Feedback

Jira webhook

Setting up webhook in Zabbix

Supported Versions

Jira webhook

Setting up webhook in Zabbix

Supported Versions

Jira webhook

Setting up webhook in Zabbix

Supported Versions

Jira webhook

Setting up webhook in Zabbix

Supported Versions

Jira webhook

Setting up webhook in Zabbix

Supported Versions

Jira Service Desk webhook

Setting up webhook in Zabbix

Supported Versions

Jira Service Desk webhook

Setting up webhook in Zabbix

Supported Versions

Jira Service Desk webhook

Setting up webhook in Zabbix

Supported Versions

Jira Service Desk webhook

Setting up webhook in Zabbix

Supported Versions

Jira Service Desk webhook

Setting up webhook in Zabbix

Supported Versions

Jira Data Center by JMX

Overview

Requirements

Tested versions

Configuration

Setup

Macros used

Items

Triggers

LLD rule Storage discovery

Item prototypes for Storage discovery

Trigger prototypes for Storage discovery

LLD rule Mail server discovery

Item prototypes for Mail server discovery

Trigger prototypes for Mail server discovery