Monitoring

Logging

The connectors make use of SLF4J for logging integration. The logger uses the logger name org.init.ohja.kafka.connect.odata.busevent.source and can be configured e.g., in the log4j configuration properties in the Confluent Platform.

The connector provides additional log location information ohja.location using MDC (mapped diagnostic context). The log location contains the name of the nearest enclosing definition of val, class, trait, object or package and the line number.

Example Log4j 1.x appender:

log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=[%d] %p %X{connector.context}%m %X{ohja.location}%n

JMX Metrics

The OData Business Events Source Connector supports all the connector and task metrics provided by Kafka Connect through Java Management Extensions (JMX). In addition, the OData Business Events Source Connector provides extra JMX metrics for accessing state managed by the connector.

MBean: org.init.ohja.kafka.connect:type=busevent-source-task-metrics,connector=([-.w]+),task=([d]+)

Metric	Explanation
retries	Count of retries performed in the connector task that is in retrying state.
${configGroup}-object-type	Name of the business object type for Business Event configured in the configuration group.
${configGroup}-object-task-code	Task code of the business object type for Business Event configured in the configuration group.
${configGroup}-latest-event	GUID and timestamp of latest extracted Business Event configured in the configuration group.