It’s clearly a bug and bug should be reported to Mikrotik support (can be via e-mail support@mikrotik.com). This is a forum with many users’ discussions and it’s not closely monitored by MT staff, hence it’s not appropriate form of reporting a bug.
@wfburton
What you have written is completely inconclusive, useless, silly, etc.
What are you talking about?
What version of RouterOS is it?
What generated the log?
Where do you read the log?
Etc.
I think @mkx has some good advice. If you generate supout.rif and attached to bug report (using https://help.mikrotik.com or support@mikrotik.com should work too) that should have the various system/config details that @rextended refers. Also, if this is a new problem in 7.10.x, make sure to state that (e.g. “it broken after upgrade” vs “I just noticed this”).
It could be a filter in rsyslog cutting out a number, but I guess that is not the case.
I do use Rsyslog both as MT user and at work and have done some mistake over the year.
See my post here on how to configure rsyslog:
http://forum.mikrotik.com/t/tool-using-splunk-to-analyse-mikrotik-logs-4-0-graphing-everything/153043/1
If you like to play around and graph the logs, see my post using Splunk here:
http://forum.mikrotik.com/t/tool-using-splunk-to-analyse-mikrotik-logs-4-0-graphing-everything/153043/1
You can use SNMP with Splunk.
- SNMP Modular Input Easy to setup, but not free.
- Splunk Connect for SNMP (SC4SNMP) Free, but need some knowledge to setup.
Since I can get nearly all that I need with commands on the router, I can send that using Syslog insted of request data from Router with SNMP.