Historic Monitoring Data - should be maintained for a minimum of 62 days

Getting noticed

Historic Monitoring Data - should be maintained for a minimum of 62 days

A typical reporting scenario is to run a report covering the previous calendar month.  Meraki's API contains too little history to support this common use case.


For example: https://documenter.getpostman.com/view/897512/SzYXYfmJ#6cd07712-f30e-49ac-ab25-2eaf80e1f9d0 


Here we can see that only 31 days of history are permitted, making it impossible to query "previous calendar month" unless the call is perfectly timed for midnight on the 1st of the month (which it can never be, particularly if a sequence of API calls are required).  The Meraki API should support the retrieval of "December" data in any of the 31 days of January.  For this reason, historic data should be maintained for a minimum of 62 days.


Please extend the storage period accordingly.


Author, https://www.nuget.org/packages/Meraki.Api/
Kind of a big deal
Kind of a big deal

There are no regulations that relate to aggregated network traffic monitoring, otherwise companies like SolarWinds, LogicMonitor, ScienceLogic, DataDog etc. would all be out of business!


Unfortunately, without longer data retention times, to report such data, all MSPs will have to purchase a separate solution, such as the above.


With better data retention times for aggregated data only, the need for such a solution will be reduced.

Author, https://www.nuget.org/packages/Meraki.Api/
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.