Troubleshooting – Cloud Foundry Event Discovery

This section describes troubleshooting for the Cloud Foundry Event Discovery.

• Check whether the CloudFoundry Event Monitor job is started successfully

  In the communication log, if the following information occurs, the connection between Data Flow Probe and Cloud Foundry is established:

  <log start="11:07:38" severity="info">Start sourceCloudFoundry event pulling</log>

  <log start="11:07:38" severity="info">Start CloudFoundry event source...</log>

• Check whether the CloudFoundry Event Monitor job can receive events successfully

  In probeMgr-adaptersDebug.log of Data Flow Probe on which the CloudFoundry Event Monitor job runs, if the following information occurs, the job can receive events from the target Cloud Foundry:

  <2016-10-08 16:20:37,562> [DEBUG] [JobExecuterWorker-0:CloudFoundry Event Monitor:Event Hub Worker:Thread-5] - Event type:audit.space.create

  <2016-10-08 16:20:37,563> [DEBUG] [JobExecuterWorker-0:CloudFoundry Event Monitor:Event Hub Worker:Thread-4] - handle event {...}

  <2016-10-08 16:20:37,891> [DEBUG] [JobExecuterWorker-0:CloudFoundry Event Monitor:Event Hub Worker:Thread-4] - Reported CIs: [...]

• Check whether the CloudFoundry Event Monitor job works continuously

  In the communication log, if the following information is printed out every 30 seconds to indicate the monitor is working, the connection between Data Flow Probe and Cloud Foundry is established:

  <log start="11:07:40" severity="debug">Get Event from: 2016-09-29T03:13:41Z</log>

• Check whether connection issues occur between Data Flow Probe and Cloud Foundry

  In the communication log, if the following information occurs, the connection between Data Flow Probe and Cloud Foundrycannot be established:

  <log start="14:18:34" severity="debug">Failed to connect to CloudFoundry.

  ...

  </log>