Yes it sends NAT events. It is a separate template with ID 260.
Unfortunately there is a bug: when this nat-events=yes setting is not done, the events are still sent but the template is not.
When you enable nat-events=yes, both the template and events are sent.
With this config, it sends ID 260 messages but it never sends the template description.
When I add nat-events=yes it sends the description and continues to send the events.
IMHO it is wrong, I do not need or want the nat events so it should not send them when
I have not enabled them.
but I have a problem that I can’t see the template. even nat-events=yes
downloaded NetFlow Analyzer and the software told me:
Error in processing flows for device with ip 10.1.1.39 as template information is not received from the device.
and the error hangs in active.
now I have two netflow collectors, who doesn’t see template for ID 260
what settings do you have
v9-template-refresh
v9-template-timeout
in /ip traffic-flow target ?
That is right. The low active-flow-timeout value is because the counters in the traffic-flow are only 32 bits (even when the fields are 64 bits, only 32 are used) so I wanted to limit the number of wrap-arounds that occur. Hopefully at some time MikroTik will fix that bug and the active-flow-timeout can be set much higher.
Otherwise I just have made a selection of the columns relevant to me and have not changed anything else.
When the nat-events capability was added in 6.49 I started to notice ID 260 events without a template, and I reported that. Then I noticed the new checkmark, set it, and the template appeared.
MikroTik noted it as a bug.