Old FKM alerts, file read from beginning, trigger for alerts already accepted, FKM alert repeated, FKM trigger repeated, duplicate FKM alerts, duplicate email alerts for FKM file, out of time alerts for FKM file, Repeat FKM alerts
- Problem 1- The FKM sampler is reading the file from the beginning, causing the dataview to show a repeat of old triggered keys for the file.
- Problem 2 - The file you are monitoring has changed names and you are seeing alerts for previously triggered entries. For example, you are monitoring a file using the following file path with a wildcard /export/home/mmuniz/FKM_TEST_FOLDER/application*.log. The sampler has picked up a file called application_1.log. At the end of the day this file gets renamed to application_1_old.log and you notice the FKM sampler has picked up this file and alerts you on all the previous triggers. Screenshot below for reference:
- Problem 3 - The FKM sampler is showing old trigger keys or triggering keys during a time you were not expecting.
- Root Cause 1 - This is covered in our Geneos - FKM reading file from the beginning Troubleshooting Guide.
- Root Cause 2 - This behavior occurs when the Wildcard Monitor All Matches setting (under the FKM advanced tab at the bottom of the sampler record) is disabled (by default).
- Root Cause 3 - If the FKM sampler has an Active time record defined on the sampler level (under the sampler Advanced tab), this causes the FKM's file pointer to stop monitoring the file when the sampler is inactive. Once the sampler becomes active again, the file pointer will alert on triggers from the point it left off at. Causing the FKM sampler to alert you on triggers between the end time and start time of the active time record.
- Solution Root Cause 1- This is covered in our Geneos - FKM reading file from the beginning Troubleshooting Guide.
- Solution Root Cause 2 - Enable the Wildcard Monitor All Matches setting (under the FKM advanced tab at the bottom of the sampler record) so the FKM view creates a separate entry for each file that follows the file path wildcard pattern.
- Solution Root Cause 2 (1) - Instead of defining the active time record on the sampler level, set the active time on the file entry itself. Setting the active time on the file level avoids the FKM sampler's file pointer from detecting file triggers during the inactive time period, and displaying them once the active time on the file entry becomes active. Screenshot below for reference.
- Solution Root Cause 2 (2)- As an alternative to defining an active time record on each file, you can set an active time to apply to all the files with the Default file active time setting (found in the Advanced tab at the bottom of the FKM sampler). Screenshot below for reference:
- File Keyword Monitor (FKM)
- Duplicate or out of time email alerts
If Issue Persists
- Please contact our Client Services team via the chat service box available in any of our websites or via email to firstname.lastname@example.org
- Make sure you provide to us:
- The troubleshooting steps done (refer to the Possible Cause and Solution sections of this article)
- Date and time of the issue
- FKM sampler.xml and any related ActiveTime xml file.
- Screenshot of the FKM dataview if possible
- Complete Gateway Log
- Gateway and Netprobe version