|
|
|
The amount of data that can be stored in the UC Monitor database depends on the volume of call activity on your network. We recommend the following limits on data storage to avoid performance degradation. The UC Monitor database can accommodate a maximum of 500 million rows per data table. We recommend no more than 200 million rows per data table, to allow for spikes in growth.
|
Call Volume |
10 million calls |
6.6 million calls |
3.3 million calls |
|---|---|---|---|
|
Data Type |
|
||
|
Interval data. Collected during regular monitoring at 15-minute intervals by the collector. Includes incident data. |
5 months |
8 months (default) |
15 months |
|
Summary data. Generated by the management console for long-range reports such as the Capacity Planning reports. |
5 months |
8 months (default) |
15 months |
|
Call data. Data about individual calls. |
5 months |
8 months (default) |
15 months |
|
Defined Call Watch data. Data from watched phones. |
5 months |
8 months (default) |
15 months |
|
Automatic Call Watch data. Data from automatically watched phones in Avaya environments. |
3 days |
7 days (default) |
14 days |
|
Midstream device data. Medianet flow metrics and device information. Recommendations are based on an average of three midstream devices per 3-minute call. |
1 day |
2 days (default) |
4 days |
|
Abandoned call data. Data from calls that were abandoned before they were completed. |
Although some information about abandoned calls can be helpful, retaining too many of this type of call can lead to degradation of report performance. By default, UC Monitor stores data from abandoned calls for three months. |
||
| Copyright © 2012 CA. All rights reserved. |
|