A number of clients have experienced the above issue where, when an Active Time kicks in an FKM trigger alert is being displayed in the dataview despite the error message (trigger) occurring outside of the Active Time.
The resolution is to set the Active Time on the FKM table itself
FKM Sampler with an Active Time of 9:00 - 17:30
The root cause of this is the wrong configuration of the Active Time on the FKM. i.e. setting it on the FKM file (files > file > activeTime) as seen in the below screenshot:
When this setting is chosen for the Active Time configuration, during the inactive state, the file will stop being read at X and when active, will continue reading the file at Y where it left off. This results in the Fail and Warning triggers set in the FKM table to still react to triggers during the inactive state. Consequently, when it becomes active, it would display a trigger (if applicable) during the inactive period.
In order to stop the incoming false alerts from triggering, you need to set the Active Time on the FKM table itself. As seen in the following screenshot:
Setting an Active Time here will mean that the file will continue to be read, but the file has NO table to react to and therefore no triggers would be produced during the inactive state, eliminating any false alerts.