Splunk Enterprise Security

adding a custom field to notable and update the value via api

gigahex
New Member

Hi Team,

I am working with Splunk version 7.3.2, and I would like to add a custom field called jira_ticket to notable events. The goal is to initially populate this field during the event creation process and later update its value via the API as the ticket progresses through different stages in Jira.

Here are my key questions:

  1. What is the best way to add a custom field like jira_ticket to notable events? Are there specific configurations or updates needed in correlation searches or incident review settings?
  2. How can I reliably update this field through the API after it has been created? Are there any specific endpoints or parameters I need to be aware of?
  3. Since I am using an older Splunk version (7.3.2), are there any limitations or additional considerations I should keep in mind while implementing this?

If anyone has successfully implemented a similar setup or can point me toward documentation, examples, or best practices, I’d greatly appreciate your input.

Thank you in advance!

 

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

Almost Too Eventful Assurance: Part 1

Modern IT and Network teams still struggle with too many alerts and isolating issues before they are notified. ...

Demo Day: Strengthen Your SOC with Splunk Enterprise Security 8.1

Today’s threat landscape is more complex than ever. Security operation centers (SOCs) are overwhelmed with ...

Dashboards: Hiding charts while search is being executed and other uses for tokens

There are a couple of features of SimpleXML / Classic dashboards that can be used to enhance the user ...