The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
All data collection tasks (and data purging tasks) are controlled from the Jobs Dashboard. See Manage Jobs Using the Jobs Dashboard. Data collection jobs are listed under System Jobs .
Changes you make on the Data Retention page determine the information that is displayed in the web GUI. You can open the data retention page by choosing
, then choosing .For example, if you do not need any historical performance data older than 7 days, you can modify the performance data retention values as follows:
Short-term Data Retention Period—1 day
Medium-term Data Retention Period—3 days
Long-term Data Retention Period—7 days
If you specify these settings, all data displayed in performance reports and on performance dashboards will be for the previous 7 days only. When you generate a performance report, even if you select a reporting period longer than the last 7 days, the report will contain data from the last 7 days only (because that is all of the data you selected to retain).
Similarly, if you view a performance dashboard and select a time frame longer than one week, the dashboard will contain date from the last 7 days only.
Note | Cisco recommends you do not change the retention periods for trend, device health, system health, and performance data because the default settings are optimized to get the most helpful information from interactive graphs. |
The following table describes the information shown on the Data Retention page.
Type of Data |
Description |
Default Retention Settings |
---|---|---|
Trend |
Device-related historical information. Trend data is gathered as a whole and summarized as minimums, maximums, or averages. |
Hourly data: 15 Daily data: 90 Weekly data: 54 weeks |
Device health |
SNMP-polled device data such as device reachability, and utilization for CPU, memory, and interfaces. |
Hourly data: 15 Daily data: 90 Weekly data: 54 weeks |
Performance |
Assurance data such as traffic statistics. |
Short-term data: 7 Medium-term data: 31 Long-term data: 365 days |
Network audit |
Audit records for configurations triggered by users, and so on. |
90 days |
System health |
Includes most data shown on the Admin dashboards |
Hourly data: 15 Daily data: 90 Weekly data: 54 weeks |
For example, these are the retention settings for optical performance data:
Note | These default purging settings are provided to ensure optimal performance. Use care when adjusting these settings, especially if Cisco EPN Manager is managing a very large network (where increasing these settings may have an adverse impact). |
Cisco EPN Manager stores a maximum of 8000000 events and 2000000 syslogs in the database.
To protect system performance, Cisco EPN Manager purges alarms, events, and syslogs according to the settings in the following table. All of these settings are enabled by default. Data is deleted on a daily basis. Alarm tables are checked hourly, and if the alarm table exceeds the 300,000 limit, Cisco EPN Manager deletes the oldest cleared alarms until the alarms table size is within the limit.
Data Type |
Deleted after: |
Default Setting |
Alarms—Cleared security alarms |
30 days |
Enabled |
Alarms—Cleared non-security alarms |
7 days |
Enabled |
Events |
60 days |
Enabled |
Syslogs |
30 days |
Enabled |
Alarms |
30 days |
Disabled |
To change the settings, choose
, then choose and modify the settings in the Alarm and Event Cleanup Options area.You can adjust the purging settings for logs by choosing
. Logs are saved until the reach the maximum size. At that point, a number is appended to the log file and a new log is started. When the number of logs exceeds the maximum, the oldest log is deleted.The following table lists the default purging values for General and SNMP logs.
Log Type |
Size of Logs |
Number of Logs |
To change the setting, see: |
General |
10 MB |
10 |
|
SNMP |
10 MB |
5 |
By default, reports are stored in a repository named /localdisk/ftp/reports and are deleted after 31 days from that directory. Reports filters that you set from the filters page are saved in the database and are not purged.
By default, 2 backups are saved for backups in local repositories. If you are using remote repositories, there is no automatic backup purging mechanism; you must manually delete old backups. See Change the Number of Automatic Application Backups That Are Saved.
For each device, 5 configuration files are saved in the configuration archive. Any file that is older than 30 days is purged. Device configuration files cannot be manually deleted. For more information on device configuration files, see Manage Device Configuration Files.
Device software image files are not automatically purged from the database. They must be manually removed using the GUI client. For more information, see Delete Software Image Files from the Image Repository.