-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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(unstable): add metrics to otel #27143
Conversation
let x = v8::ValueView::new(scope, string); | ||
match x.data() { | ||
v8::ValueViewData::OneByte(bytes) => { | ||
String::from_utf8_lossy(bytes).into_owned() | ||
} | ||
v8::ValueViewData::TwoByte(bytes) => String::from_utf16_lossy(bytes), | ||
} |
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.
Is there a reason to do it instead of v8::String::to_rust_string_lossy()
?
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.
ext/telemetry/lib.rs
Outdated
spans.on_end(temporary_span.0); | ||
} | ||
|
||
pub struct TemporaryMetricsExport { |
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.
Could you add some docstrings here about the purpose of these structs and enums?
Co-Authored-By: Luca Casonato <[email protected]>
Refs: #26852
Initial support for exporting metrics.