Even if it were 365 days, which I assume would be tested as 31536000 seconds internally... - you'd still need to cope with leap years by separately acquiring an extra day - 365 'days' from when? 00:00:00 UTC? each local network's time zone? individual device clocks? some timestamp in a table? etc. - this sort of thing is not well defined across the API documentation (this is not unique to Meraki) - devices do not report instantly, there's a delay - unless you could nail acquisition at exactly 365 days since last time, you'll lose data or maybe have an overlap, due to latency, clock errors, rate limits, outages etc. Because I'm picky about time, I spent a while digging into this stuff when creating a platform that acquires/analyses data from Meraki and other SDN platforms. I decided it's better overall to acquire in shorter chunks month/day/whatever, then there's margin to recover from problems, and avoid edge effects due to retention period cut-offs.
... View more
