Configuring the DBTuna Aggregation Interval
The "aggregation interval" is the time in minutes that the DBTuna agent will write out collected performance data to disk, and therefore allow it to be visualized in the user interface. Out of the box DBTuna will log data every minute, but depending on your environment this may be too frequent, and you may be happy with longer intervals.
There are positives and negatives to short aggregation periods, check the list below to help you work out what is best for you.
Positives:
- More granularity - See within a very small time window what is happening
- Almost real-time access to data - If you need to know what's going on in your databases in almost real time, then shorter aggregation intervals are best
Negatives:
- More storage is required to store the history - If you want to keep weeks or even months of granular data, then having short aggregation intervals will consume much more disk space. e.g. Data in chunks of one minute, will consume almost 5 times that of 5 minute aggregation intervals
- (Slightly) more overhead - DBTuna will run additional monitoring queries at the end of each interval, therefore shorter aggregation intervals will mean that more queries are hitting your monitored database and therefore the overhead will be more N.B. This will probably not be a big issue, as the overhead to monitoring should be negligible
How granular do you need your data?
Check out the screenshot below to compare different intervals!10 Seconds -- 1 Minute -- 5 Minutes -- 15 Minutes
To set your aggregation in DBTuna you need to edit the dbtuna.properties file located in the [dbtuna installation directory]agent directory. There is a property called agg-interval, which is a numeric value specified in minutes. Out-of-the-box this is set to 1 (i.e. One minute), therefore it can be changed to any integer value.
REQUEST A DEMO
START A FREE TRIAL