778860e606
testing: update Go to 1.19 ( #5717 )
2022-10-17 15:04:34 -07:00
ccc060cb43
grpclog.DepthLoggerV2: Correct comment: formats like fmt.Println ( #5038 )
2021-12-07 13:58:17 -08:00
49f6388789
grpclog: support formatting output as JSON ( #4854 )
2021-10-11 11:06:15 -07:00
d9063e7af3
standardized experimental warnings ( #3917 )
2020-10-02 09:11:08 -07:00
8beeedb8b1
internal: clean up all usages of grpclog, and replace with component ( #3719 )
2020-08-06 13:19:17 -07:00
506b773066
Implemented component logging ( #3617 )
2020-06-26 12:04:47 -07:00
fff75ae40f
channelz: log on channelz trace events and trace on channelz relevant logs. ( #3329 )
...
channelz: log on channelz trace events and trace on channelz relevant logs. (#3329 )
2020-02-14 10:11:26 -08:00
861d8e7992
internal: fix typos in comments ( #3046 )
2019-09-30 15:30:07 -07:00
bcfa7b30ac
Downgrade grpclb package info logs to V(2). ( #2710 )
...
Fixes #2709 .
2019-03-22 10:11:37 -07:00
f8dbc38bdc
Fix "deprecated" function godoc comments to match standard formatting ( #2027 )
2018-05-02 08:52:49 -07:00
963eb485d8
Fix missing and wrong license ( #1422 )
2017-08-04 13:46:18 -07:00
b34c88b087
Add doc in default implementation fatal functions on os.Exit() ( #1365 )
2017-07-21 09:39:31 -07:00
d6723916d2
Use log severity and verbosity level ( #1340 )
...
- All logs use 1 severity level instead of printf
- All transport logs only go to verbose level 2+
- The default logger only log errors and verbosity level 1
- Add environment variable GRPC_GO_LOG_SEVERITY_LEVEL and GRPC_GO_LOG_VERBOSITY_LEVEL to set severity or verbosity levels for the default logger
2017-07-13 12:10:19 -07:00
2887f9478e
Add Severity and VerboseLevel to grpclog. ( #922 )
...
* Add Severity and VerboseLevel to grpclog.
* keep old interface and add loggerv2
* export NewLoggerv2
2017-06-19 13:57:04 -07:00
a94a7ac054
add license for some files ( #1296 )
2017-06-12 18:10:06 -07:00
ddbf6c46a6
autofix license notice
2017-06-08 14:42:19 +02:00
4a119ee276
Use InfoDepth/FatalDepth in glogger.go
...
This way, log messages will show the proper location where the log
statement originated, instead of "glogger.go:67" or something like that.
2016-11-29 12:51:42 -08:00
65e7361599
Comment: explain concurrent access to grpclog.logger
...
grpc's pluggable logger is not mutex-protected: added comments that it
should be changed only in init() functions.
2016-02-01 15:07:17 -05:00
524ed331d2
Add grpclog/glogger to restore glog functionality
2015-06-09 10:47:28 -04:00
c2d7a03d75
Merge pull request #218 from tamird/stdlib-logger
...
Remove dependency on `glog`
2015-06-08 16:05:18 -07:00
da7217126b
Remove dependency on glog
...
Addresses part of #217 .
2015-06-08 17:44:29 -04:00
f5bae617c6
Add a Makefile to show development commands
...
Signed-off-by: Peter Edge <peter.edge@gmail.com>
2015-05-24 16:05:35 +02:00
77e94abaae
move log to grpclog
2015-05-09 11:38:40 +02:00
