Back to ITRS Internal Only FAQ

Internal documentation only

This page has been marked as draft.

[INTERNAL] How to enable FKM debug settings

Sometimes, there may be an issue with FKM that needs further investigation, and a detailed Netprobe log may be useful. In cases like this, we ask the customer to turn on FKM debug and send us an updated Netprobe log.

Keep in mind that enabling debug settings will produce a significant number of log entries that may quickly fill up the Netprobe log. We suggest the Netprobe’s default log size should be increased (default at 10MB).

The “Max log file size” setting can be found in the Advanced tab of the Probe entry as seen in the screenshot.

                              ![Max log file size](/faq/images/itrs-internal-only/360012502118-inline-1-max_log_file_size.JPG)

The following FKM debug settings are available, with steps to enable them:

  1. In Gateway Setup Editor, go to the Probes folder and locate the Netprobe.

  2. On the Probe’s Debug tab, add FKM2 in the Module field.

  3. Click “Setting..” in the same row. You can set the following individual settings or add an asterisk * which will enable all 6 settings for you. (The table at the bottom describes each setting)

    FKM2 debug

    FKM2 debug asterisk

  4. Click “Add new” in the Module section and add file_view_module in the Module field.

  5. Click on “Setting..” in the same row, and add find_latest_matching_file as the setting.

    View file module

Please note these are the debug settings as of GA5.3.1 and they may change over time without prior notice.
Debug Module Debug Setting Description Example log output
FKM2 setup Shows FKM sampler XML upon Netprobe startup 2020-08-27 12:26:09.716-0400 DEBUG: FKM2:setup TABLE_ACTIVETIMES: 2020-08-27 12:26:09.717-0400 DEBUG: FKM2:setup
file_view_module find_latest_matching_file Shows how FKM matches files 2020-08-27 12:26:09.721-0400 DEBUG: file_view_module:find_latest_matching_file ###### { start find_latest_matching_file( … ) 2020-08-27 12:26:09.722-0400 DEBUG: file_view_module:find_latest_matching_file szFilename: /export/home/mmuniz/geneos_setup/asset_logging/generic_log.txt 2020-08-27 12:26:09.722-0400 DEBUG: file_view_module:find_latest_matching_file expandFilename( szFilename, … ): /export/home/mmuniz/geneos_setup/asset_logging/generic_log.txt 2020-08-27 12:26:09.723-0400 DEBUG: file_view_module:find_latest_matching_file Adding [/export/home/mmuniz/geneos_setup/asset_logging/generic_log.txt] to vecFilesFound { size: 0, &: 0x7fff31835230 } as MatchedFile [ Filename:/export/home/mmuniz/geneos_setup/asset_logging/generic_log.txt Change:1598545441 Modified:1598545441, Time of last status change: 27/08/20 12:24:01, Time of last modification: 27/08/20 12:24:01 ]
FKM2 doesLockFileExist Check if lock file exists 2020-08-27 12:26:10.168-0400 DEBUG: FKM2:doesLockFileExist checking for lock file: “netprobe_54906_fkm.geneos-lock” 2020-08-27 12:26:10.170-0400 DEBUG: FKM2:doesLockFileExist checking for lock file: “Generic_FKM_Testing_Sampler_2_fkm.geneos-lock” 2020-08-27 12:26:10.173-0400 DEBUG: FKM2:doesLockFileExist checking for lock file: “/export/home/mmuniz/geneos_setup/asset_logging/generic_log.txt.geneos-lock”
FKM2 rollOver Checks if file has rolled over 2020-08-27 12:26:10.181-0400 DEBUG: FKM2:rollOver checkFile: check [1] compare(file.strCurrentFilename(/export/home/mmuniz/geneos_setup/asset_logging/generic_log.txt) vs strTempFilename(/export/home/mmuniz/geneos_setup/asset_logging/generic_log.txt)):0. [2] bFileSmaller(curr: 21922, last:21922):0
FKM2 isKeyMatched Shows if each line is matched against a key and gives true or false 2020-08-27 12:27:10.112-0400 DEBUG: FKM2:isKeyMatched Line(THU AUG 27 12:26:15 EDT 2020 THIS ERROR IS CRITICAL) Key(THIS ERROR IS CRITICAL) gives true
FKM2 checkForCondition Shows if each line is matched against a key and shows the full line from the file. 2020-08-27 12:27:10.113-0400 DEBUG: FKM2:checkForCondition Match for file 0: ‘THIS ERROR IS CRITICAL’ in ‘Thu Aug 27 12:26:15 EDT 2020 This error is critical’ 2020-08-27 12:27:10.114-0400 DEBUG: FKM2:checkForCondition - adding 2020-08-27 12:27:10.115-0400 DEBUG: FKM2:addCondition Table(2) Key(0), Sev(failed), Cleartime(0), Message(), Line(Thu Aug 27 12:26:15 EDT 2020 This error is critical)
FKM2 conditionCount Shows trigger count per sampling interval 2020-08-27 12:27:10.116-0400 DEBUG: FKM2:conditionCount nSampleCondition count in addCondition(): 1
["Geneos"] ["FAQ"]

Was this topic helpful?