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

Access logs for Websocket APIs #3419

Closed
rmsamitha opened this issue Dec 4, 2024 · 0 comments · Fixed by wso2/carbon-mediation#1743
Closed

Access logs for Websocket APIs #3419

rmsamitha opened this issue Dec 4, 2024 · 0 comments · Fixed by wso2/carbon-mediation#1743

Comments

@rmsamitha
Copy link
Member

rmsamitha commented Dec 4, 2024

Problem

Logs related to WebSocket API invocations should be able to be enabled in WSO2 API Manager. These logs should allow to monitor WebSocket API invocations and debug/troubleshoot issues that may arise.

Solution

Websocket access logs are implemented by overriding io.netty.handler.logging.LoggingHandler and adding it to the websocket pipeline.

These Access logs are printed only if the related configurations are added to log4j2.properties file and there can be slight performance impact when the access logs are enabled. So it is recommended not to enable Websocket access logs if there is no requirement, in production environments.

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

Successfully merging a pull request may close this issue.

2 participants