note that order may matters when using multiple processors, you can write your config in the appropriate order, or put order = X in the config section itself
humm technically, for my need the field can be named differently, so i will look with the option to clone the tag value to a new one with differnt name and then convert it.
So i respond to myself with the solution that is in place now:
first we clone the tag to a new name
Second we convert it tag → field
third we rename it again to correspond to the final field
fourth i convert the integer value to a human readable value
## create a new tag, this is temporary as the next block convert the tag in field
[[processors.regex.tags]]
key = "EventID"
result_key = "Event_ID"
[[processors.converter]]
[processors.converter.tags]
integer = ["Event_ID"]
## create a new field with a simple short name/description depending of the ID
[[processors.enum]]
[[processors.enum.mapping]]
## Name of the field to map. Globs accepted.
field = "Event_ID"
dest = "EventTXT"
## Default value to be used for all values not contained in the mapping
## table. When unset and no match is found, the original field will remain
## unmodified and the destination tag or field will not be created.
# default = 0
## Table of mappings
[processors.enum.mapping.value_mappings]
25 = "ICA Session Connected"
26 = "ICA Session Disconnected"
27 = "ICA Connection Broken"
1015 = "LSASS crash"
Objective is to guard the tag allowing filter by tag, and when data is presented field is readable by a human.
Have a nice day!
p.s. if there is a better way to proceed i have no pb to change that