Re: "Suspend Alarm" and "Unsuspend Alarm" Agent Procedure Steps: It's time for an "Official Response" from Kaseya...

Forums

Forums, discussions, and Q&A for all products.

"Suspend Alarm" and "Unsuspend Alarm" Agent Procedure Steps: It's time for an "Official Response" from Kaseya...

Answered (Verified) This question is answered

Happy Friday, everybody!  Smile

I've just submitted the ticket below to Kaseya (CS098207).  I will pass along any response I receive.  I'm determined that this will not be "Feature Requested" into oblivion... 

Good afternoon,

I'm sure this isn't the first time you've been asked this question, and it certainly won't be the last:

http://community.kaseya.com/xsp/f/29/p/261/764.aspx
http://community.kaseya.com/xsp/f/28/p/14198/69227.aspx
http://community.kaseya.com/xsp/f/36/t/262.aspx
http://community.kaseya.com/xsp/f/29/t/13427.aspx
http://community.kaseya.com/xsp/f/28/t/11924.aspx
(there are more, I'm just lazy)

I understand that many of these folks have put in Feature Requests as early as 2010 for this same request... but here goes again:

Can Kaseya please add Agent Procedure Steps to "Suspend Alarms" and "Unsuspend Alarms?"

This would help everybody by:

1) Allowing us to suspend alarms prior to Automatic Updates, and unsuspend alarms after Automatic Updates are complete:



2) Making it easy to temporarily stop alarms if an Agent Procedure is cycling a key service

I certainly understand, if the machine is not online, that the "Suspend Alarms" and "Unsuspend Alarms" Agent Procedure Steps would have no impact (the machine needs to be online in order to run an Agent Procedure), so a site-wide alarm suspension (for an internet outage/flood/earthquake/tornado) would still have to be done manually, and that's not a problem... you could certainly mention this in the "notes" field of the Agent Procedure Step.

What I'm looking for here is an "Official Response" from Kaseya... this "Feature Request" has been in the works since 2010, and is something that many of your best customers are asking for.  Given that this request has, in the past (per forum posts above), been relegated to a sort of "Feature Request Purgatory," I'm kindly requesting a direct response (Yes/No, When) from Engineering on this issue.

And yes, this ticket (and any responses I receive) will be added to the Community Forums... fair warning :-)  We've all waited long enough...

Thanks,

Brian Dagan
bdagan@cwps.com  

Brian Dagan
CWPS: Connected WorkPlace Solutions
bdagan@cwps.com | brian@briandagan.com
http://www.briandagan.com

 

Verified Answer
  • Ok, official response:

    I will create this as a custom step you can select when creating an agent procedure, possibly available as a hotfix, if two conditions are met:

    1) Brian Dagan agrees to come to the user conference and buys me a beer

    2) HardKnoX promises to put off raiding in World of Warcraft for an evening and make it out to one of our upcoming Kaseya events in Australia

    Deal?

  • Ok Hardknox, NZ then :)

    Since you all are such good sports I put together the custom steps this evening.

    Grab this zip file:

    http://tinyurl.com/csaztyo

    Extract to your Kaseya folder. You should be asked to overwrite Subscripts.xml.

    Run a Re-Apply schema. When it finishes, go try out the new "Alarms - Suspend" and" Alarms - Unsuspend all" custom steps.

    I'll be submitting these for inclusion into 6.3 unless you guys report anything really odd with them.

    • Top 25 Contributor
    • Male
All Replies
Page 2 of 5 (70 items) 12345