-
-
Notifications
You must be signed in to change notification settings - Fork 214
Closed
Labels
area/connectKafka Connect, its connectorsKafka Connect, its connectorsscope/backendRelated to backend changesRelated to backend changesscope/frontendRelated to frontend changesRelated to frontend changesstatus/triage/completedAutomatic triage completedAutomatic triage completedtype/enhancementEn enhancement/improvement to an already existing featureEn enhancement/improvement to an already existing feature
Description
Issue submitter TODO list
- I've searched for an already existing issues here
- I'm running a supported version of the application which is listed here and the feature is not present there
Is your proposal related to a problem?
When a connector itself is FAILED (not just tasks), the UI currently does not show the connector-level trace. This makes troubleshooting harder because users only see task traces (if any), while some failures occur at the connector level (e.g., initialization, class loading, AdminClient creation).
Describe the feature you're interested in
- Make the FAILED badge on the Connector Details page clickable.
- On click, open a modal that displays the connector-level trace if present (status.trace).
Example payload (connector-level trace present):
{
"connect": "<cluster-name>",
"name": "<connector-name>",
"connectorClass": "<connector-class>",
"type": "<source/sink>",
"topics": [],
"status": {
"state": "FAILED",
"workerId": "<worker-id>",
"trace": "org.apache.kafka.common.KafkaException: Failed to create new KafkaAdminClient\n\tat org.apache.kafka.clients.admin.KafkaAdminClient.createInternal(...)\n...\nCaused by: org.apache.kafka.common.config.ConfigException: You must set either bootstrap.servers or bootstrap.controllers\n\tat org.apache.kafka.clients.admin.internals.AdminBootstrapAddresses.fromConfig(...)\n..."
},
"tasksCount": 0,
"failedTasksCount": 0
}
Describe alternatives you've considered
No response
Version you're running
Additional context
- UX keeps users on the same page, no navigation context loss.
- I am happy to contribute the implementation and open a PR linked to this issue.
Metadata
Metadata
Assignees
Labels
area/connectKafka Connect, its connectorsKafka Connect, its connectorsscope/backendRelated to backend changesRelated to backend changesscope/frontendRelated to frontend changesRelated to frontend changesstatus/triage/completedAutomatic triage completedAutomatic triage completedtype/enhancementEn enhancement/improvement to an already existing featureEn enhancement/improvement to an already existing feature