-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Metrics and Logging name changes #541
Conversation
@@ -102,7 +102,7 @@ extension ApplicationProtocol { | |||
eventLoopGroup: self.eventLoopGroup, | |||
logger: self.logger | |||
) { (request, responseWriter: consuming ResponseWriter, channel) in | |||
let logger = self.logger.with(metadataKey: "hb_id", value: .stringConvertible(RequestID())) | |||
let logger = self.logger.with(metadataKey: "hb.id", value: .stringConvertible(RequestID())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let logger = self.logger.with(metadataKey: "hb.id", value: .stringConvertible(RequestID())) | |
let logger = self.logger.with(metadataKey: "http.request.id", value: .stringConvertible(RequestID())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non standard and we don't own http
namespace. Using hb.request.id
IMO we should follow the OTel guides: |
So I've followed the conventions for HTTP metrics |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
These are some metrics and logging name changes based off discussions in #539
These are not set in stone, but I thought implementing the changes would trigger final decisions