-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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(routing): success based routing metrics #5951
Conversation
4b55ae3
to
231ad25
Compare
); | ||
|
||
let success_based_connectors = client | ||
.calculate_success_rate( |
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.
why is this function not accepting &str
?
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.
cc: @Aprabhat19
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.
For id_type we are anyhow passing a String value to the service, so that's why we chose not to pass a &str and then clone the value later
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 update the "How did you test it" section in the PR description to include the name of the metric that you queried for?
Type of Change
Description
This PR will enable logging of metrics for Dynamic Routing feature. This will be an async call inside the post_update_tracker.
Additional Changes
Motivation and Context
How did you test it?
Once the PR goes to sandbox a grafana dashboard will be created.
tested the metrics (
DYNAMIC_SUCCESS_BASED_ROUTING
) in local Grafana. Here is the screenshot for the same:Checklist
cargo +nightly fmt --all
cargo clippy