Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log engine created as debug #305

Closed
npepinpe opened this issue Dec 23, 2024 · 0 comments · Fixed by #306
Closed

Log engine created as debug #305

npepinpe opened this issue Dec 23, 2024 · 0 comments · Fixed by #306
Assignees

Comments

@npepinpe
Copy link
Member

Describe the bug

Note

Not really a bug, but also not a feature 😄

Whenever the engine is opened, I get the following INFO level log:

17:14:52.049 [Broker-0] [StreamProcessor-1] [zb-actors-1] INFO  org.camunda.dmn.DmnEngine - DMN-Engine created. [value-mapper: CompositeValueMapper(List(io.camunda.zeebe.feel.impl.MessagePackValueMapper@70bd44db)), function-provider: org.camunda.feel.context.FunctionProvider$EmptyFunctionProvider$@7be06e40, audit-loggers: List(), configuration: Configuration(false,false,false)]

In fact, this occurs multiple time if I use multiple engines. In Zeebe, for example, on any given transition, I get the following log sequence:

17:14:52.047 [Broker-0] [StreamProcessor-1] [zb-actors-1] INFO  org.camunda.dmn.DmnEngine - DMN-Engine created. [value-mapper: CompositeValueMapper(List(io.camunda.zeebe.feel.impl.MessagePackValueMapper@61d1b616)), function-provider: org.camunda.feel.context.FunctionProvider$EmptyFunctionProvider$@7be06e40, audit-loggers: List(), configuration: Configuration(false,false,false)]
17:14:52.047 [Broker-0] [StreamProcessor-1] [zb-actors-1] INFO  org.camunda.dmn.DmnEngine - DMN-Engine created. [value-mapper: CompositeValueMapper(List(io.camunda.zeebe.feel.impl.MessagePackValueMapper@1082dfa6)), function-provider: org.camunda.feel.context.FunctionProvider$EmptyFunctionProvider$@7be06e40, audit-loggers: List(), configuration: Configuration(false,false,false)]
17:14:52.048 [Broker-0] [StreamProcessor-1] [zb-actors-1] INFO  org.camunda.dmn.DmnEngine - DMN-Engine created. [value-mapper: CompositeValueMapper(List(io.camunda.zeebe.feel.impl.MessagePackValueMapper@411ce270)), function-provider: org.camunda.feel.context.FunctionProvider$EmptyFunctionProvider$@7be06e40, audit-loggers: List(), configuration: Configuration(false,false,false)]
17:14:52.048 [Broker-0] [StreamProcessor-1] [zb-actors-1] INFO  org.camunda.feel.FeelEngine - Engine created. [value-mapper: CompositeValueMapper(List(org.camunda.dmn.NoUnpackValueMapper@7435353a)), function-provider: org.camunda.feel.context.FunctionProvider$EmptyFunctionProvider$@7be06e40, clock: SystemClock, configuration: {externalFunctionsEnabled: false}]
17:14:52.049 [Broker-0] [StreamProcessor-1] [zb-actors-1] INFO  org.camunda.dmn.DmnEngine - DMN-Engine created. [value-mapper: CompositeValueMapper(List(io.camunda.zeebe.feel.impl.MessagePackValueMapper@70bd44db)), function-provider: org.camunda.feel.context.FunctionProvider$EmptyFunctionProvider$@7be06e40, audit-loggers: List(), configuration: Configuration(false,false,false)]

Considering most of the information provider is not understandable or actionable for the average user, but is there primarily for debugging purposes, I would propose to lower the log level of this statement to DEBUG.

I'll open a similar issue in the FEEL engine :)

To Reproduce

  • Start Zeebe :)

Expected behavior

INFO level logs are information useful for a user/operator - debugging information for the developers should be at the DEBUG level. This helps avoid the noise/ratio signal when debugging issues in cloud, which can help speed up diagnoses (and thus reduce the MTTR).

Environment

  • DMN engine version: latest
  • Integration:
    • Camunda Cloud/Zeebe: 8.7.0-SNAPSHOT
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant