Question

336 views13th February 2025logging

3

Joshua Lee [SLC] [DevOps Advocate]583 13th February 2025 1 Comment

When logging in a QAction, when should we use the different log levels i.e. NoLogging, Level1, Level2, Level3, Level4, Development, LogEverything?

For the development it is quite straight forward but what about the levels?

Samuel Duarte [SLC] [DevOps Member] Answered question 13th February 2025

Joshua Lee [SLC] [DevOps Advocate] commented 13th February 2025

To add some usecase context, I have a logging that is useful to have but is triggering excessively and flooding the element log. I would like to have it for troubleshooting but it should be hidden by default. I was considering using log levels for this.

1 Answer

You are viewing 1 out of 1 answers, click here to view all answers.

To add some usecase context, I have a logging that is useful to have but is triggering excessively and flooding the element log. I would like to have it for troubleshooting but it should be hidden by default. I was considering using log levels for this.

score 0 · Answer 1 · 2025-02-13T17:33:37+00:00

Hi Joshua,

For your case, the best solution to have logging ready for troubleshooting is to add a Debug Mode parameter to the protocol. Based on this parameter, extra logging can be enabled or disabled as needed.

You can find more information on how to implement this here How to use the element log in connector integrations | DataMiner Docs

When to use different logging levels?

1 Answer