Entering Downtime incident is very slow


 Product(s):APM Implementation and Performance Management
 Version(s):prior to 712.1
 Environment:all
 Area:N/A
 Subarea:N\A

Problem

System slows to a crawl when adding a new downtime entry to an asset. 

Each time a  downtime incident is added to an asset, the asset's existing collection of downtime incidents is analyzed to determine if the new incident’s start date/time overlaps any of the existing downtimes’ start date/time and end date/time.

When adding new downtime incident to an asset which has thousands of previous incidents, the addition of a new one will be very slow due to the volume of validations taking place.

 



Solution

In APM Version 7.12.1, we introduce the ability to bypass this logic check.  New Setting:

See Also

In APM Help - Allowing Overlapping Downtime Incidents

DevOps - Work item 176206 - workaround to bypass the validation 

DevOps - Bug 281640  - to fix the speed if validation bypass is not used

SR - 7000987457