Log level of Camunda Connector Runtime

Camunda 8 Topics
1

Hi folks,

during the development of some custom connectors, we are using the connector runtime docker image (GitHub - camunda/connector-runtime-docker: Docker image for the Connector Runtime) which is in fact a connector runtime from spring-zeebe (spring-zeebe/connector-runtime at main · camunda-community-hub/spring-zeebe · GitHub)

I wonder why the output of the container is so noisy. I believe it runs in DEBUG mode. For some reasons I was not able to limit the output to at least INFO.

Another thing is: both Apache Client and GRPC lib are dumping full binary message content into the log (which is breaking the “convention” to dumb binary content on TRACE only).

This fact make the use of the Connector runtime very difficult to use.

Any plans how I can switch it off?

Cheers,

Simon

2

Hi @zambrovski - I admit, I not very versed in JVM configuration options, but maybe setting the log level via JAVA_OPTS is an option here?

docker run ... \
  -e JAVA_OPTS=-Dlogging.level.org.springframework=INFO

If that doesn’t work, I’d also be curious to know what else you’ve tried that didn’t work.

2 Likes
3

Thank you Nathan,

I already tried all that. My problem was that the connector shipped a wrong SLF4J configuration (multiple binders on the classpath), and then Spring just fallbacks to DEBUG and is not controllable anymore.

So indeed you answer is correct, my problem was a different one.

Thanks and cheers,

Simon

1 Like