Event tracking in Confluent Manager for Apache Flink
An event in Confluent Manager for Apache Flink (CMF) is a timestamped record of a state change in a Apache Flink® application or cluster. Events enable you to track the lifecycle and status of your Flink applications without accessing the Kubernetes cluster or Flink Web Interface.
Flink applications are deployed in Confluent Platform with CMF, which is a central management component of Confluent Platform for Apache Flink.
Events tell you:
The time an event occurred.
The Flink application instance that the event is associated with.
What changes to the Flink application resource occurred.
The status of the Flink cluster.
Events help you to understand the status of your Flink clusters, without examining the Kubernetes cluster or using the Flink Web Interface.
CMF stores a maximum of 100 events per Flink application (the 100 most recent events). You can configure this limit with the cmf.application-events.max-events-per-application property. When you delete a Flink application, all associated events are also deleted.
Note that if you are using RBAC, you must have View permissions on the Flink application to view its events.
Event types tracked by CMF
You can use CMF to track the following events.
CMF Status:
Flink application resource creation.
Flink application resource updated.
Cluster status: Tracked from status.lifecycleState of the FlinkApplication:
CREATED: The resource was created in Kubernetes but not yet handled by the operator.
SUSPENDED: The (job) resource has been suspended.
UPGRADING: The resource is suspended before upgrading to a new spec.
DEPLOYED: The resource is deployed/submitted to Kubernetes, but it’s not yet considered to be stable and might be rolled back in the future.
STABLE: The resource deployment is considered to be stable and won’t be rolled back. This means the Flink cluster is healthy.
ROLLING_BACK: The resource is being rolled back to the last stable spec.
ROLLED_BACK: The resource is deployed with the last stable spec.
FAILED: The job terminally failed.
Flink Job status:
Any change to the Flink job status. Tracked from the
FlinkApplication.status.jobStatus.state.
Flink Exceptions: Any exception causing a restart of a Flink job will be tracked as an event.
View events with Control Center
You can view events in the Confluent Control Center UI. The Events page displays a list of events associated with your Flink applications. The following image shows Events in Confluent Control Center:

Get events with the REST API
You can also use the Events REST API to determine the status of your Flink applications and clusters. For example, you can use the following command to get a list of events for a specific Flink application:
- GET /cmf/api/v1/environments/dev-east/applications/fraud-detection/events
An example response might look like the following:
{
"pageable": null,
"metadata": {
"size": 3
},
"items": [
{
"apiVersion": "cmf.confluent.io/v1alpha1",
"kind": "FlinkApplicationEvent",
"metadata": {
"name": "77d37980-4798-437b-8850-1ecd6b612ade",
"uid": "77d37980-4798-437b-8850-1ecd6b612ade",
"creationTimestamp": "2025-06-18T11:16:38.061Z",
"flinkApplicationInstance": "9f118068-3855-4442-919f-2007338a88b2",
"labels": null,
"annotations": null
},
"status": {
"message": "Flink job status changed to RECONCILING",
"type": "JOB_STATUS",
"data": {
"newStatus": "RECONCILING"
}
}
},
{
"apiVersion": "cmf.confluent.io/v1alpha1",
"kind": "FlinkApplicationEvent",
"metadata": {
"name": "e66b2e16-b833-4350-8e18-8f51dd148f28",
"uid": "e66b2e16-b833-4350-8e18-8f51dd148f28",
"creationTimestamp": "2025-06-18T11:16:36.434Z",
"flinkApplicationInstance": null,
"labels": null,
"annotations": null
},
"status": {
"message": "Flink cluster status changed to CREATED",
"type": "CLUSTER_STATUS",
"data": {
"newStatus": "CREATED"
}
}
},
{
"apiVersion": "cmf.confluent.io/v1alpha1",
"kind": "FlinkApplicationEvent",
"metadata": {
"name": "27102d2e-18f1-4135-a49e-62bd423c5023",
"uid": "27102d2e-18f1-4135-a49e-62bd423c5023",
"creationTimestamp": "2025-06-18T11:16:35.435Z",
"flinkApplicationInstance": null,
"labels": null,
"annotations": null
},
"status": {
"message": "FlinkApplication created",
"type": "CMF_STATUS",
"data": null
}
}
]
}