Expand my Community achievements bar.

Join us for the Adobe Journey Optimizer Community Q&A Coffee Break on 28th February at 8 am PT with Ariel Sultan, Daniel Wright, Josee Haeley and Rohit Basuri.

Debug mode - Filter type of logs printed to the console

Avatar

Community Advisor

5/21/21

Description -

Currently when debugging is enabled all events are logged to the console which makes it very hard to see what is going on.   It would be great if there was a way to select which types of events were written to the console.  Often I just want to see the custom logs generated where I've used the _satellite.logger function in custom code. 

Why is this feature important to you -

It would make debugging easier.   At the moment I find myself often resorting to using console.log because it is easier to see what is happening but this has it's own drawbacks


How would you like the feature to work -

Maybe the _satellite.setDebug() function could be altered to take an additional optional parameter listing the categories of log that you want to write to the console?

Current Behaviour -

Everything gets written to the console

2 Comments

Avatar

Community Advisor

5/24/21

@Stewart_Schilling It's a fair point, and one I considered

 

But I don't think I can get the configuration I wanted this way.  I want everything to appear in the console that would normally appear, plus just the custom logs I've set in code using the _satellite.logger function (i.e. none of the other stuff that launch outputs by default when you enable debugging)  - Launch seems to split out so much stuff when we have debugging is enabled that it just swamps the console.