The Flink console provides a job details page where you can view basic job information, configuration details, monitoring metrics, snapshots, logs, and alert configurations.
Basic Information: displays basic job information, such as the name, status, type, resource pool, priority, and engine version, and provides a quick link to the Web UI.
Network Information: displays the subnet and security group information for the resource pool where the current job is running.
Historical Instances: lists all historical job instances, allowing you to view the configuration details, monitoring metric curves, and logs for each instance.
Displays the job's current configuration details, including the following information:
SQL Configuration: displays the job's SQL statement for SQL jobs only.
Job Configuration: displays the JAR URI, main class, and the main function's args[] parameters for JAR jobs. Displays information such as the code file and Entrypoint for Ray jobs. Displays information such as the Python File URI and Entry Point Main Arguments for Python jobs.
Job Resource Configuration: displays the job's Flink parameter configuration.
Checkpoint Configuration: displays the checkpoint configuration of the task.
Task Restart Strategy Configuration: displays the restart strategy and rules for the task.
Task Failure Retry Configuration: displays the rules for retrying failed tasks, including the maximum number of retries and the retry interval.
Custom Parameters: displays the custom parameters configured for the task.
Auto-tuning:
Dependency Files: displays the dependency files selected for the task.
Logs key events throughout the entire task runtime and displays critical information. Helps operations personnel troubleshoot, analyze, and identify the cause of errors.
Provides direct access to the instance's configuration details.
Flink is integrated with Cloud Monitor to provide monitoring and alerting capabilities for Flink jobs.
The Data Curves tab on the Flink job details page displays the monitoring metric data curves for the current job. You can view key metrics across different dimensions as needed, including Overview, Network & IO, JVM, Schedule Info, Watermark, Checkpoint View, Checkpoint Timer, Checkpoint Operator Performance, Resource, and Kafka. Analyzing these metrics helps you quickly identify any job abnormalities.
tip
The Data Curve page provides a Chart Linkage feature.
When this feature is enabled, hovering over any monitoring chart displays the metric details for all other charts at the same time.
The Flink platform now supports auto-tuning for jobs. Once enabled, the system will auto-scale the job based on the configured time rules.
In the left navigation pane, go to Job O&M > Job Management.
On the Flink Jobs tab, filter for and click the target job name.
On the Auto-tuning tab, click New Rule, configure the tuning parameters, and click OK.
If auto-tuning is enabled and you need to modify the tuning rules, click Edit Rules.
After a rule is created, click the enable button to activate the corresponding tuning task. The task will be scheduled once the rule's status is Enabled.
Adjust priority: Drag and drop priorities to change the scheduling order of tuning rules. If there is a time overlap, the rule with the higher priority is executed first.
The parameters are described as follows:
Configuration
Description
Rule Type
The type of rule. Scheduled rules are currently supported.
Rule Name
Set the rule name.
Scheduling period
The scheduling period for the tuning rule. Supported frequencies include one-time, daily, weekly, and monthly.
Select time
You can set a start time and an end time:
Start time: At the start time, the Flink task will restart, and its resources will be adjusted to the target resource usage.
End time: When the task reaches its end time, the Flink task will automatically revert to its pre-tuning resource parameters.
Displays task snapshots of Flink tasks created manually or by the system within the last 5 days.
Snapshots are primarily used to restore tasks after a system failure, preventing data loss. For details on how to create and use snapshots, see 作业快照.
On the Logs tab of the task details page, you can view the log details for the current task. The system retains logs for 7 days. You can view the task's historical logs during the log retention period.
Task type
Description
Flink
Displays logs for the current task. You can switch between JobManager, TaskManager, and Client to view the corresponding logs.
View logs from historical instances, JobManager, TaskManager, Client, and Pod.
Specify a start and end time to view task logs within that period.
Set the log output type to log, err, or out to view only logs of that specific type.
tip
Log files typically contain general information about the Flink system's operation, such as task start and stop times, status updates, warnings, and error messages. This log content provides important information for diagnosing and debugging issues. You can use the env.log.level parameter in Flink to set the log output level. Once set, only logs of the specified level and higher will be displayed in the task log. For setup instructions, see Custom Parameters.
Out files typically contain the output data generated during a Flink task's execution. This data can be the final or intermediate result of a Flink application. If the Flink application is a stream processing application, the out file may be continuously updated and grow as new data arrives.
The err file typically contains error messages and exceptions that occur during Flink task execution. This information is crucial for diagnosing and debugging issues, helping you quickly identify and resolve them.
Set the log level to view only task logs of a specific level.
Set a keyword to find task logs containing that keyword.
View logs in full-screen mode.
Download log files to your local device in the format <Instance Name>-<Log Type>-<Pod Name>-log.txt.
Jump to the top or bottom of the logs using one-click shortcut buttons.
Ray
View current Ray task logs and switch between log types to see the corresponding logs.
View logs for a specific time range.
Specify log levels and keywords to view task logs with precision.
View logs in full-screen mode.
Download log files to your local device.
Use one-click shortcuts to navigate to the top or bottom of task logs.
Flink integrates with Cloud Monitor to provide monitoring and alerting for Flink tasks.
On the Alert Configuration tab of the Flink task details page, click Go to Cloud Monitor to Configure Alert Rules to create alert rules and notification methods for the current task. When a monitored metric reaches the alert threshold, the system triggers an alert event and sends a message to the alert contacts. This helps you promptly detect and handle task exceptions.
To learn how to create an alert policy, see 创建告警策略.
Note: The Intelligent Diagnosis feature is currently an invitation-only feature. To enable it, Technical Supportsubmit a ticket.
Flink Intelligent Diagnosis collects real-time job metrics, such as latency, throughput, backpressure, CPU/memory usage, GC, Checkpoint status, operator watermarks, and data skew. It combines a rule engine with AI large model analysis to automatically identify anomalies, bottlenecks, and potential risks in streaming jobs, and then generates actionable repair suggestions or automated actions.
On the Intelligent Diagnosis tab in Task Details, select Intelligent Diagnosis to run an automatic diagnosis. The main supported features are:
Restart Diagnosis: Analyzes the causes of restarts and suggests avoidance methods based on task restart events and related logs.
Data Processing Analysis: Provides graphical DAGs, critical paths, hotspot metrics, and anomaly trends to help business and data teams quickly understand issues.
Task Configuration Analysis: Analyzes a task's resource usage based on its configuration and provides optimization suggestions.
Resource Usage Analysis: Analyzes core resource usage, such as CPU and memory, for the resource pool, JobManager, and TaskManagers, and provides optimization suggestions.
AI Diagnosis: Provides analysis capabilities enhanced by large models. It performs a comprehensive diagnosis of a task's end-to-end information and offers risk root cause localization, diagnostic reports, and repair solutions. Users can also use interactive Q&A for a more in-depth technical analysis of complex path issues, hidden bottlenecks, and potential risks.
In the AI Diagnosis feature, click the Diagnose Now button to automatically run a diagnosis with the large model. AI Diagnosis performs a comprehensive diagnosis of your Flink job by combining real-time metrics, logs, and other information. It also generates a diagnostic report with optimization suggestions.
You can further communicate with the large model in the dialog box to get more information about the job and receive a more in-depth diagnosis.