Este contenido no está disponible en el idioma seleccionado.
Chapter 52. EntityTopicOperatorSpec schema reference
Used in: EntityOperatorSpec
Full list of EntityTopicOperatorSpec schema properties
Configures the Topic Operator.
52.1. Logging Copiar enlaceEnlace copiado en el portapapeles!
The Topic Operator has a configurable logger:
-
rootLogger.level
The Topic Operator uses the Apache log4j2 logger implementation.
Use the logging property in the entityOperator.topicOperator field of the Kafka resource Kafka resource to configure loggers and logger levels.
You can set the log levels by specifying the logger and level directly (inline) or use a custom (external) ConfigMap. If a ConfigMap is used, you set logging.valueFrom.configMapKeyRef.name property to the name of the ConfigMap containing the external logging configuration. Inside the ConfigMap, the logging configuration is described using log4j2.properties. Both logging.valueFrom.configMapKeyRef.name and logging.valueFrom.configMapKeyRef.key properties are mandatory. A ConfigMap using the exact logging configuration specified is created with the custom resource when the Cluster Operator is running, then recreated after each reconciliation. If you do not specify a custom ConfigMap, default logging settings are used. If a specific logger value is not set, upper-level logger settings are inherited for that logger. For more information about log levels, see Apache logging services.
Here we see examples of inline and external logging. The inline logging specifies the root logger level. You can also set log levels for specific classes or loggers by adding them to the loggers property.
Inline logging
- 1
- Creates a logger for the
topicpackage. - 2
- Sets the logging level for the
topicpackage. - 3
- Creates a logger for the
TopicOperatorclass. - 4
- Sets the logging level for the
TopicOperatorclass. - 5
- Changes the logging level for the default
clientslogger. Theclientslogger is part of the logging configuration provided with Streams for Apache Kafka. By default, it is set toINFO.
When investigating an issue with the operator, it’s usually sufficient to change the rootLogger to DEBUG to get more detailed logs. However, keep in mind that setting the log level to DEBUG may result in a large amount of log output and may have performance implications.
External logging
Garbage collector (GC)
Garbage collector logging can also be enabled (or disabled) using the jvmOptions property.
52.2. EntityTopicOperatorSpec schema properties Copiar enlaceEnlace copiado en el portapapeles!
| Property | Property type | Description |
|---|---|---|
| watchedNamespace | string | The namespace the Topic Operator should watch. |
| image | string | The image to use for the Topic Operator. |
| reconciliationIntervalSeconds | integer |
The |
| reconciliationIntervalMs | integer | Interval between periodic reconciliations in milliseconds. |
| zookeeperSessionTimeoutSeconds | integer |
The |
| startupProbe | Pod startup checking. | |
| livenessProbe | Pod liveness checking. | |
| readinessProbe | Pod readiness checking. | |
| resources | CPU and memory resources to reserve. | |
| topicMetadataMaxAttempts | integer |
The |
| logging | Logging configuration. | |
| jvmOptions | JVM Options for pods. |