Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Advanced alerting - Do not trigger this action until condition has exists for more than ###

Good morning Network dudes!

I would like to ask a question to the community at large but i suspect this will need to be answered by the solarwinds guys themselves.

I love the advanced alerting engine, it is great and I use extensively. There are 2 things that i would like to be able to do, one is related to the subject line and the other is something else:

1. I would like the value configured in "Do not trigger this action until condition has exists for more than" to be taken from a custom variable set on either volume, node or interface (choice of the end-user) or of course it can just be entered like in complex rules. is there a way to modify the interface or is this a feature request?

2. I would like to be able to use the "trigger time" variable within the alert condition, rather than just in the action tab. can this be done?

I have not listed why i want these to minimise the post, but if you want reasoning i will gladly provide

Happy thanks giving to the US guys… I am going to try and make sweet potato pie tonight to bring the Irish into the spirit of it all….

cheers
Dan

Find more posts tagged with

Accepted answers

Yann

Morning :-),

1. This field only accepts numbers so yes this is a feature request.

2. The Alert Manager front end wizard which writes in the Alerts table does not actually provide a way to select all the database fields you need in the Alert conditions, only the most relevant. I have done some tests where I edited the alert in the database to trigger on unavailable fields and that worked but as soon as I edit the alert through the wizard that overwrites the alert field itself. Of course that's customization and not supported by us. So the official response is no, you cannot trigger on it with the current version of the alert manager but a non-recommended work around exists.

Have a good day and enjoy your yummy sweet potato pie tonight.

Yann

All comments

Yann

Morning :-),

1. This field only accepts numbers so yes this is a feature request.

Have a good day and enjoy your yummy sweet potato pie tonight.

Yann

FormerMember

thanks very much for the fast reply. Could we possibly ask for both of these to be added to a list of possible additions to the product development plan, i.e. do you agree that both requests are valid enough to be considered in the next or later releases? I suspect adding the "trigger time" as an available variable would not be a lot of work, but the first request would be a little more dificult...

Yann

do you agree that both requests are valid enough to be considered in the next or later releases?

I cannot speak for the dev team but the more users are requesting a feature the highest is the probability to see that feature in a future release.

FormerMember

Consider your features requested. And Yann is right, the more we hear it, the more likely it is to get added.

vhcato

I think what we really need is the ability to add a custom SQL query string as a condition. This would provide limitless flexibility and control over the alerting process. As it is today, one is limited to just the options that are presented in the GUI.

FormerMember

agree, that would be very useful as long as we keep the simple functionality for us simple-heads :-)

another minor change but int he same space would be to allow a Custom property field be called from the "email To, CC and BCC" field int he action tab. I would then be able to assign Node contacts as a custom property and not have to separate out the devices in alerts etc.

vhcato

another minor change but int he same space would be to allow a Custom property field be called from the "email To, CC and BCC" field int he action tab. I would then be able to assign Node contacts as a custom property and not have to separate out the devices in alerts etc.

You should be able to do this today. We use this quite extensively in our environment as a means to simplify email address management with regard to alerting. Try adding the custom property to one of the email recipient lists like so: ${Your_Custom_Property}. You can even use multiples in the same line, or in conjunction with some specific addresses entered in the list as well.

When using this methodology, the thing to keep in mind is that you never want the alerting engine to look in this field and find that the custom property for a given device is null. If it encounters a null value, it will throw an error message in the Windows event log stating "The specified string is not in the form required for an email address", and it will not send the alert to any of the addresses in the recipient list. Having said that, you always want to have some value in the custom property field, unless you don't want any emails sent for a given device. We have 2 macros pointing to different custom property fields in many of our alerts, and simply use a "service" email address for Orion in general (as a "filler") for the ones that would otherwise have no value.

FormerMember

genius, plain and simple, u r a genius... thank you! i will go play