
As I've mentioned in the past, if you give us the ability to create and share "plug-in" solutions you will likely find that we'll do the work for you. We know what we're looking for and by giving us a handy way to share our successful configurations in some sort of "one-click import" solution other users would have the opportunity to lean on our efforts.


This same "arguments" paradigm would work great for actions. For example, I could create a few different email actions with different content (passive, active, information, warning, etc.) and give the email address as an argument when the active monitor is applied to the device.
Right now I have an "Active" and "Passive" email action for every one of my notification emails. I've considered building emails with more or less details or description (email to mobile devices for example) but I'd end up creating a new email action for every address on my system. Give me arguments and I only need one of each notification style.

For example: HTTP Content monitor: Currently I have to create one for each of my sites but, if I could put the device.name in the URL I would only need one. I can also add attributes to devices that are used to configure more generic FTP "expect" statements.
The same issues apply to "Folder Monitor", "File Properties Monitor","SQL Query Monitor", etc.

You've done it in the thresholds. Can we move it into the action policies?

This is such a simple fix and I've been asking about it since version 11.

This is especially important for measuring bandwidth to ensure that we are within our contracted 95th percentile CIR for burstable circuits.

I love the idea behind this script. I hadn't previously considered having the system do some additional "fact finding" before the time arrived to begin notifications.

I register Where?
I have been here all along!
Please tell me I'm In.