Good Morning ,
need suggestions
we have a requirement, where when ever a source goes unhealthy it should get triggered and create a jira ticket
link but i would need the other changes to understand here like what would be the api that calls / triggers when sources goes unhealthy if you could help make some changes
Hey, @osmanmohammed!
The limitation I see here is a trigger. Perhaps SailPoint ES could offer that process (or someone else who has developed this type of use case), but in the past I’ve met this requirement just fine using notifications. Within system settings for IDN there is configuration of system notifications. You can create the process by which an email creates a JIRA ticket, and then add the necessary email address to IDN for alerting on sources.
Additionally, you can update the source health email template to behave differently when the source becomes healthy again.
This is fairly basic, but again without the known trigger of a source being unhealthy (and if I understand correctly, IDN is just doing constant checks on the sources, potentially via GET Source call, and when one fails for 15+ minutes, that’s when the notification sends), a workflow is tough to come by.
Configuring System Health Notifications - SailPoint Identity Services
Source Health Email Template - SailPoint Identity Services
One additional possibility without the known trigger would be using scheduled search, but that could get muddy. You’d just need to consistently run a scheduled search looking for source events in the last X minutes or hours, and then use that as the workflow trigger and handle non-events within the workflow itself.
As Nicholas stated, this is a hard requirement to hit. You could do a scheduled workflow that does a GET request of the sources on the tenant and checks for the “healthy” flag.
The flow could be:
Here are some limitations you may encounter with this approach:
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.