-
Notifications
You must be signed in to change notification settings - Fork 86
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[vpj][controller] Emit push job status metrics from controller (#1185)
VPJ communicates with the controller to write PushJobDetails to the PUSH_JOB_DETAILS_STORE_NAME system store. This PR introduces new metrics emitted by the controller for push job success/failure. New Metrics Added (Count and CountSinceLastMeasurement added in Tehuti, hence using tehuti:0.12.2): batch_push_job_success, batch_push_job_failed_user_error, batch_push_job_failed_non_user_error incremental_push_job_success, incremental_push_job_failed_user_error, incremental_push_job_failed_non_user_error Current flow is VPJ checks 'push.job.status.upload.enable' config and sends PushJobDetails to '/send_push_job_details' path in Venice-controller, which writes it to the push job details system store. Derive success/failure in the controller and emit metrics, tying metric emission and push job details upload via the same config. This config is enabled everywhere, and this approach doesn’t require deployment ordering (controllers -> VPJ) unlike other options and no schema evolution needed. Config introduced: Added parent controller config 'push.job.failure.checkpoints.to.define.user.error' to provide a custom list of these checkpoints based on the use case to emit the metrics accordingly. DEFAULT_PUSH_JOB_USER_ERROR_CHECKPOINTS will be used by default.
- Loading branch information
1 parent
5619993
commit 328d72a
Showing
25 changed files
with
1,247 additions
and
384 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.