Monitoring Device Administration › How the Management Console Manages Database Growth › Database Growth Control

Database Growth Control

To manage the 120 million row maximum, the management console:

• Filters each combination, using a minimum threshold for Network Round Trip Response Time (NRTT), to limit the impact of periodic client and server messages, such as keep-alives, on monitoring statistics in reports, and to control database growth.

  If the number of NRTT observations during a 5-minute interval does not meet the minimum threshold, the management console does not create rows for that combination in the database.

  From a reporting perspective, a filtered combination would prevent the management console from reporting session-level statistics for the filtered 5-minute interval, but the response time metrics for the application across the network are still valid.

  If you do not want the management console to filter or groom an application, prioritize the application.

  By default, the management console filters combinations for non-priority applications that have less than 10 NRTT observations during a 5-minute interval.

• If the moving average for the row creation rate is too high, the management console limits the number of incoming rows by grooming low-volume applications that have the smallest number of application/server/network combinations. When the management console grooms an application, it does not create rows for the application/server/network combinations in the database. The management console does not groom priority applications or the busiest application on a server.

  Grooming helps the management console maintain its database maximum of 120 million rows, and at same time, lets you report on the monthly time period that you want for the most interesting applications with the highest number of application/server/network combinations. The management console disables grooming when the moving average for row creation returns to an acceptable rate.

  From a reporting perspective, the management console rates groomed application data as No Data (white).

  If you do not want the management console to filter or groom an application, prioritize the application.

• If grooming does not successfully lower the moving average for the row creation rate, the management console does not create rows for non-priority application combinations with the smallest packet volumes. When the moving average for row creation returns to an acceptable rate, the management console resumes normal monitoring of non-priority applications.

  From a reporting perspective, a filtered combination would prevent the management console from reporting session-level statistics for the filtered 5-minute interval, but the response time metrics for the application across the network are still valid.

  If you do not want the management console to filter or groom an application, prioritize the application.