-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
2.3.3.Final
-
None
-
False
-
-
False
Bug report
I tried to create a generic pattern to capture the JMX metrics inside the Debezium Server to send to the Datadog separate between the context (snapshot and streaming).
The same Debezium Server connects in three database types: MongoDB, MySQL and SQL server. But when I tried to use the generic bean_regex to try to capture the metrics, only Mongodb and MySQL captured the metrics separating between the context, the sql server not.
SQL Server bean_regex can't provide to me the metrics if I set the context, If I omit the same, works (but we need to separate for context).
"domain_regex":"debezium.*", "bean_regex": "debezium.*:type=connector-metrics,context=snapshot,server=.*",
What Debezium connector do you use and what version?
Debezium Server 2.3.3.Final
What is the connector configuration?
# pub/sub config debezium.sink.type=pubsub debezium.sink.pubsub.project.id= debezium.sink.pubsub.ordering.enabled=true debezium.sink.pubsub.lowercase.topic.enabled=true # offset storage config debezium.source.offset.storage=org.questrade.storage.gcs.CloudStorageOffsetBackingStore debezium.source.offset.flush.interval.ms=0 debezium.source.offset.storage.gcs.bucket=${GCS_BUCKET_NAME} debezium.source.offset.storage.gcs.object=${GCS_OFFSET_OBJECT} # schema history storage config debezium.source.schema.history.internal=org.questrade.storage.gcs.CloudStorageSchemaHistory debezium.source.schema.history.internal.gcs.bucket=${GCS_BUCKET_NAME} debezium.source.schema.history.internal.gcs.object=${GCS_HISTORY_OBJECT} # transforms config debezium.transforms=addSuffix debezium.transforms.addSuffix.type=org.apache.kafka.connect.transforms.RegexRouter debezium.transforms.addSuffix.regex=(.*) debezium.transforms.addSuffix.replacement=$1.${TOPIC_SUFFIX} # controls whether a delete event is followed by a tombstone event. debezium.source.tombstones.on.delete=${DEBEZIUM_TOMBSTONES_ON_DELETE} # domain config debezium.source.topic.prefix=${TOPIC_PREFIX} debezium.source.snapshot.mode=initial # quarkus config quarkus.http.port=${QUARKUS_HTTP_PORT} quarkus.log.console.json=${QUARKUS_LOG_CONSOLE_JSON} quarkus.log.level=${QUARKUS_LOG_LEVEL} # sqlserver config debezium.source.connector.class=io.debezium.connector.sqlserver.SqlServerConnector debezium.source.database.encrypt=${DEBEZIUM_DATABASE_ENCRYPT} debezium.source.database.trustServerCertificate=${DEBEZIUM_DATABASE_TRUST_SERVER_CERTIFICATE} debezium.source.database.hostname=${DEBEZIUM_DATABASE_HOSTNAME} debezium.source.database.port=${DEBEZIUM_DATABASE_PORT} debezium.source.database.user=${DEBEZIUM_DB_USERNAME} debezium.source.database.password=${DEBEZIUM_DB_PASSWORD} debezium.source.database.names=${DEBEZIUM_DATABASE_NAME} debezium.source.table.include.list=${DEBEZIUM_TABLE_INCLUDE_LIST} debezium.source.column.include.list=${DEBEZIUM_COLUMN_INCLUDE_LIST} debezium.source.include.schema.changes=${DEBEZIUM_INCLUDE_SCHEMA_CHANGES}
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
Microsoft SQL Server 2016
What behaviour do you expect?
When I tried to use the bean_regex:
debezium.sql_server:type=connector-metrics,context=snapshot,server=.*
and/or
debezium.*:type=connector-metrics,context=snapshot,server=.*
The same should be returned the all metrics with the context snapshot between the databases or specific database,, if I try to use the SQL server case, not work.
What behaviour do you see?
Returns all metrics from SQL server separete for the context (snapshot and streaming). Just working if I dont use the context value
