log.level parameter disappeared from the documentation README.md and seems to have been replaced by verbosity (that expects an integer as value). Is this really the case or is verbosity a new parameter?
log.level is still displayed in kafka_exporter --help
sh-4.4$ ./kafka_exporter --help
usage: kafka_exporter [<flags>]
Flags:
-h, --help Show context-sensitive help (also try --help-long and --help-man).
--web.listen-address=":9308"
Address to listen on for web interface and telemetry.
--web.telemetry-path="/metrics"
Path under which to expose metrics.
--topic.filter=".*" Regex that determines which topics to collect.
--group.filter=".*" Regex that determines which consumer groups to collect.
--log.enable-sarama Turn on Sarama logging.
--kafka.server=kafka:9092 ...
Address (host:port) of Kafka server.
--sasl.enabled Connect using SASL/PLAIN.
--sasl.handshake Only set this to false if using a non-Kafka SASL proxy.
--sasl.username="" SASL user name.
--sasl.password="" SASL user password.
--sasl.mechanism="" The SASL SCRAM SHA algorithm sha256 or sha512 or gssapi as mechanism
--sasl.service-name="" Service name when using kerberos Auth
--sasl.kerberos-config-path=""
Kerberos config path
--sasl.realm="" Kerberos realm
--sasl.kerberos-auth-type=""
Kerberos auth type. Either 'keytabAuth' or 'userAuth'
--sasl.keytab-path="" Kerberos keytab file path
--tls.enabled Connect to Kafka using TLS.
--tls.server-name="" Used to verify the hostname on the returned certificates unless tls.insecure-skip-tls-verify is given. The kafka server's name should be given.
--tls.ca-file="" The optional certificate authority file for Kafka TLS client authentication.
--tls.cert-file="" The optional certificate file for Kafka client authentication.
--tls.key-file="" The optional key file for Kafka client authentication.
--server.tls.enabled Enable TLS for web server.
--server.tls.mutual-auth-enabled
Enable TLS client mutual authentication.
--server.tls.ca-file="" The certificate authority file for the web server.
--server.tls.cert-file="" The certificate file for the web server.
--server.tls.key-file="" The key file for the web server.
--tls.insecure-skip-tls-verify
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.
--kafka.version="2.0.0" Kafka broker version
--use.consumelag.zookeeper
if you need to use a group from zookeeper
--zookeeper.server=localhost:2181 ...
Address (hosts) of zookeeper server.
--kafka.labels="" Kafka cluster name
--refresh.metadata="30s" Metadata refresh interval
--offset.show-all Whether show the offset/lag for all consumer group, otherwise, only show connected consumer groups
--concurrent.enable If true, all scrapes will trigger kafka operations otherwise, they will share results. WARN: This should be disabled on large clusters
--topic.workers=100 Number of topic workers
--verbosity=0 Verbosity log level
--log.level=info Only log messages with the given severity or above. One of: [debug, info, warn, error]
--log.format=logfmt Output format of log messages. One of: [logfmt, json]
--version Show application version.
log.level parameter disappeared from the documentation README.md and seems to have been replaced by verbosity (that expects an integer as value). Is this really the case or is verbosity a new parameter?
As a consequence the latest strimzi 0.26 doesn't work anymore (See https://github.com/strimzi/strimzi-kafka-operator/issues/5764)
log.level is still displayed in kafka_exporter --help