The interface menu retains total bytes/packets in/out for each interface. You can copy out the numbers on the first of each month than zero it for next month.
I have a script which is exporting RX/TX values twice a day to a file on MTiK.
When I need statistics, just download the file on my computer and process it within excel to get information needed.
Since MTiK file size shouldn’t be more that 4 kb, another script warns me when file reaches 3.5 kb.
One nice thing I will never hesitate to say about using MT gear over the past 12 years is that gratuitous reboots have rarely been an issue, especially where you employ a UPS.
My very first MikroTik was installed in the desert, at the top of a windmill. Used to operate 11 months straight without a break inside a metal enclosure, 0-49°C outdoor temp (hotter in the box), until seasonal monsoon storms hit the area each autumn and town experienced total power outages.
Over 100 days uptime and I had to restart it yesterday.
HAP AC, 2.4 and 5 GHz links up, clients were disconnected while connected through 5 GHz link, forgot what was the error in the log
anyway working normally after reboot
Somehow related to the original post, I discovered that adding registered devices to IP/Kid Control, offers some stats (bytes up/down, rates up/down) about each device activity, stats that are still there after a reboot. Stats can be reset manually via Reset Counter button. In a relatively stable environment (let’s say household) with 99% of devices known and registrable, I think it’s a good way to monitor monthly traffic, totally or per device.