Getting Data In

Splunk Integration App For ServiceNow

akriti
Explorer

Hi Splunkers

I would like to know if anyone has faced the issue of multiple incidents getting created in ServiceNow for the same entity/issue if the incident is not resolved in ServiceNow and the Splunk custom alert generates another ticket for the same issue when it sweeps through the data again and finds the same entity/issue.

The correlation id is supposed to prevent that from happening as it tells servicenow that a ticket already exists for that issue but it doesn't seem to be working as multiple incidents are getting created in snow for the same asset. I have added $result.asset_tag$ as the asset_tag is a unique field but that hasn't helped either.

Any advice?

Thanks,

Akriti

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

Take Your Breath Away with Splunk Risk-Based Alerting (RBA)

WATCH NOW!The Splunk Guide to Risk-Based Alerting is here to empower your SOC like never before. Join Haylee ...

SignalFlow: What? Why? How?

What is SignalFlow? Splunk Observability Cloud’s analytics engine, SignalFlow, opens up a world of in-depth ...

Federated Search for Amazon S3 | Key Use Cases to Streamline Compliance Workflows

Modern business operations are supported by data compliance. As regulations evolve, organizations must ...