mirror of
https://github.com/fnproject/fn.git
synced 2022-10-28 21:29:17 +03:00
e637661ea2
* Adding a way to inject a request ID It is very useful to associate a request ID to each incoming request, this change allows to provide a function to do that via Server Option. The change comes with a default function which will generate a new request ID. The request ID is put in the request context along with a common logger which always logs the request-id We add gRPC interceptors to the server so it can get the request ID out of the gRPC metadata and put it in the common logger stored in the context so as all the log lines using the common logger from the context will have the request ID logged
36 lines
1.3 KiB
Go
36 lines
1.3 KiB
Go
// Copyright 2017 Michal Witkowski. All Rights Reserved.
|
|
// See LICENSE for licensing terms.
|
|
|
|
//
|
|
/*
|
|
grpc_logging is a "parent" package for gRPC logging middlewares.
|
|
|
|
General functionality of all middleware
|
|
|
|
The gRPC logging middleware populates request-scoped data to `grpc_ctxtags.Tags` that relate to the current gRPC call
|
|
(e.g. service and method names).
|
|
|
|
Once the gRPC logging middleware has added the gRPC specific Tags to the ctx they will then be written with the logs
|
|
that are made using the `ctx_logrus` or `ctx_zap` loggers.
|
|
|
|
All logging middleware will emit a final log statement. It is based on the error returned by the handler function,
|
|
the gRPC status code, an error (if any) and it will emit at a level controlled via `WithLevels`.
|
|
|
|
This parent package
|
|
|
|
This particular package is intended for use by other middleware, logging or otherwise. It contains interfaces that other
|
|
logging middlewares *could* share . This allows code to be shared between different implementations.
|
|
|
|
Field names
|
|
|
|
All field names of loggers follow the OpenTracing semantics definitions, with `grpc.` prefix if needed:
|
|
https://github.com/opentracing/specification/blob/master/semantic_conventions.md
|
|
|
|
Implementations
|
|
|
|
There are two implementations at the moment: logrus and zap
|
|
|
|
See relevant packages below.
|
|
*/
|
|
package grpc_logging
|