Complete list of RouterOS logging messages by topic? .. and what they mean/ when they're logged?

RouterOS
1

:sweat_smile: this was asked twenty years ago ....

So, still, again, now, is there a list of all messages for each logging topic?

It would be helpful, in the face of question like:

"Given the prevalence of unactionable messages like:

ssld,error ssl: peer suggested unsupported TLS version

?Are there ANY ssld error messages that would be of interest? .. or should I just !exclude ssld,error messages?"

And,

"When, exactly, are(n't) WireGuard 'Sending keepalive packet' messages logged?"

(That one, we now know: they're sent only once right after each handshake, which is also not useful).

thanks,
-Jay

2

Yes, it would be great to see this list in the docs.

I just remembered one crazy message that had no sense at all:

Even though this specific issue is resolved, the message itself was absolutely unclear. Wtf "array is more than array" means?? :laughing:

3 
[rex@test]  > :put ({} < {})
Script Error: cannot compare if nothing is less than nothing

[rex@test]  > :put ({} > {})
Script Error: cannot compare if nothing is more than nothing

[rex@test]  > :put ({} = {})
true

[rex@test]  > :put ({} != {})
false

< = less than
> = more than

"Script Error: cannot compare if %typeA is %operation %typeB"

That is:
RouterOS does not compare certain types of variables if they are more or less than each other.

4

I understand. I just mean, one array can't be more or less that other array. They could write more clear message, something like "arrays are not comparable with > operator" or whatever. When I see "...array is more than array" phrase, I start thinking, how one array can be more than other array, and I feel bad.

5

Not only would it be useful to have a listing of error message, it would also be useful when EVERY message had its own UNIQUE ID, e.g. as an 8-digit hexadecimal numer as a topic for that message only.

Similar to the 8-digit number known from Windows error messages. Having that as a topic provides an easy index into an error message list, and also allows to select/exclude specific messages when trying to programmatically handle event messages. The currently available "topic" often include more than one message.

Situation has been improved by having regexp capability in the logging filter, but because there is no !regexp filter method it still isn't perfect. A unique ID could help.