I would like to send a trap each time that a service is in alarm.
However I do not want to send a trap if several elements are in alarm in a service.
I’m currently using a correlation rule :
My concern is if a second service is in alarm from the same active trees it won’t send any trap.
Do you have any advice to perform a correlation rule for Services in the same active tree but not on the different elements ?
Perhaps, the correlation rule is not the best approach. Let me know if you have another approach.
Hi,
I believe it might also be worth looking at the grouping functionality in Correlation.
In a Correlation rule, you first filter the incoming alarms. By default, no grouping is done, and this basically means all the filtered alarms arrive in one big 'bucket'. As soon as something is in the bucket, the actions are being executed.
You can also add grouping to your Correlation rule, e.g. group by service. This means that DataMiner will create a 'bucket' for each service, and as soon as an alarm arrives in the bucket, the actions are being executed. This way, the actions should be executed for each service going in to alarm.
Hi Laurine,
Maybe I am missing something, but have you tried using as condition 'Service':
In case you would like to keep using the condition 'View', then you could enable the option 'Trigger on single events'. Every time that the condition is met (in the view), a correlated alarm will be created.
Hi Miguel,
Thank you for your reply.
My issue is that in a view, we have a lot of services.
I would like to avoid adding in the correlation rule the service each time there is a new service.
Hello Bert,
Thank you for your reply. I have tried what you advice to me and it’s indeed solving my issue.
Thanks a lot for the tips.