Origin https://groups.google.com/forum/#!msg/logstash-users/exgrB4iQ-mw/R34apku5nXsJ and https://botbot.me/freenode/logstash/msg/4169496/ via https://gist.github.com/electrical/4660061e8fff11cdcf37#file-jira-rb Uses jiralicious as the bridge to JIRA By Martin Cleaver, Blended Perspectives with a lot of help from ‘electrical’ in #logstash
This is so is most useful so you can use logstash to parse and structure your logs and ship structured, json events to JIRA
To use this, you’ll need to ensure your JIRA instance allows REST calls
output {
jira {
assignee => ... # string (optional)
codec => ... # codec (optional), default: "plain"
host => ... # string (optional)
issuetypeid => ... # string (required)
password => ... # string (required)
priority => ... # string (required)
projectid => ... # string (required)
reporter => ... # string (optional)
summary => ... # string (required)
username => ... # string (required)
workers => ... # number (optional), default: 1
}
}
JIRA Reporter
The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output, without needing a separate filter in your Logstash pipeline.
Only handle events without any of these tags. Note this check is additional to type and tags.
The hostname to send logs to. This should target your JIRA server and has to have the REST interface enabled
JIRA Issuetype number
JIRA Priority
Javalicious has no proxy support JIRA Project number
JIRA Reporter
JIRA Summary
Only handle events with all of these tags. Note that if you specify a type, the event must also match that type. Optional.
The type to act on. If a type is given, then this output will only act on messages with the same type. See any input plugin’s “type” attribute for more. Optional.
The number of workers to use for this output. Note that this setting may not be useful for all outputs.