-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[serve] Add telemetry for lightweight config updates #34039
Conversation
Signed-off-by: Cindy Zhang <[email protected]>
Signed-off-by: Cindy Zhang <[email protected]>
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.
Just a nit, otherwise LGTM, do we need approval from anyone else on this?
src/ray/protobuf/usage.proto
Outdated
// Whether num_replicas changed as a lightweight config update | ||
SERVE_NUM_REPLICAS_UPDATED = 15; | ||
// Whether user_config changed as a lightweight config update | ||
SERVE_USER_CONFIG_UPDATED = 16; | ||
// Whether autoscaling_config changed as a lightweight config update | ||
SERVE_AUTOSCALING_CONFIG_UPDATED = 17; |
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.
// Whether num_replicas changed as a lightweight config update | |
SERVE_NUM_REPLICAS_UPDATED = 15; | |
// Whether user_config changed as a lightweight config update | |
SERVE_USER_CONFIG_UPDATED = 16; | |
// Whether autoscaling_config changed as a lightweight config update | |
SERVE_AUTOSCALING_CONFIG_UPDATED = 17; | |
// Whether num_replicas changed as a lightweight config update | |
SERVE_NUM_REPLICAS_LIGHTWEIGHT_UPDATED = 15; | |
// Whether user_config changed as a lightweight config update | |
SERVE_USER_CONFIG_LIGHTWEIGHT_UPDATED = 16; | |
// Whether autoscaling_config changed as a lightweight config update | |
SERVE_AUTOSCALING_CONFIG_LIGHTWEIGHT_UPDATED = 17; |
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.
I believe we need approval from either @pcmoritz or @thomasdesr.
Signed-off-by: Cindy Zhang <[email protected]>
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.
Telemetry Boop
Failures unrelated. @edoakes ready for merge |
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.
Approved for cherry picking
This change adds new telemetry to get more insight into if and how users are using the lightweight config updates feature of Serve. It adds the telemetry tags: - `SERVE_NUM_REPLICAS_UPDATED`: whether `num_replicas` was updated (without any heavyweight option updated) - `SERVE_USER_CONFIG_UPDATED`: whether `user_config` was updated (without any heavyweight option updated) - `SERVE_AUTOSCALING_CONFIG_UPDATED`: whether `autoscaling_config` was updated (without any heavyweight option updated) These values are set to True as long as the user uses the feature at least once for any deployment in any application on the cluster.
This change adds new telemetry to get more insight into if and how users are using the lightweight config updates feature of Serve. It adds the telemetry tags: - `SERVE_NUM_REPLICAS_UPDATED`: whether `num_replicas` was updated (without any heavyweight option updated) - `SERVE_USER_CONFIG_UPDATED`: whether `user_config` was updated (without any heavyweight option updated) - `SERVE_AUTOSCALING_CONFIG_UPDATED`: whether `autoscaling_config` was updated (without any heavyweight option updated) These values are set to True as long as the user uses the feature at least once for any deployment in any application on the cluster. Signed-off-by: Cindy Zhang <[email protected]>
This change adds new telemetry to get more insight into if and how users are using the lightweight config updates feature of Serve. It adds the telemetry tags: - `SERVE_NUM_REPLICAS_UPDATED`: whether `num_replicas` was updated (without any heavyweight option updated) - `SERVE_USER_CONFIG_UPDATED`: whether `user_config` was updated (without any heavyweight option updated) - `SERVE_AUTOSCALING_CONFIG_UPDATED`: whether `autoscaling_config` was updated (without any heavyweight option updated) These values are set to True as long as the user uses the feature at least once for any deployment in any application on the cluster. Signed-off-by: Cindy Zhang <[email protected]>
This change adds new telemetry to get more insight into if and how users are using the lightweight config updates feature of Serve. It adds the telemetry tags: - `SERVE_NUM_REPLICAS_UPDATED`: whether `num_replicas` was updated (without any heavyweight option updated) - `SERVE_USER_CONFIG_UPDATED`: whether `user_config` was updated (without any heavyweight option updated) - `SERVE_AUTOSCALING_CONFIG_UPDATED`: whether `autoscaling_config` was updated (without any heavyweight option updated) These values are set to True as long as the user uses the feature at least once for any deployment in any application on the cluster.
This change adds new telemetry to get more insight into if and how users are using the lightweight config updates feature of Serve. It adds the telemetry tags: - `SERVE_NUM_REPLICAS_UPDATED`: whether `num_replicas` was updated (without any heavyweight option updated) - `SERVE_USER_CONFIG_UPDATED`: whether `user_config` was updated (without any heavyweight option updated) - `SERVE_AUTOSCALING_CONFIG_UPDATED`: whether `autoscaling_config` was updated (without any heavyweight option updated) These values are set to True as long as the user uses the feature at least once for any deployment in any application on the cluster. Signed-off-by: elliottower <[email protected]>
This change adds new telemetry to get more insight into if and how users are using the lightweight config updates feature of Serve. It adds the telemetry tags: - `SERVE_NUM_REPLICAS_UPDATED`: whether `num_replicas` was updated (without any heavyweight option updated) - `SERVE_USER_CONFIG_UPDATED`: whether `user_config` was updated (without any heavyweight option updated) - `SERVE_AUTOSCALING_CONFIG_UPDATED`: whether `autoscaling_config` was updated (without any heavyweight option updated) These values are set to True as long as the user uses the feature at least once for any deployment in any application on the cluster. Signed-off-by: Jack He <[email protected]>
Why are these changes needed?
This change adds new telemetry to get more insight into if and how users are using the lightweight config updates feature of Serve. It adds the telemetry tags:
SERVE_NUM_REPLICAS_UPDATED
: whethernum_replicas
was updated (without any heavyweight option updated)SERVE_USER_CONFIG_UPDATED
: whetheruser_config
was updated (without any heavyweight option updated)SERVE_AUTOSCALING_CONFIG_UPDATED
: whetherautoscaling_config
was updated (without any heavyweight option updated)These values are set to True as long as the user uses the feature at least once for any deployment in any application on the cluster.
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.