Applicable for ENA v17.0 P03 upwards
To manually remove incidents with no object
To view types of stale objects
From ENA v17.0 P03 upwards, Entuity expires incidents for objects that have been stale for long enough and for objects that are no longer under Entuity management. This is a periodic cleanup job that by default runs inside the Entuity Event Management System (EMS) process responsible for cleaning up incidents for deleted and staled objects.
By default, Entuity will automatically remove incidents with no object after two weeks.
Note, from Entuity v21.0 P01 upwards, wireless controller access points remain associated with their parent device for the time specified by the stale delay value. This means that the association is not lost if the access point goes down or becomes unreachable.
To configure the cleanup job:
- If you want to configure the cleanup job so that it runs differently to the default, you can do so from the following configuration file:
<ENTUITY_HOME>/etc/event-engine-cfg-template.properties - To ensure that these changes persist between patches and upgrades, you need to edit the following file (which you can create by making a copy of the above):
ENTUITY_HOME>/etc/event-engine-cfg.properties - After making changes to the above file, you need to restart the EMS or issue the following command to reload the configuration:
<ENTUITY_HOME>/bin/eventEngine[.bat|.sh] -reloadCfg
The following are new, related configuration properties in this file:
# The time between situation cleanup jobs. Set to zero to disable the job situationCleanupPeriodSec = 3600
# The number of seconds what need to pass since object becoming stale and its situation expiry. Default is 2 weeks situationStaleTillExpiryPeriodSec = 1209600
# What age (in seconds since it's first opening) situation must be for it to be eligible for cleanup situationAgeSecEligibleForCleanup = 900
To manually remove incidents with no object:
You can also manually remove incidents with no object from the database. Incidents without an object can exist where the object/device has been removed from Entuity management, but the incident remains in the database. This can cause database performance issues.
- From the command line, access entuity_home\bin
- Enter swmaint -r
To view types of stale objects:
To help with configuration problems, you can view the types of stale objects present on the database.
- From the command line, access entuity_home\bin
- Enter swmaint -t
Comments
0 comments
Please sign in to leave a comment.