All Products
Search
Document Center

Realtime Compute for Apache Flink:View boot and operational logs

Last Updated:Aug 06, 2026

You can view boot and operational logs for a running deployment. This topic shows you how.

Background information

Type

Description

boot log

A boot log contains events that occur during a deployment's startup, from the initialization of the Flink environment until the JobManager is running. For details, see View boot logs.

Note

The boot log does not contain scheduling logs. To find information about scheduling events, such as insufficient resources or a shortage of vSwitch IP addresses, check the runtime events.

operational log

An operational log contains logs from the JobManager and TaskManagers. You can view these logs on the Logs page or in the Flink UI. For more information, see View operational logs.

Prerequisites

The deployment must be running.

Usage notes

Logs are paginated. Each page displays up to 1 MB of data (about 8,000 to 9,000 entries), which is typically sufficient for troubleshooting. If you cannot identify the issue on the first page, navigate to subsequent pages.

View boot logs

  1. Log on to the Realtime Compute for Apache Flink console.

  2. Find the desired workspace and click Console in the Actions column.

  3. In the left-side navigation pane, choose O&M > Deployments.

  4. Click the name of the desired deployment.

  5. Click the Logs tab.

  6. On the Startup Logs tab, view the boot log.

    seconds: [900]
    end new OSSLogClient endTimeInMs:[xxx 47], costInMs:[22 ms]end new AbstractVvpLogAppender endTimeInMs:[17222176513...]
    09:47:31,625 [main] INFO  org.apache.flink.runtime.entrypoint.ClusterEntrypoint          [] -
    ------------------------------------------------------------------------------------------------------------------------------
    xxx 09:47:31,643 [main] INFO  org.apache.flink.runtime.entrypoint.ClusterEntrypoint          [] - Preconfiguration:
    xxx 09:47:31,644 [main] INFO  org.apache.flink.runtime.entrypoint.ClusterEntrypoint          [] -
    RESOURCE_PARAMS extraction logs:
    jvm_params: -Xmx469762048 -Xms469762048 -XX:MaxDirectMemorySize=134217728 -XX:MaxMetaspaceSize=268435456
    dynamic_configs: -D jobmanager.memory.off-heap.size=134217728b -D jobmanager.memory.jvm-overhead.min=201326592b -D jobmanager.memory.metaspace.size=268435456b -D jobmanager.memory.heap.size=469762048b -D jobmanager.memory.jvm-overhead.max=201326592b
    logs: WARN  [] - Error while trying to split key and value in configuration file /flink/conf/flink-conf.yaml:59: Line is not a key-value pair (missing key-value separator after ':'?)
    INFO  [] - Loading configuration property: table.exec.operator-name.max-length  10240

View operational logs

On the Logs page

  1. Log on to the Realtime Compute for Apache Flink console.

  2. Find the desired workspace and click Console in the Actions column.

  3. In the left-side navigation pane, choose O&M > Deployments.

  4. Click the name of the desired deployment.

  5. Click the Logs tab.

  6. On the Logs tab, select the running deployment from the drop-down list next to Deployment.

  7. View the logs for the JobManager and TaskManagers.

    • View JobManager logs

      On the Job Manager tab, click Logs.

    • View TaskManagers logs

      1. On the Running Task Managers tab, click a Path, ID.

      2. Click Logs.

        The page displays the operational log for the selected TaskManager. To filter the logs by level, select an option such as INFO from the drop-down list.

    In the Flink UI

  1. Log on to the Realtime Compute for Apache Flink console.

  2. Find the desired workspace and click Console in the Actions column.

  3. In the left-side navigation pane, choose O&M > Deployments.

  4. Click the name of the desired deployment.

  5. On the Status page, click Flink UI.

  6. In the left-side navigation pane, click Task Managers or Job Manager.

    • Click Task Managers, and then click a Path, ID to view that TaskManager's logs.

    • Click Job Manager and view its logs on the Logs tab.