I love a good challenge!
So to start, my Script Action had one flaw. I messed up my math. 8000 seconds is 533 minutes. Needless to say, that notification will not be executing any time soon.
Here is what I have now for the Script Action:
var mid_name = "MIDServer1Sandbox";
mid_server_down(mid_name);
function mid_server_down(name) {
var fifteen_minutes = new GlideDateTime();
fifteen_minutes.addSeconds(100);
//fifteen_minutes.addSeconds(1);
var gr = new GlideRecord("ecc_agent");
gr.addQuery("name", name);
gr.addQuery("status", "Down");
gr.query();
if (gr.next()) {
gs.eventQueueScheduled('MIDServerDownNotification', gr, '', '', fifteen_minutes);
}
}I used 100 seconds for my test, but modify to 900 for 15 minutes. I double checked that number this time too 🙂
I then modified the Notification to use a self-invoking function. Now it does work:
(function () {
var gr_mid = new GlideRecord("ecc_agent");
if (gr_mid.get(current.sys_id)) {
if (gr_mid.status == "Down") {
return true;
}
}
return false;
}) ();
By using the Advanced Conditions, I think we are able to do a real time lookup (when the notification is processed). I think using the Conditions it will be based on whatever the passed in object has.
I am not sure if the notification advanced conditions can invoke a function. Perhaps that's why the self-invoking function works.
Can you try the above and see if it now works for you?
Edit: In case it's not clear, this is how the self-invoking function looks:
Step 1:
Confirm that you have events created for mid_server.down and mid_server.up. I think these are OOB, but we have been a client for so long we do have some things in our instance from many years ago that no longer exist.
Step 2
Create an Event Registry entry for your MID Server notification. Let's call it mid_server.future_email. This is just to trigger our email.
Step 3
Create a Script Action. This is what runs every time the mid_server.down event is detected (which is OOB on my instance, so we are just piggybacking on that)
https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/platform-events/reference/r_ScriptActions.html
Step 4:
Create a notification. You want to check if the MID Server is currently down in Advanced condition. I assume the rest of the notification stuff you know.
This is the step I see areas for improvement (sorry, just wanted to get you something to work with for now). The areas of improvement I see:
a) I would want to verify I need to do that glide record lookup in the Advanced Conditions. I assume if I pass the object, then it would pass the "down" status with it (the object is not updated I assume). This code here doesn't hurt regardless, I am just working off the assumption when I pass the object it is the object at the time and is not updated when the script actually runs. If this doesn't make sense, ignore it. Otherwise, feel free to test it out (or not care that it might run an extra glide record lookup - that's fine too).
b) I think it would be nice to take the time in the Advanced Condition to see if there was a series of up/down/up/down events. This script lacks the logic to say "has it been down for 15 minutes". It merely says "15 minutes ago you detected a down server. Is the server still down?". Slight difference.
If you can get the above working and need help with the optimization I suggested in Step 4 just let me know. However, focus on getting it working first because the optimization (specifically 4b) will not hold you back from it. It's merely to avoid a scenario where the MID Server goes up and down often within the 15 minute window.
Hope that all makes sense. Try out those basics, and we can refine the Advanced Condition to look into the event queue and see if the server has come up (and gone back down) within the 15 minutes. In that case, we would not want to send an email (ultimately if it stays down for 15 minutes another subsequent notification would handle it).
