Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Implement log levels #116

Closed
benbullnz opened this issue Nov 8, 2020 · 4 comments
Closed

Implement log levels #116

benbullnz opened this issue Nov 8, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@benbullnz
Copy link

benbullnz commented Nov 8, 2020 •
edited
Loading

Which version are you using?

v0.12

Enhancement request

Would it be possible to add an option to the config to allow printing of source SDP's into stdout or log file?
This would help with fault finding and confirming that the server and clients are being presented with the expected SDP from encoders.

Thanks.
@benbullnz benbullnz changed the title Add option to print receiving stream SDP in stdout or log file Add option to print source SDP in stdout or log file Nov 8, 2020
@aler9
Copy link
Member

aler9 commented Nov 8, 2020

Hello, the most correct way to do this consists in implementing log levels (debug, info, warn, error) and print SDPs and responses if the log level is "debug".

@aler9 aler9 added the enhancement New feature or request label Nov 8, 2020
@aler9 aler9 changed the title Add option to print source SDP in stdout or log file Implement log levels Nov 26, 2020
aler9 added a commit that referenced this issue Dec 8, 2020
@aler9
implement log levels; print requests and responses when log level is …
74b592b 
…"debug" (#116)
@aler9
Copy link
Member

aler9 commented Dec 8, 2020

log levels have been implemented; now SDPs appear into the log when the "logLevel" option is set to "debug".

@aler9
Copy link
Member

aler9 commented Dec 15, 2020

added to v0.13.0

@aler9 aler9 closed this as completed Dec 15, 2020
@github-actions
Copy link
Contributor

github-actions bot commented Jan 1, 2023

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 1, 2023
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@benbullnz @aler9