You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
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:
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
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
The text was updated successfully, but these errors were encountered: