Hi All
I have a use case when for different kind of live event, I'm creating different services, mainly this services are created before the live event start, so I need to turn off the alarm that are coming from services if the event is not yet started.
I see there is not an option to mask the entire service, and if I mask the element inside, it will mask the entire element that can be used in other live events in the meanwhile.
So which option I have to achive this?
For the moment I think there is few ways
- Create an automation script that will remove the alarm from the alarm console if specific services are impacted
- Generate a Child element and use that in the service, so I can mask the child element
There ins't other way to achive this?
As this question has now been inactive for a very long time, I will close it. If you still want more information about this, could you post a new question?
Hi Marco,
Have you tried using the conditional service severity impact?
If you can determine when the service is live based on parameters inside the same (or even a different) element, you can configure that the impact of an element is based of that parameter.
e.G.
My core switch below will only impact the severity of my service if the admin state of my used interface is up.
Hi Marco,
Is the connector able to generate child elements (DVEs)? If this is not the case then you could go for the first approach (Create an automation script that will remove the alarm from the alarm console if specific services are impacted).
You could proceed as follows:
- When creating a service, you could assign a default alarm template
- When the event starts, you can trigger an automation script to change the alarm template so you can monitor if there are alarms that are service impact
- When the event is stops, you could trigger the automation script to update the alarm template back to default one
If the connector is able to generate child elements (DVEs), then it is better to map the child elements to the service.
Hope it helps.
Hi Miguel
Thanks for your answer
Few connectors provide the possibility to generate DVEs, but not all of them, so yeah this could be a problem.
It will be easier to mask the alarm direclty, you told about assign an alarm template to the service or to the element direclty? in case you talk about the service, this can only be done if the service is created with a service protocol right? in this moment the service are created via API Automation script from outside of dataminer
Hi Marco,
Indeed, with assigning alarm templates I was referring to elements, not services. As you mentioned, at service level you can only assign alarm templates to enhanced services (services using service protocols).
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer that has been most helpful for you (using the ✓ icon)?