An administrator has noticed that an incident fetch has failed, causing several internal workflows to be backed up. The administrator would like to receive notifications the next time the incident fetch fails.
Option E: Hire a team of carrier pigeons to manually deliver incident reports. Guaranteed to never fail, as long as the pigeons don't get distracted by breadcrumbs along the way.
Hmm, Option A with the custom playbook sounds interesting. I'm always up for a bit of coding and customization. Although, I hope the playbook doesn't end up being more complex than the problem itself!
Option C is a bit overkill, don't you think? Scheduling a job to monitor incidents just to catch a failed fetch seems like a lot of work. I'd rather go with something more straightforward like Option B.
I think Option D is the simplest solution. Just adding a server config to notify when the incident fetch fails seems like the easiest way to get the job done. Why complicate things with a custom playbook or integration?
Option B is the way to go. Creating a new integration to monitor the incident fetch is the most robust and flexible solution. I can customize the notifications and integration to fit our specific needs.
Julio
16 days agoDylan
1 days agoLashaun
2 days agoCarin
22 days agoKayleigh
1 months agoEmmanuel
2 days agoIzetta
24 days agoKaitlyn
25 days agoCassandra
1 months agoStefania
1 months agoDevon
10 days agoMarylyn
22 days agoRolland
1 months agoMari
2 months agoJunita
2 months agoTommy
2 months ago