+5Hi Community,
We recently had an incident where 1000's of cases got created and we have multiple environments affected by this as the playbooks got queued up.
We are planning to have a monitoring solution for this, if a playbook status is queued in an environment we could have a job that could report it while the playbook stay in queue.
Any possible solution that is already available?
+12I wonder if Jobs run in the same queue as playbooks (i.e. they would be delayed too), it would be worth checking
You could consider an API call from a remote solution (Nagios/Icinga/python) to check the status of latest 20 cases, if >x% are in status "pending" you have a problem.
+5I wonder if Jobs run in the same queue as playbooks (i.e. they would be delayed too), it would be worth checking
You could consider an API call from a remote solution (Nagios/Icinga/python) to check the status of latest 20 cases, if >x% are in status "pending" you have a problem.
Thanks @SoarAndy . The instance where we had those playbook queued up was still ingesting new cases. So connectors definitely is a different process. Yet to figure out for Jobs.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
