FKM Plugin - How to show only the last error message for each key in FKM
maxConditionsPerKey property will limit the number of errors shown in the dataview for each of the defined keys
Whether using FKM tables to define keys or defining FKM keys in the sampler itself, it is important to remember that the order the keys are defined will be the order that the keys will be evaluated.
Example:
-
If you want FKM to distinguish different errors, you need to define a key for each one. This could be an FKM table:
The order in this table matters. FKM evaluates keys from top to bottom, once it finds a matching key, it stops evaluating them. This is the reason why we will define Ignore keys before error keys. Also, this is why the more generic keys like “ERROR” have to be the last.
-
Enable maxConditionsPerKey parameter. This is the key component that will help us achieve our goal. It will show only the latest log line that matched the key. But because of this, it is more important than ever to define multiple keys and not only a generic one.
After echoing each error multiple times to the log file we can see that only one line is showed per key in the dataview.
This is the resulting dataview with both settings configured:
