Hi All,
Is there a way to filter out alarms on the display key when building a service template, on some we use the primary key by including a parameter with ^pk^ but is there a way to filter out and alarm like the one attached where the display key [IDX] is the only thing we can filter on?
Hi Ryan,
Service templates are powerful tools for automating the creation of multiple services with similar characteristics. However, they can be challenging to work with, especially when the desired end result isn’t clear.
In my experience, it’s helpful to create one or two services manually first. Only when they’re working exactly as intended do I start building templates to automate the creation process.
After reading your question, I’m not quite sure what the desired end result should be. I will provide some information, but if this is not enough, you should explain what you are trying to accomplish in more detail. It would help if you shared screenshots of a manually created service.
To prevent certain alarms from impacting the service, you need to make sure not to include the corresponding data points (parameter:index)
This page explains the possibilities when including elements and parameters in a service Creating child elements in service templates | DataMiner Docs
To filter rows based on the [IDX], you must remove the ^pk^ prefix. That is because filtering by the [IDX] is the default behavior. When you use ^pk^ you are explicitly telling DataMiner to filter on the primary key instead of the index key [IDX].
Hope that helps.
Regards