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

Server logs in production mode are lacking information as virtually everything is at /CodeCheckerService #3047

Closed
whisperity opened this issue Nov 24, 2020 · 0 comments · Fixed by #3105

Comments

@whisperity
Copy link
Contributor

The current log output of the server outside verbose mode is not terribly useful as virtually everything that is related to CodeChecker is accessed through /CodeCheckerService.

For example, during normal day-to-day usage, the following logs are generated:

[INFO 2020-11-24 11:12] - 127.0.0.1:39506 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39512 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39514 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39518 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39522 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39526 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService

I have looked into the server implementation code and I agree it's not the easiest to properly refactor, however, an output similar in nature to

[INFO 2020-11-24 11:12] - 127.0.0.1:39506 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService@getReport
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