Hello I want to use the filter in the alarmtemplate using a wildcard at the end, but NOT at the beginning.
So for instance I want to alarm on this IDX's :
100
100/
100/xxxx
100/YYYYYYY
100/ZZ
So I wrote in the filter: 100/*, but I also get the numbers: 1100/...., 2100/.... etc.
How can I fix, that I only receive the 100 range?
Is there a prefix I can use?
Regards,
Rob.
Hi Rob,
With the filter that you have added, I would expect that you do not get an alarm for 1100/..., 2100/... etc, as you did not define a wildcard in the beginning.
On an internal system, I have applied an alarm threshold with following filter:
The result does correctly exclude 1100/... and 2100/...
Would it be possible for you to:
- Provide information on which DMS version you are using?
- Check if you double click on a cell if the display is indeed that specific column, just to ensure that the filter is indeed applied on the column that you expect it to? (as marked in image below)
Ok, thanks for the feedback, Rob. Do I understand correctly that your question is answered? Not sure if the absolute type is currently an issue to you? Thx
Yes the question has been answered.
The filter you're describing should actually exactly do that.
So it might be that you're overseeing something. Are you sure there's no other alarm rule in the template that would catch those unexpected rows? E.g. alarm rule with filter * that would just match everything?
If next to everything that matches 100/* you also like to monitor 100 like you mentioned in your post, you'll need to create an extra alarm rule that just matches exactly 100 with the same thresholds. This can easily be done by duplicating the alarm rule by clicking the + icon and changing the filter.
Hello Thanks for the answers.
We are running on Dataminer version: 9.6.0.0-9944-CU22.
I Have looked into this and indeed it is working fine when using the alarmtemplate Type setting “Normal”.
But when using the Alarmtemplate Type setting “Absolute” and then click in the alarmtemplate on the base values, then all the IDx’s with wildcard 100/ will be displayed, also 4100/….
That seemed a bit strange.
I have tested this, and entered an value for the IDx 4100/ but it didn’t alarm on that. So for me it works fine.