Migrate from an existing add-on
This add-on replaces JIRA Cloud Audit Logs Add-On for Splunk.
There are no contradictions in running both the JIRA Cloud Audit Logs Add-On for Splunk and Splunk Add-on for Jira Cloud if you want to verify that data is being collected correctly.
Some differences are summarized in the following table.
JIRA Cloud Audit Logs Add-On for Splunk
(existing TA) |
Splunk Add-on for Jira Cloud
(new TA) | |
---|---|---|
host | References to splunk server where event was ingested | References to Jira Cloud instance (expected format: [your-domain].atlassian.net, eg. splunk.atlassian.net) |
source | jira_audit_log://[input name] | jira_cloud_input://[input name] |
sourcetype | jira:audit:log | jira:cloud:audit:log |
CIM fields | Not extracted | Extracted
See Source types for the Splunk Add-on for Jira Cloud for more information. Event time is taken from the audit log events created for both add-ons. |
Install the Splunk Add-on for Jira Cloud | Generate API tokens for Splunk Add-on for Jira Cloud |
This documentation applies to the following versions of Splunk® Supported Add-ons: released
Feedback submitted, thanks!