When configuring a service template, it's possible to include an element conditionally, in that case, the alarm for that service will not be affected and in the alarm console, columns "service impact" will be 0 and the "service" column will not contain that specific service.
However, in case an element influences the alarm severity conditionally, you can have the following situation:
- Due to the condition an alarm does not influence the service alarm state
- It does however influence the condition, leading to 1.
In the latter situation the alarm console will have the following columns:
- "service impact": 1 (for the aforementioned service)
- "service": aforementioned service name (and any other services,...)
Is the latter expected behavior? Possibly, I would believe this to be so, due to point 2, it does influence the condition. However, wouldn't it make more sense to have it not influence the alarms, as it does not influence the alarm state itself (point 1) purely?
This would ensure that e.g. trap forwarding to customers with only the service impacting alarms is easier and a bit more lightweight compared to dynamic element exclusion.
Any feedback on this is greatly appreciated!
This is by design and also applies to regular services in general.
As soon as an element is included in a service (always or conditionally), any alarm on that element will list the service as being impacted (provided the parameter is included).
Any further configuration (conditionally influencing the overall alarm severity of the service, capping through maximum severities) only affects the calculation of the summary severity for the service.