Another option is to set the DWH_SAMPLING back to 60 and restart dwh.
This will lower the granularity of the dashboard calculations.
The dwh db size grow since now it samples the statistics every 15 seconds instead of once a minute.
Best regards,
Shirly Radco
Hi Didi,
El 2016-09-01 14:02, Yedidyah Bar David escribió:
On Thu, Sep 1, 2016 at 3:26 PM, Sandro Bonazzola <sbonazzo@redhat.com>
wrote:
Didi, Shirly, can you help here?
On Thu, Sep 1, 2016 at 8:52 AM, <nicolas@devels.es> wrote:
Hi,
Since we upgraded to 4.0.x, DWH's PostgreSQL database is getting
really huge. Is there a clean way to limit its size, like setting
a maximal retention time for DWH data?
Earlier today replied to a similar question, search list archives for
"Change Engine History Logging from Advanched to Basic".
Just to confirm: I already have basic DWH configured, and the content of /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-scal e.conf is:
DWH_TABLES_KEEP_SAMPLES=24
DWH_TABLES_KEEP_HOURLY=720
DWH_TABLES_KEEP_DAILY=0
So according to [1] regarding "DWH_TABLES_KEEP_HOURLY":
The number of hours that hourly data is stored. The default is 60 days.
Hourly data more than two days old is aggregated into dailydata.
if I reduce that value to say 240 (10 days), any older entry from that should be erased upon a DWH restart, right?
Thanks.
[1]: https://access.redhat.com/documentation/en-US/Red_Hat_Enterp rise_Virtualization/3.6/pdf/ Reports_and_Data_Warehouse_ Guide/Red_Hat_Enterprise_ Virtualization-3.6-Reports_ and_Data_Warehouse_Guide-en- US.pdf
Best,
Thanks.
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [1]
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community
collaboration.
See how it works at redhat.com [2]
[3]
--
Didi
Links:
------
[1] http://lists.ovirt.org/mailman/listinfo/users
[2] http://redhat.com
[3] https://www.redhat.com/it/about/events/red-hat-open-source- day-2016