1.0.8

Graylog alarm callback for JIRA issue integration with templating of JIRA title/message and MD5 generation to avoid duplicates.

PRE-RELEASE - Graylog 2.0.2 broke plugins!!!

With Graylog 2.0.2 the classloading for plugins has changed, forcing a single, shared classloader. I have logged a issue with Graylog - Graylog2/graylog2-server#2436. More info about the issue can also be read in this comment: Graylog2/graylog2-server#2280 (comment)

The Graylog map plugin ships with outdated (version 4.0.0) HTTPClient libraries and it also misses classes. This results in the Jira integration breaking.

The only workaround if you need to run Graylog 2.0.2 or onwards is to remove the Graylog map plugin and restart Graylog:

mv /usr/share/graylog-server/plugin/graylog-plugin-map-widget-1.0.3.jar /tmp

If you rely on the map-plugin, I suggest not to upgrade to Graylog 2.0.2 or later until this issue (or it's cause Graylog2/graylog2-server#2436) is resolved).

The attached plugin includes additional exception logging to assist identifying classloader issues.

1.0.7

Graylog alarm callback for JIRA issue integration with templating of JIRA title/message and MD5 generation to avoid duplicates.

PRE-RELEASE - provide feedback here

• Feature #9: Auto-map Graylog fields into JIRA

Introduced an "auto-mapping" feature which allows the configuration of a comma-separated list of Graylog message-fields mapping into JIRA. The list needs to be in the format of graylogmessagefieldname1=jirafieldname1,graylogmessagefieldname2=jirafieldname2

JIRA fields which can be iterated (such as fixVersions or versions) need to be configured as fixVersions#i

1.0.6

Graylog alarm callback for JIRA issue integration with templating of JIRA title/message and MD5 generation to avoid duplicates.

• Bug #7: Removed hard-coding of stream result description and made this now a place-holder via [STREAM_RESULT]
• Bug #8: Fixed an issue where the plugin would attempt to set an empty JIRA component or JIRA label, resulting in an error when creating the ticket.
• Feature: Added place-holder [STREAM_RESULT] to include the stream-result - i.e. 'Stream had 7 messages in the last 30 minutes with trigger condition more than 5 messages. (Current grace time: 0 minutes)'
• Some more bugfixes and refactored code to improve checking of empty configuration fields

1.0.5

Graylog alarm callback for JIRA issue integration with templating of JIRA title/message and MD5 generation to avoid duplicates.

• New feature: Added optional config-option jira_md5_custom_field to define the JIRA MD5 field (normally in the format of customfield_####). It is recommended to use this method as it does not require elevated permissions in JIRA to read the schema to automatically determine the name of the custom-field. For legacy reasons, the plugin will continue to determine the custom-field if the option is not set and log a warning in the Graylog server.log
• Improvement: Reworked JIRA integration so that the JIRA issue is created within one JIRA call (no more incremental updates)
• Improvement: Reworked configuration checks of the AlarmCallback
• Bug #6: JIRA task title field is not being picked up
• Several bug fixes and improvements to speed up the callback

1.0.4

Graylog alarm callback for JIRA issue integration with templating of JIRA title/message and MD5 generation to avoid duplicates.

• Bug #2: Optional fields are not blanked
• Bug #4: Once field-substitution via [LAST_MESSAGE.fieldname] has been performed, replace unsubstituted placeholders with blanks.
• Feature #3: Field names are now case-sensitive
• Feature #5: Make the MD5-filter query configurable
• Refactored the plugin code to be more maintainable and added extra logging
• Reworked JIRA integration to avoid multiple JIRA connections. Posting/searching in JIRA via the plugin should now be faster.
• Refreshed libraries and adjusted plugin code to be compatible with both Graylog and Graylog2
• Change in JIRA-assignee behaviour: With the recent JIRA client-library, the assignee was automatically set to the user logging in. I don't think this is correct and I now explicitly default the JIRA assignee field to NULL (which marks the assignee in JIRA as "Unassigned" or would use the default-assignee such as the project-/component-lead).

1.0.3

Graylog alarm callback for JIRA issue integration with templating of JIRA title/message and MD5 generation to avoid duplicates.

• Reworked the JIRA MD5 functionality to avoid the generation of duplicate JIRA issues:
  • Introduced a new config parameter jira_md5_hash_pattern which can contain a string of place-holder variables to construct an unique MD5 string which is used to identify duplicate JIRA issues
  • If the config parameter message_regex is configured, it can be used as a place-holder variable [MESSAGE_REGEX] for the JIRA title as well as the MD5 generation
  • You can reference any field in the last-message to be part of the MD5 generation. Example: jira_md5_hash_pattern=[LAST_MESSAGE.SOURCE][LAST_MESSAGE.ERRORCODE][LAST_MESSAGE.TAGS][LAST_MESSAGE.TYPE]
• Several bug fixes and code cleanup

1.0.2

Graylog alarm callback for JIRA issue integration with templating of JIRA title/message and MD5 generation to avoid duplicates.

• You can now use a custom JIRA field graylog_md5 to ingest the MD5 hash of the message
• Several bug fixes and code cleanup

1.0.1

Graylog alarm callback for JIRA issue integration with templating of JIRA title/message and MD5 generation to avoid duplicates.

• Reworked JIRA connector
• Bugfixes and improvements

Initial release with templating

Thanks to @tjackiw for his initial codebase at https://github.com/tjackiw/graylog-plugin-jira

I reworked the code to include a number of features and fixes

• [FEATURE] Allow templating via placeholders in JIRA issue title and JIRA message
• [FEATURE] Generate a unique MD5 hash and embed into JIRA issue to avoid duplicate JIRA issues. We search JIRA for any via JQL for existing issues with the same hash (via Status not in (Closed, Done, Resolved))
• [FIX] JIRA password was not masked