This Splunk Technical Add-on enables you to index Jira issues by querying your Jira servers' REST API. You can control which issues to index by specifying a JQL query string.
project = SD AND updated > -15m
The Add-on Jira Issues Collector does not support API pagination. That means if your JQL query string returns more than the maximum allowable value defined by the Jira property
jira.search.views.default.max, which defaults to
100, you will loose data.
This TA supports API pagination and adds some additional functionalities!
Account Name | Unique name of the account
Jira Server | Jira Server Hostname (without
Verify Jira Server Certificate | Whether the Jira server certificate should be verified
Username | Jira REST API username
Password | Jira REST API password
(Optional) Setup a proxy to use for the requests to the Jira REST API: Configuration -> Proxy
Add your Jira issue input on the app Inputs configuration page
Name | Unique name of the data input (this also represents the
Interval | Time interval of input in seconds
Index | The destination index in which the Jira issue data will be stored
Jira Account | The Jira account configured in step 1
JQL (Jira Query Language) | The JQL query string defines which issues to collect
Issue Fields | Comma-separated list of Jira issue fields to collect. This config option also supports wildcards like *all. More infos can be found here.
Expand Fields | (optional) Comma-separated list of entities to expand. More infos can be found here.
This project is hosted on Github: https://github.com/Stjubit/TA-jira_issue_input
Fixed bug in which help text was larger than the max. allowed character count
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.