You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/monitoring/jmx_monitor.md
+16-11Lines changed: 16 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,19 @@
1
1
# JMX MBEAN Monitoring
2
2
3
-
## JMX (Java Management Extensions)
3
+
## **JMX (Java Management Extensions)**
4
+
4
5
JMX, or Java Management Extensions, is a Java technology that provides tools for managing and monitoring applications, system objects, devices, and service-oriented networks. It allows developers to expose application information and enables external tools to access and interact with this information for monitoring and management purposes.
5
6
6
-
## JMX MBean for Debezium
7
+
## **JMX MBean for Debezium**
8
+
7
9
Debezium connectors expose metrics via the MBean name for the connector with MBean tag equals to the connector name. These metrics, which are specific to each connector instance, provide data about the behavior of the connector’s snapshot, streaming, and schema history processes.
8
10
9
-
## Enable JMX on a Connector with synchdb_add_jmx_conninfo() or disable with synchdb_del_jmx_conninfo()
10
-
The synchdb_add_jmx_conninfo() function adds JMX monitoring configuration to an existing connector. This enables runtime monitoring and diagnostics via tools like JConsole or Prometheus JMX Exporter.
11
+
## **Enable JMX on a Connector with synchdb_add_jmx_conninfo() or disable with synchdb_del_jmx_conninfo()**
12
+
13
+
The synchdb_add_jmx_conninfo() function adds JMX monitoring configuration to an existing connector. This enables runtime monitoring and diagnostics via tools like JConsole or Prometheus JMX Exporter.synchdb_del_jmx_conninfo() can be used to disable JMX.
11
14
12
15
**Function Signature**
16
+
13
17
synchdb_add_jmx_conninfo(
14
18
name text,
15
19
jmx_listenaddr text,
@@ -47,7 +51,8 @@ synchdb_del_jmx_conninfo(
47
51
|**`jmx_ssl_truststore`**|*(text)*<br>Path to the truststore (JKS) that holds trusted CA certificates. Used to verify client identities if mutual TLS is configured. |
48
52
|**`jmx_ssl_truststore_pass`**|*(text)*<br>Password for the truststore file. |
49
53
50
-
### Password and Access Files for JMX Authentication
54
+
### **Password and Access Files for JMX Authentication**
55
+
51
56
When enabling JMX authentication in your JVM configuration (i.e., setting jmx_auth = true), you must provide two files:
52
57
53
58
Password File – defines usernames and their passwords.
@@ -60,14 +65,14 @@ These files are used by the JVM to control who can connect and what they are all
60
65
61
66
This file stores valid JMX usernames and their corresponding passwords.
When a connector with JMX configuration is started, the JMX service will be running on the designated port number. We can use `jconsole` that comes with Java distribution to connect to JMX server. It is possible to connect locally via the JVM (connector worker) PID or via IP address and port number. If authentication is enabled, username and password are required as well. If no authentication is used, these can be left empty.
189
195
190
196

191
197
192
-
193
198
Once connected, we can view all the details about JVM's operating metrics such as CPU, memory, class utilization, threads...etc.
194
199
195
200

196
201

197
202

198
203
199
-
## Visualize Debezium JMX MBeans
204
+
## **Visualize Debezium JMX MBeans**
200
205
201
206
The last tab is MBeans, which contains the Debezium specific metrics for schema history, snapshot and streaming stages.
0 commit comments