-
Notifications
You must be signed in to change notification settings - Fork 123
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
feat: Adding gfe_latencies metric to built-in metrics #3490
base: main
Are you sure you want to change the base?
Conversation
085d5b8
to
7383362
Compare
TagContext tagContext, | ||
Attributes attributes, | ||
Span span, | ||
Map<String, String> builtInMetricsAttributes) { | ||
MeasureMap measureMap = STATS_RECORDER.newMeasureMap(); | ||
String serverTiming = metadata.get(SERVER_TIMING_HEADER_KEY); | ||
if (serverTiming != null && serverTiming.startsWith(SERVER_TIMING_HEADER_PREFIX)) { |
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.
Can we make this compatible with other server timing headers?
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.
More specifically, a server timing header is in the format of [component]; dur=[latency]
, as stated in the w3c standard. gfet4t7
is just one of the possible component and it is not guaranteed to be the first one, so startsWith
shall be changed to something like contains
.
b6bd6f2
to
3b03055
Compare
105edeb
to
59459ae
Compare
6e6e94b
to
6fbf28c
Compare
No description provided.