I’m currently looking for an easy way to get some data volume statistics (monthly usage info)
It seems Mikrotik does not have anything out of the box (to reduce flash writes maybe?)
Must haves:
Get monthly (this and previous month) information about Download/Upload
Optional/Nice to Have:
information for the last 12 months
Per Device (IP/MAC?) or Interface statistics
I’ve found a couple ways but all seem to be very custom or require an external server which I’m not really happy about;
no monthly intervals, only cover what appeared from last boot
Custom scripts
Some funny script which exports the daily status and resets the counters once a month? Alrough this will loose some data during reboots/firmware updates.
Someone wrote something here; https://github.com/muhannad0/mikrotik-traffic-counter
But that again needs a server running somewhere
Is there any obvious, simple and robust solution?
It seems all the ways I’ve found are just too complex.
You don’t provide any scenario requiring monitoring, so this is a generic answer. As a low impact home solution, you can make a simple queue to monitor your gateway interface and reset it manually each month. You can make a queue for each user/client, and do the same thing. The problem with services running on small embedded devices is always overhead. Many brands offer some sort of monitoring with a fancy GUI, but there’s a cost to it, one way or another. For professional/lab applications, having an external device/server isn’t generally an issue. MT has The Dude, but there are other solutions for ISP/WISP operators. Lots of threads on Reddit. If you are inquiring for a commercial application, consultants are also available.
One usecase would be a LTE router where want to get an idea about the data you consumed.
Personally I just want to get an overview about the data usage on my internet connection.
Per device would be a nice bonus, but not necessary.
Queue seem to not survive reboots/firmware updates, so those are not really an option.
Also, I’m not asking for a fancy gui. It’s just a couple numbers.
Those do not create any real overhead.
It seems they’ve chosen to just store them in RAM to reduce eeprom/flash writes and thus increase endurance.