Oxidized backup issue

Hi,

We are using oxidized to automatically backup our router configs.
Oxidized is sending export command and save the config if any change was applied since last check.
The problem with Mikrotik is that a timestamp is in the output so each check is considered as a config change.
I’m trying to fix it on Oxidized side but I wonder if we could also do something on Mikrotiks themselves?

Any ideas welcome.

Since it’s just the top line that is set with the actual export date, you can simply skip that using a rewrite rule in Oxidized.

2024-01-25 09:35:49 by RouterOS 7.12.1

software id = KAVV-XYZQ

. . .

. . .

Indeed I fixed this with a few oxidized rewrite rules.
Thanks.

Just as a reference, here is the official Oxidized RoS plugin that supports the new v7 date header with the courtesy of Brian Candler (candlerb)
https://github.com/ytti/oxidized/blob/master/lib/oxidized/model/routeros.rb