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

How to control log level, how to redirect logs to my own logger? #479

Closed
kuvaldini opened this issue Apr 19, 2021 · 2 comments · Fixed by #490
Closed

How to control log level, how to redirect logs to my own logger? #479

kuvaldini opened this issue Apr 19, 2021 · 2 comments · Fixed by #490

Comments

@kuvaldini
Copy link
Contributor

No description provided.

@gjasny
Copy link
Collaborator

gjasny commented Apr 19, 2021

Hello,

which output are you referring to? My suspicion is that it's either libcurl or civetweb.

Thanks,
Gregor

@kuvaldini
Copy link
Contributor Author

It is civetweb.
I found that

  1. civetweb must be built as RELEASE to suppress debug logs. They are controlled via #define DEBUG
  2. civetweb has mg_callbacks or CivetCallbacks (in C++) to control log_message() and log_access() functions

So. What I do to suppress logs a) build civetweb RELEASE and b) see PR

kuvaldini added a commit to kuvaldini/prometheus-cpp that referenced this issue Apr 20, 2021
Signed-off-by: kuvaldini <ivan@kuvaldini.pro>
kuvaldini added a commit to kuvaldini/prometheus-cpp that referenced this issue Apr 20, 2021
Signed-off-by: kuvaldini <ivan@kuvaldini.pro>
@jupp0r jupp0r closed this as completed in 8416888 May 1, 2021
gjasny added a commit that referenced this issue May 9, 2021
gjasny added a commit that referenced this issue May 9, 2021
gjasny added a commit that referenced this issue May 9, 2021
gjasny added a commit that referenced this issue May 9, 2021
gjasny added a commit that referenced this issue May 9, 2021
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

Successfully merging a pull request may close this issue.

2 participants