Related to:

FKM match key issue, FKM keyword, not finding string.

Problem

FKM not picking up the string correctly

Possible Cause(s)

There are numerous causes why FKM not picking up the string correctly. In this article, we will summarize some of the common ones.

Root Cause 1: Misconfiguration of file source

• • Common misconfiguration:
    • Incorrect file path of the file source is supplied
    • Incorrect files > file > contentType is selected
    • wildcardMonitorAllMatches setting is disabled while wildcard is used in the path of file source to monitor more than one file
    • Incorrect format of date keyword is used

Root Cause 2: Misconfiguration of the setting of the key table

• • Key table contains the actual key definition. Common misconfiguration:
    • Search string
      • • Misspell of search string
    • Rules
      • • Misconfigured regular expression if the match mode “Regexp” or “Regexp_ignore_case” is selected for fkmTable > keys > key > setKey > match > rules

Root Cause 3: The user running the NetProbe has no permission to read the file. In such case, “NOT_FOUND: Permission Denied” status message is shown

Root Cause 4: The FKM trigger key is cleared by clear key

Root Cause 5: fkmTable > keys > key > clearTime is set, the trigger row is removed from the dataview after the number of seconds set of clearTime has passed

Root Cause 6: Keyword is detected out of the active time if active time is set

Root Cause 7: The key is ignored by an ignore key

Root Cause 8: Incorrect file content type files > file > contentType is set

Possible Solution(s)

Below are the corresponding possible solution of each of the problem above: 

Solution Root Cause 1: Any suspected misconfiguration of the file path of file source

• • It can be verified by
    • enable display > columns > Absolute path under the sampler’s advanced tab. This displays the full path to the file including the filename on the dataview
    • use the full path(s) of the file(s) if implicit path using wildcard or date keyword is used and suspected with issue
  • If files > file > source > stream is used, make sure the value must be a fully qualified stream name, with the format: managedEntity-name.sampler-name.stream-name
    
    

Solution Root Cause 2: Issue with match mode set to “Regexp” or “Regexp_ignore_case” and problem with regular expression is suspected:

• • verify the regular expression format. For more information on using regular expressions on FKM, see Regular Expressions
  • enable / disable Perl Compatible Regular Expressions (PCRE) option. If disabled, FKM use the Portable Operating System Interface (POSIX) extended regular expressions. Beginning Geneos 5.4.x, the FKM plugin uses PCRE by default. For difference between POSIX and PCRE, see Notable differences between POSIX and PCRE
  • if the regular expression contains special character which you want to match it literally, you will need to use the back slash “\” to escape the character. For the list of the special characters that require escaping for literal match, see Regular Expressions
  • Do not use Negative Regular expressions (A negative pattern in a regular expression that returns matches that are not equal to a specified pattern).
    
    

Solution Root Cause 3: Make sure the user running the Netprobe has the necessary permissions to the directories and files. In the case of running Windows Netprobe, the typically Netprobe runs as a Windows service as "Local System Account", and this process has no access to mapped drives, only local files is accessible to FKM

Solution Root Cause 4: If a file line matches the match key (creating a trigger) and a file line later match this clear key, the created trigger will be automatically removed

Solution Root Cause 5: All triggers of a file is cleared at the defined time of day if a clear time is set

Solution Root Cause 6: If active time is used, the place where you set in the sampler configuration impacts when and how the file is read. If a keyword is not picked up, you might have active time set on file-level or keyword table-level. During the time is inactive, file lines are not scanned for the keyword.

Solution Root Cause 7: When ignore key is detected, it silently ignores the line which would otherwise match a key and create a trigger

Solution Root Cause 8: Make sure the correct file content type files > file > contentType is set. For more information of possible values of file content type, please see here

Related Articles

File Keyword Monitor (FKM)

File Keyword Monitor Configuration

Why is the FKM unable to detect some files

If Issue Persists

• Please contact with our Client Services team via the chat service box available in any of our websites or via email to support@itrsgroup.com
  
  
  
• Make sure you provide to us:
  • FKM sampler configuration in xml
  • Monitored file in question
  • Screenshot of FKM dataview if error is seen on it
  • Any troubleshooting step already verified from the ones described in this article.