Answer:

The Netprobe log should be useful as a starting point for troubleshooting Netprobe issues. While there is currently no specific documentation on contents of the log file, we have collected some general information here as a reference.

1. Netprobe startup and shutdown

(a) Startup

• Netprobe version, paths, user, schema version, heartbeat and timeout options, various Netprobe environment variables, port number

(b) Shutdown

• Signal received and clean up

2. Gateway connection and disconnection

(a) Connection

• Gateway name, gateway host, heartbeat and timeout options, samplers and sampling interval

(b) Disconnection

• Socket errors and gateway host

3. Initialization of Samplers

Some plugins especially those that load more libraries may write additional information during initialization

• Monitored Days options (FTM plugin)
• Java / JVMManager library (JMX, E4JMS, Tibco RV, IBMi plugins)
• MQLibraryManager library (MQ plugins)
• CURL library (Web-Mon plugin)
• Market Data feed library (Market Data Monitoring plugin)
• Local database and cache (FIX Analyser 2 plugin)

4. Other Informational Messages

• When an Active Time changes from active to inactive and vice versa
• When SampleNow command is invoked

5. Other Warning and Error Messages

• The Netprobe log should be generally quiet during normal operations. If errors are encountered, the messages logged would largely dependent on the individual plugin and situation. You may look for the error messages in the product documentations or FAQ section for more information.

6. Debug Messages

The Netprobe and plugins may include certain debug settings, which are not turned on by default. If necessary, ITRS may also provide special Netprobe version (non-GA) that outputs additional debug information. The debug settings are suggested to be enabled only when advised by ITRS personell as needed.

Related articles:

• Netprobe documentation

If you need further help:

• Please contact our support team via the chat service box on any of our websites or raise a support request.
  
• Make sure you provide us with:
  • Background of the issue or request.
  • Use cases, requirements, business impact, etc.
  • Encountered error messages.
  • Log files or diagnostic files.
  • Screenshots.
  • And other important information relevant to your inquiry.