Debezium UI
This feature is currently in incubating state, i.e. exact semantics and behaviours etc. may change in future revisions, based on the feedback we receive. Please let us know about your feature requests or if you encounter any problems while using the Debezium UI. |
The Debezium UI allows users to set up and operate connectors more easily. For instance, a list of all connectors can be viewed along with their status, etc. The Create Connector wizard allows the user to configure connectors, guiding and validating the property entries along the way.
Design Considerations
The UI is implemented as aQuarkus-based web application. The backend is configured with the URL(s) of one or more Kafka Connect clusters and provides a REST interface for the frontend. The frontend user interface usesReactJSas the primary technology, utilizingPatternflyreact components and design patterns.
Installation and Configuration
Configure the Debezium UI
The following table shows the environment variables for theDebezium UI container imageand the related parameter names insideapplication.properties
when running the Java application without the container.
Item | Environment variable | Parameter name in application.properties | Default value | Description |
---|---|---|---|---|
1 |
|
default |
Specifies how the Debezium UI is deployed. |
|
2 |
|
A comma-separated list to one or more URLs of Kafka Connect REST interfaces to specify the Kafka Connect clusters that should be managed by the Debezium UI. |
Debezium UI container image
The Debezium UIcontainer imageis available for running the UI. To start the UI and connect to an existing Kafka Connect instance via Docker (where KAFKA_CONNECT_URIS supplies the comma-separated list of available URI(s)):
$ docker run -it --rm --name debezium-ui -p 8080:8080 -e KAFKA_CONNECT_URIS=http://connect:8083 debezium/debezium-ui:{debezium-version}
The UI connects to Kafka Connect via REST, so you need to make sure that the latter is reachable, e.g. by running both components on the same Docker network.
Currently, the UI connects to un-authenticated Kafka Connect instances. Also, there’s no authorization or authentication implemented in the UI itself yet. Until that is the case, you should secure the components e.g. with your own proxy for authorization, if needed. |
Self-contained example
A self-contained exampleui-demois available, which is included underdebezium-exampleson Github. The ui-demo includes a docker-compose file which brings up several sources with data as well as the UI. Please refer to theREADME filefor more details on running the Debezium ui-demo.
UI Operation
UI Connector List
The main page of the UI displays all the registered connectors. Some of the highlights of the main page are as follows:
Kafka connect clustercan be selected via the dropdown in the header.
Connector table shows each connector with its type (MongoDB, MySQL, Oracle, PostgreSQL, or SQL Server), connector status, and connector tasks.
A connector row can be expanded to show more details, as shown below with the 'testPostgres' connector. Metrics are shown in the expansion area (Note:this feature is still under development and not functional yet). Connector tasks are shown, with ability toRestartthe task if desired.
The overflow menu at the right of each connector row provides actions which allow the user toPause, Resume, Restart or Deletethe connector.
UI Create Connector Wizard
The user can create a connector by clicking on theCreate a connectorbutton on the main page. The first two steps of the wizard are required, but the remaining steps are optional. Each step will validate the user entries and provide feedback if there are problems. After completing steps 1 and 2 successfully, the user can proceed to the final page to review and create the connector.
Create Connector - Connector type (required)
Choose the type of connector in Step 1. Currently, you can specify the following connector types:MongoDB,MySQL,Oracle,PostgreSQLandSQL Server.
Create Connector - Properties (required)
In Step 2, you enter the basic connection properties for the selected connector and confirm that the properties validate successfully. You can also specify advanced connection properties in a separate section of this step. After successful validation, you can proceed to the next steps (Additional properties), or clickReview and finishin the wizard footer to bypass the additional properties and proceed directly to review.
Create Connector - Additional properties (optional)
The Additional properties are optional and can be summarized as follows:
Filter definition- entry ofregular expressions为包含/排除o定义过滤器f the items that will be included for CDC. The included items are displayed as the filters are entered and applied.
Transformations——允许一次性修改个人messages. Single message transformations (SMTs) modify records before they are sent to Apache Kafka by applying them to the Debezium connectors. For more information about single message transformations, seeTransformations.
Topic creation- Define default properties and groups for enabling automatic topic creation.
Data options-SnapshotandMappingproperties (optional). The defaults can be viewed and changed if desired.
Runtime options-EngineandHeartbeatproperties (optional). The defaults can be viewed and changed if desired.
Custom properties- Enable pass-through of additional properties that are not specified in the previous sections, such as
database.
anddatabase.history.
options. You can enter any valid property name and value.
Create Connector - Review
TheReviewstep provides a summary of the configuration that will be used to create the connector. If you are satisfied with your selections, clickFinishto create the connector. To adjust any properties, navigate back to the earlier steps. You can also copy or download the JSON configuration payload for the connector.