GMC: enhance log

[KfreeZ]

Description

Use standard log to replace the fmt.Printf functions
use curl -X GET "http://localhost:8008/loglevel?level=debug" and curl -X GET "http://localhost:8008/loglevel?level=info" to change the debug level

root@cis-gms-worker-3:~/zkf/repo/kfreez/GenAIInfra/microservices-connector# curl -X PUT "http://localhost:8008/loglevel" -d '{"lloglevel":"debugh"}' -H "Content-Type: application/json"
log_level field is required

root@cis-gms-worker-3:~/zkf/repo/kfreez/GenAIInfra/microservices-connector# curl -X PUT "http://localhost:8008/loglevel" -d '{"loglevel":"debugh"}' -H "Content-Type: application/json"
log_level field is required

root@cis-gms-worker-3:~/zkf/repo/kfreez/GenAIInfra/microservices-connector# curl -X PUT "http://localhost:8008/loglevel" -d '{"log_level":"debugh"}' -H "Content-Type: application/json"
invalid log level: unrecognized level: "debugh"

root@cis-gms-worker-3:~/zkf/repo/kfreez/GenAIInfra/microservices-connector# curl -X PUT "http://localhost:8008/loglevel" -d '{"log_level":"debug"}' -H "Content-Type: application/json"
log level set to debug
root@cis-gms-worker-3:~/zkf/repo/kfreez/GenAIInfra/microservices-connector# curl -X PUT "http://localhost:8008/loglevel" -d '{"log_level":"info"}' -H "Content-Type: application/json"
log level set to info
root@cis-gms-worker-3:~/zkf/repo/kfreez/GenAIInfra/microservices-connector# 

Issues

n/a.

Type of change

List the type of change like below. Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would break existing design and interface)

Dependencies

n/a.

Tests

no new feature, CI/CD covers the regression tests

[irisdingbj]

Shall this be on Debug level instead of Info level?

[KfreeZ]

from my view, this information is kind of useful for me, to know what condition trigger the reconcile, we don't want unexpected reconcile, if we hide this information to Debug, it would be less easier to find out such problem, espically for un-experienced developers.
Besides, there is no log.Debug, instead, it's log.V(2).Info

[irisdingbj]

We should add an option when controller start, to let user select the log level they want to set, eg: --logLevel debug
in such case, they can have much info in logs.
It does not make sense to have most info output to Info level by default.

[KfreeZ]

We should add an option when controller start, to let user select the log level they want to set, eg: --logLevel debug in such case, they can have much info in logs. It does not make sense to have most info output to Info level by default.

it's implemented

[zhlsunshine]

LGTM

[irisdingbj]

Thanks @KfreeZ for adding this support, Can we change it a little bit to better relflect HTTP VERBs? like:

curl -X GET "http://localhost:8008/loglevel -- this will return current loglevel for user
curl -X PUT "http://localhost:8008/loglevel -d '{"log_level":"debug"}' -- this will change current loglevel to 'debug`
also plz update docs to tell user how to use it.

[KfreeZ]

Thanks @KfreeZ for adding this support, Can we change it a little bit to better relflect HTTP VERBs? like:

curl -X GET "http://localhost:8008/loglevel -- this will return current loglevel for user curl -X PUT "http://localhost:8008/loglevel -d '{"log_level":"debug"}' -- this will change current loglevel to 'debug` also plz update docs to tell user how to use it.

done