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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...