[SOLVED] Unable to use macro %5 as key in event processing policy

[Dan]

Hi!

I found this in the forum, which is a great way to differentiate events:

@victor said in Event Processing Policy:

Hi!

I would suggest to change alarm key in your configuration for %m (message text) to DC_%i_%5 - that would create separate alarms for different nodes, even if they have same message text. But anyway, that is not important for sending e-mails. From information you have sent it is not clear why you getting e-mail only for 1 DCI - I should see configuration and values of all 4 DCIs. Also, was it your intention to send e-mails every minute as long as there are files matching filter?

Best regards,
Victor

But, when I use it in already existing events in my event processing policy, it is blank.
If I try to set it as a text message, the macro parameter is shown as a blank, i.e null or nothing.

I configure the DCI that uses these events from a template that distributes to my nodes.

When I create a new DCI on one of my nodes, not through a template, and then test it, the macro %5 shows output, which I think is the correct one.

Could there be a problem because I use a template?

Best regards,
Dan

[Dan]

I forgot to mention that I am using 1.0.4.

Best regards,
Dan

[victor]

Hi!

All %number macros are event-dependent. %5 will be DCI ID for threshold violation events. However, for threshold rearm events DCI ID will be %3 (I know that it's confusing, but unfortunately this cannot be changed without breaking backward compatibility). There should not be any difference on how DCI was created - directly on the node or via template.
Could you please provide more details about your configuration (DCI thresholds configuration, event policy rule)?

Best regards,
Victor

[Dan]

Hi!

I think it is me that configured it wrong, I used %5 on my rearm, instead of %3.
I will try this first just to ensure that it is not me.

If it does not work I will try to explain my configuration

Thank you for your answer!

Best regards,
Dan

[Dan]

Seems like that was the problem, the difference between %5 when using it in a threshold and a rearm event.

Thank you very much for your help!

Best regards,
Dan