Splunk SOAR (f.k.a. Phantom)

Why does Jira ticket ingestion fail due to attachment(s)?

New Member

I have been seeing containers without any artefacts with jira 'on poll'. After comparison against those successfully ingested and failed, it appears to be caused by attachment(s) on the jira tickets. If all attachments are removed from the tickets, then the ingestion would succeed.

This is seen for failures using manual poll.


/builds/phantom/phantom/alchemy/connectors/spawn3/spawn3.cpp : 978 : JiraConnector :Downloading from: .../screenshot-1.png
2022-07-27T02:46:06.524696 PID:28743 TID:28743 : DEBUG: SPAWN3 : /builds/phantom/phantom/alchemy/connectors/spawn3/spawn3.cpp : 978 : JiraConnector :Could not connect to url to download attachment: Error Code:Error code unavailable. Error Message:HTTPSConnectionPool(host='domain', port=443): Max retries exceeded with url:  .../screenshot-1.png (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7ff09d00b190>: Failed to establish a new connection: [Errno -2] Name or service not known'))
The asset is running through an automation broker , polling a on-prem Jira instance

Jira; Publisher: SplunkApp; version: 3.4.0; Python version: 3; Product vendor: Atlassian

Labels (1)
Tags (1)
0 Karma
Get Updates on the Splunk Community!

Registration for Splunk University is Now Open!

Are you ready for an adventure in learning?   Brace yourselves because Splunk University is back, and it's ...

Splunkbase | Splunk Dashboard Examples App for SimpleXML End of Life

The Splunk Dashboard Examples App for SimpleXML will reach end of support on Dec 19, 2024, after which no new ...

Understanding Generative AI Techniques and Their Application in Cybersecurity

Watch On-Demand Artificial intelligence is the talk of the town nowadays, with industries of all kinds ...