-
Notifications
You must be signed in to change notification settings - Fork 93
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
chore(llm-monitoring): Extract AI data from data instead of measurements #3630
Conversation
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.
Long term, we only want data
to stay. So, I would change the metric to read from data
fields and extract measurements to those data
fields if need be, otherwise the SDK will start sending them directly and no extraction needed.
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
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.
@colin-sentry could you please expand the PR description to include the motivation for this change? Can be a one-liner.
Some(Value::U64(u)) => Some(*u as f64), | ||
_ => None, | ||
} | ||
} |
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.
Nice!
We need to start porting things over to data, since
measurements
is being deprecated and will be removed from the APIs.For backcompat, this goes data -> measurement -> metric