Skip to content
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

Feature Request: use setEchoLevel and setLogLevel at the top level to change CCP logs #864

Open
alexgurr opened this issue Apr 18, 2024 · 2 comments

Comments

@alexgurr
Copy link

alexgurr commented Apr 18, 2024

This has been an issue for years (#503). We are unable to control the logging at the lowest level, meaning while developing we continue to get hundreds of logs in the console.

It would be really helpful if we could set the log level at the top level and actually have this propagate down to the lowest CCP/code level.

@maddoxd
Copy link

maddoxd commented Apr 18, 2024

I don't want to steal the thread, but further to this, we notice that the only 'component' that ever gets logged is 'CCP' and a few 'chat'. i.e. not 'Softphone'. Softphone contains a lot of useful info that displays in the console that we would like to capture when the agent downloads the logs, but today this info is completely missing - things like ICE timeout, Mic not allowed etc etc

The documentation seems to suggest these should be logged - https://github.com/amazon-connect/amazon-connect-streams/blob/master/Documentation.md#ccp-error-logging

@hngan
Copy link
Contributor

hngan commented Apr 25, 2024

Yea, I agree that CCP's console logs can be quite excessive, and for the most part we ignore them too... Will ask internally if we have any issues removing them or if it'll be easy to add an option to disable the console logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants