-
Notifications
You must be signed in to change notification settings - Fork 10
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
Unclear logging / debugging instructions #397
Comments
8 tasks
petar-slavov
pushed a commit
to petar-slavov/camunda-8-js-sdk
that referenced
this issue
Mar 14, 2025
## [8.6.32](camunda/camunda-8-js-sdk@v8.6.31...v8.6.32) (2025-03-06) ### Bug Fixes * add tests and documentation for logging ([3522faf](camunda@3522faf)), closes [camunda#397](camunda#397) * **operate:** allow paging for getVariablesforProcess ([b94532d](camunda@b94532d)), closes [camunda#387](camunda#387)
petar-slavov
pushed a commit
to petar-slavov/camunda-8-js-sdk
that referenced
this issue
Mar 14, 2025
## [8.6.32](camunda/camunda-8-js-sdk@v8.6.31...v8.6.32) (2025-03-06) ### Bug Fixes * add tests and documentation for logging ([3522faf](camunda@3522faf)), closes [camunda#397](camunda#397) * **operate:** allow paging for getVariablesforProcess ([b94532d](camunda@b94532d)), closes [camunda#387](camunda#387)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem
I want to understand what tools I have to debug log what happens in the SDK. Given that there is both an undocumented
CAMUNDA_LOG_LEVEL
(ref) and documented debugging instructions available, I'm a little lost what is the consistent approach how to do debug logging.Relevant for Desktop Modeler, as an API client. We want to put the SDK into a "DEBUG" mode, where needed, to trace errors.
Describe the solution you see
I want to learn, from a single place, how logging works with this SDK, how I can influence it to change log levels, etc.
I assume that logging is a concern that is handled in a unified way, across different components exposed by this SDK.
The text was updated successfully, but these errors were encountered: