-
Notifications
You must be signed in to change notification settings - Fork 693
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
grpc.request.deadline and grpc.start_time precision is in seconds #131
Labels
Comments
@domgreen you made tracking of the elapsed time, right? It's probably best for you to take this. |
stanhu
added a commit
to stanhu/go-grpc-middleware
that referenced
this issue
Feb 12, 2021
By default, RFC3339 timestamps are used, but our application uses a custom format. This commit enables us to set the format in a consistent manner. Closes grpc-ecosystem#131
stanhu
added a commit
to stanhu/go-grpc-middleware
that referenced
this issue
Feb 12, 2021
By default, RFC3339 timestamps are used, but our application uses a custom format. This commit enables us to set the format in a consistent manner. Closes grpc-ecosystem#131
Can someone review #398? |
johanbrandhorst
pushed a commit
that referenced
this issue
Feb 13, 2021
By default, RFC3339 timestamps are used, but our application uses a custom format. This commit enables us to set the format in a consistent manner. Closes #131
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
grpc.request.deadline
andgrpc.start_time
used.Format(time.RFC3339)
which means maximum precision is in seconds. I believe it would be useful to used.Format(time.RFC3339Nano)
at least.Best would be a configuration option for me to format all logged timestamps as desired.
I can work on a PR for this change if it makes sense.
The text was updated successfully, but these errors were encountered: