Replies: 2 comments
-
Hi, As regards to logging level, if you want to increase log level of runtime containers, you can do it by customizing k8s deployments via k8sDeploymentConfig and set NU_LOG_LEVEL environment variable to DEBUG (default is INFO). I assume that you are using docker image in version 1.2 (in next version this environment variable will be renamed to NUSSKNACKER_LOG_LEVEL). After this change, you have to restart designer and redeploy scenario. We have plans to make it easier by exposing logback configuration in configmap. Also have you checked logs of all runtime containers (in designer container you rather won't see anything interesting). |
Beta Was this translation helpful? Give feedback.
-
Hi @an0r0c |
Beta Was this translation helpful? Give feedback.
-
Hi!
Is there a trouble shooting guide for nussknacker light?
So in my example: I see in the consumer groups that messages get consumed by the deployed scenario. But somehow they get lost somewhere and do not land in the target topic.
I checked the logs of the deployed scenario (pods that got deployed fr that scenario) as well as the metrics. But no clue why those messages are "lost" somewhere. I assume it is some wrong SpEL but no error message or exception anywhere.
Is there any guideline or docu which would help me to dig into that? (like where can/should I increase the log levels ....)
Beta Was this translation helpful? Give feedback.
All reactions