Develop > Developer Reference > Creating Discovery and Integration Adapters > Developing Generic Adapters > How to Troubleshoot and Debug Using Generic Adapter Log Files

How to Troubleshoot and Debug Using Generic Adapter Log Files

For troubleshooting and debugging, use the following:

  • Adjust logging levels in these files (set the loglevel variable to TRACE for the most detailed results):

    • <UCMDB_DataFlowProbe>\conf\log\fcmdb.push.properties

      <UCMDB_DataFlowProbe> is the UCMDB Data Flow Probe installation directory.

    • <UCMDB_Server>\conf\log\reconciliation.properties

      <UCMDB_Server> is the UCMDB Server installation directory.

  • Analyze the following Generic Adapter log files by considering the following three scenarios:

    • If integration.log.mode=0, that is, all the log messages are included in fcmdb.push.all.log, analyze the following log files:

      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.all.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.configuration.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.connector.all.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.connector.configuration.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.mapping.log

    • If integration.log.mode=1, that is, both fcmdb.push.all.log and separate log files based on integration point names are generated, analyze the following log files:

      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.all.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.configuration.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.connector.all.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.connector.configuration.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.mapping.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.<integrationPointName>.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.<integrationPointName>.configuration.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.<integrationPointName>.connector.all.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.<integrationPointName>.connector.configuration.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.push.<integrationPointName>.mapping.log

    • If integration.log.mode=2, that is, only separate log files based on integration point names are generated, analyze the following log files:

      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.<integrationPointName>.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.<integrationPointName>.configuration.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.<integrationPointName>.connector.all.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.<integrationPointName>.connector.configuration.log
      • <UCMDB_DataFlowProbe>\runtime\log\fcmdb.<integrationPointName>.mapping.log

  • Analyze the following generic log files:

    • <UCMDB_DataFlowProbe>\runtime\log\probe-error.log
    • <UCMDB_DataFlowProbe>\runtime\log\WrapperProbeGw.log
    • <UCMDB_Server>\runtime\log\error.log
    • <UCMDB_Server>\runtime\log\cmdb.reconciliation.log

Related information:

How to Generate Separate Generic Adapter Log Files

Send Help Center feedback