Create Incident when MID Server goes down with wait condition

chaluisant
Tera Expert

Hello,

I created an after Business Rule to open an Incident when a MID server goes down which is working as intended.  What I am trying to accomplish is to modify its behavior so it waits 5 minutes before creating the Incident. 

The ideal behavior would be:

  1. ecc_agent changes to down
  2. 5-minute timer starts
  3. At the end of the 5 minutes ecc_agent state is checked again
  4. if still down create Incident 

Here is my business rule as is:

find_real_file.png

 

find_real_file.png

Any help is greatly appreciated.  

1 ACCEPTED SOLUTION

DScroggins
Kilo Sage
Hello. Why not use a flow or workflow for this? Server status = down can be the start trigger then add a wait timer to see if server came back up. If not create the incident.

View solution in original post

3 REPLIES 3

DScroggins
Kilo Sage
Hello. Why not use a flow or workflow for this? Server status = down can be the start trigger then add a wait timer to see if server came back up. If not create the incident.

Thanks.  I didn't think about going that path.  

hello @DScroggins  

how can i set the Configuration item of incident record to the Mid server which is also getting discovered in CMDB
Mid Server host name is same as the ci in cmdb

CI.jpg