Splunk IT Service Intelligence

How do I work around known issue ITSI-4387?

cdemir
Explorer

The documented workaround doesn't make sense. An aggregation policy cannot be triggered to break a group on a group by group basis. It's all or nothing. Any advice is helpful.

Labels (1)
0 Karma
1 Solution

cdemir
Explorer

The issue as figured out. I found in the second to latest release notes for the ITSI API a juicy tidbit that was more clearly spelled out. The known issue is not documented in the release notes as clearly to know this is what you have to do moving forward.

If you want to break the episode via API, you must pass a breaking event into the tracked alert index. This can be accomplished using this example:

curl -k -u admin:changeme https://localhost:8089/servicesNS/nobody/SA-ITOA/event_management_interface/notable_event_group?brea... -X POST --data '{"_key":"{episode_id}","status":"5","title":"splunkd_access","description":"None","severity":"1","owner":"unassigned"}' --header "Content-Type: application/json

Unfortunately, we were not pulling out the itsi_policy_id and instead linking our external ticketing system to only the unique itsi_group_id. So we are now re-developing to link both fields per episode into our external ticketing system.

View solution in original post

0 Karma

cdemir
Explorer

The issue as figured out. I found in the second to latest release notes for the ITSI API a juicy tidbit that was more clearly spelled out. The known issue is not documented in the release notes as clearly to know this is what you have to do moving forward.

If you want to break the episode via API, you must pass a breaking event into the tracked alert index. This can be accomplished using this example:

curl -k -u admin:changeme https://localhost:8089/servicesNS/nobody/SA-ITOA/event_management_interface/notable_event_group?brea... -X POST --data '{"_key":"{episode_id}","status":"5","title":"splunkd_access","description":"None","severity":"1","owner":"unassigned"}' --header "Content-Type: application/json

Unfortunately, we were not pulling out the itsi_policy_id and instead linking our external ticketing system to only the unique itsi_group_id. So we are now re-developing to link both fields per episode into our external ticketing system.

View solution in original post

0 Karma

sensitive-thug
Community Manager
Community Manager

Hi @cdemir,

Thanks for asking a question! If you were able to resolve this issue, please click “Accept” directly below the answer to resolve the post.

0 Karma
Register for .conf21 Now! Go Vegas or Go Virtual!

How will you .conf21? You decide! Go in-person in Las Vegas, 10/18-10/21, or go online with .conf21 Virtual, 10/19-10/20.