Dear Dojo community,
I would like to know whether it is possible to generate an alarm on a service (or on an element) directly from an Automation script.
I know this can be achieved using a Correlation Rule. For example, an Automation script can generate an information event, and a Correlation Rule can then use the New alarm event action to generate an alarm if the information event condition is triggered. However, this approach generates only element alarms (not service alarms) and feels like a heavy workaround, and in my case it is not ideal...
So my questions are:
- Is there a way via Automation script to generate an alarm directly on a servicet?
- Is there a way via Automation script to generate an alarm directly on a element?
- If this is not supported directly, what would be the recommended best-practice approach for this use case?
Thanks in advance for your help.
Yahya
Hi Yahya,
Could you provide more details about your use case?
Rather than assigning alarms directly to elements/services, you could consider the following approaches:
- Service: You could define specific conditions for child elements in your service:
- Filter specific parameter that influence the severity of the service
- Include/exclude elements from the service based on conditions.
- Influence the overall service alarm severity based on conditions.
- Enhanced service: If a standard DataMiner service is not able to cover your use case, another option is to develop a service protocol. A service protocol is a special connector assigned to a service, allowing custom logic and behavior. This provides extra flexibility when influencing the severity of a service based on information from the child elements.
Hope it helps.
Hello Miguel, and thank you for your quick response.
My use case is the following: I need to set a parameter through an Automation script and raise an alarm if the set operation fails.
Ideally, the alarm should be raised either:
– on a specific service, even if the service does not necessarily include the element where the set failed.
– directly on the element where the set operation failed.
Using an enhanced service could be a possible approach, in addition to the workaround I mentioned in my original question. However, I would prefer to use something similar to the New alarm event action available in Correlation Rules, but directly from within the Automation script.
In other words, I am looking for a way to generate an alarm programmatically from an Automation script, instead of relying on a separate Correlation Rule/Service protocol to create the alarm