You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With precedence from left to right. Since we prioritise exact matches over wildcards.
The moment an incoming line starts to match we descend to the depths of one of the branches while matches occur. If at any point we stop making matches, we bail and fallback to the default template. The default template produces the output you are observing.
So your line taskmanagerTask.alarm-detector.Assign.numRecordsInPerSecond.m5_rate matches all the way down the search tree to taskmanagerTask.alarm-detector.Assign and then alarmDefinitionId != numRecordsInPerSecond. The search bails at this point. Rather than going back to other branches which could match. As it forked from the wildcard filter early on when it exactly matched alarm-detector.
@danielnelson@glinton Can you deny or confirm that the desired behavior in this scenario would be to continue searching other candidates which would have also matched early parts of the line?
Relevant telegraf.conf:
System info:
Telegraf 1.10.4
Steps to reproduce:
telegraf --config conf-from-bug-report.conf
Expected behavior:
Telegraf output:
Actual behavior:
Telegraf output:
Additional info:
I get expected behavior when I remove first template, but I need both of them to work correctly.
The text was updated successfully, but these errors were encountered: