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!

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Deprecation of Splunk Observability Kubernetes “Classic Navigator” UI starting ...

Access to Splunk Observability Kubernetes “Classic Navigator” UI will no longer be available starting January ...

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...