To view the list of Archived issues, navigate to the Issues tab, then toggle the Archived button at the top right corner.
The Archived list is an accumulation of historical records of all the issues detected. Generally, users archive issues that no longer require their attention. When an issue is archived, it is automatically removed from the Active list and moved to the Archived list.
See 3.2 Issues Tab for more details.
Automatic archiving of resolved issues
In releases prior to v25.1.0, LiveAssurance retains all resolved issues in the Active issues list until they are manually archived; there is no aging algorithm. Starting in v25.1.0, issues that have been in Resolved state for more than 30 days (default) are automatically archived. The archiving process runs as a background task every 24 hours (1440 minutes), by default.
If required, you can add an overwrite.conf file
(/usr/share/indeni/conf/overwrite.conf) to override these
default values present in the application.conf file.
You can customize the duration (in hours) after which you want the issues to be
archived, by modifying the default value for archive-after-hours to
set the desired value. Similarly, you can customize the archiving interval (in
minutes) by modifying the default value for
archiving-interval-minutes.
The following snippet shows an example of the alerts section in the
overwrite.conf file that overrides the default values for the
duration and interval:
indeni-server {
alerts {
archiving-interval-minutes = 720 # 12 hours
archive-after-hours = 240 # 10 days
}
}For more details on the overwrite.conf file, see Persistent Server Configuration.
- The automatic archiving feature is also applicable to existing issues, upon upgrading to v25.1.0.
- Issues in Cooldown state are not considered resolved, so such issues will not be automatically archived.
Restoring an issue
To restore an issue, select the issue and then select Unarchive in the issue summary drawer that opens, as shown in the following image. The issue will return to the Active issues list.
When an issue is archived, the system halts email notification relating to the issue. The system will continue to populate the Notes section with the state change information. It will continue to update Syslog, the incident ticket (if applicable) and SNMP. This way, when you decide to restore the issue, you will have the historical information about the issue.