grpc-go

Commit Graph

Author	SHA1	Message	Date
Doug Fawley	fbff2abb0f	*: update `interface{}` to `any` and `go.mod` version to `go 1.19` (#6544 )	2023-08-14 09:04:46 -07:00
Garrett Gutierrez	506b773066	Implemented component logging (#3617 )	2020-06-26 12:04:47 -07:00
Garrett Gutierrez	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
Menghan Li	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
Menghan Li	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
Jan Tattermusch	ddbf6c46a6	autofix license notice	2017-06-08 14:42:19 +02:00
Adam Michalik	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
Tamir Duberstein	524ed331d2	Add grpclog/glogger to restore glog functionality	2015-06-09 10:47:28 -04:00

9 Commits