Forum Discussion
Andreas_Lamprec
Nov 27, 2012Nimbostratus
Analytics module (Advanced Visibility and reporing) historical data
Hello!
I've enabled the AVR module with "minimal" resource provisioning on a LTM VE version 11.2.1.
It seems there is very limited storage of historical data. For the last hour, the graphs ...
Andreas_Lamprec
Jan 28, 2013Nimbostratus
Hello!
We opened a support case and after a long time we got the answer that there is no chance to change the granularity of the saved data.
The full answer was:
By design, external data is a requirement for the granularity. Internal data collection is limited to allow for storage and performance limitations. For this reason, AVR aggregates data according to the following:
First 2 hours it keeps data aggregated every 5 minutes
After 8 hours it keeps data aggregated every 1 hours (60 minutes)
After 2 days it keeps data aggregated every 4 hours (240 minutes)
After 2 weeks it keeps data aggregated every 24 hours
After 2 months it keeps data aggregated every 1 week
After 1 year it keeps data aggregated every 4 weeks
Other internal limits are;
chart capacity is limited to 1 year
Captured transaction data is limited to 1000 records and although new records are being displayed in the gui, the old records must be cleared before the new records are stored.
Greetings!
Andreas
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects