Closed eloekset closed 1 year ago
I thought I did not see the problem. But on a router with 7.11b2 I do see the error, will tryfix
This is a but in RouterOS. It fails to spilt Key Value correctly on some version.
Mostly fixed in latest commit. Problem was multi value fields. Like a neighbor router my be discovered by several type of protocol
Thanks! I've updated the view file on the Splunk app and the script on all of my devices. I'll report back once the neighbor part has been logged again.
Fixed with better extraction code.
I'm not sure whether this is a real issue, but it looks like the split on "\n" works for most, but not all properties. From my syslog:
I cannot reproduce the output running the
/ip neighbor get
command on the terminal, but I'm just guessing that some of these properties are split by semicolon.I haven't tested it, but maybe this would split by both newline and semicolon?
I may also break things if Mikrotik should choose to use semicolons in their content somewhere.