Monitor Statements with the Cloud Console

You start a stream-processing app on Confluent Cloud for Apache Flink®️ by running a SQL statement. Once a statement is running, you can monitor its progress by using the Confluent Cloud Console.

Important

Confluent Cloud for Apache Flink®️ is currently available for Preview. A Preview feature is a Confluent Cloud component that is being introduced to gain early feedback from developers. Preview features can be used for evaluation and non-production testing purposes or to provide feedback to Confluent. The warranty, SLA, and Support Services provisions of your agreement with Confluent do not apply to Preview features. Confluent may discontinue providing Preview releases of the Preview features at any time in Confluent’s sole discretion. Check out Getting Help for questions, feedback and requests.

For Flink SQL features and limitations in the preview program, see Notable Limitations in Public Preview.

  1. In the Flink SQL shell or in a Confluent Cloud Console workspace, run a SQL statement to start a Flink statement.

  2. Log in to the Confluent Cloud Console.

  3. Navigate to the Environments page.

  4. Click the tile that has the environment where your Flink compute pools are provisioned.

  5. Click Flink (preview).

    The Statements list opens.

  6. You can filter for running statements by clicking the Status filter above the statements list.

  7. For each statement, you can see the rate at which records are read (Messages in per min) and written (Messages out per min). Also, the consumer lag for each statement is displayed (Messages behind). For all three values, the sum over all inputs for output tables/topics and partitions is shown.

    A low, close-to-zero consumer lag is the best indicator that your statement is running smoothly and keeping up with all of its inputs. A growing consumer lag indicates a problem: check the exceptions (see next steps).

  8. When you click on a particular statement, the details view opens. In the Overview section, the statement’s SQL source code is displayed.

  9. Click Exceptions.

    The error log opens. If your statement is experiencing issues, errors and runtime exceptions are listed with the corresponding timestamp for when it occurred.

  10. Click X to dismiss the details view.

  11. Click Compute pools.

    The details view opens and shows details for the current Flink compute pool.