You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 705bbfd
Browse filesBrowse the repository at this point in the historyBrowse files
Name the parked and canceled resume outcomes on the route metric
ate.router.resume put budget exhaustion, lot rejection, client
cancellation and real failures all under unknown. Add parked_exhausted,
parked_rejected and canceled; unknown now means a failed resume or a
direction that resumes nothing.
Copy file name to clipboardExpand all lines: docs/observability.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -306,7 +306,7 @@ For `ate.workerpool.desired_workers` and `ate.workerpool.ready_workers`:
306
306
For `atenet.router.route.duration`:
307
307
*`ate.router.outcome` categorizes the route attempt result: `ok`, `cancelled`, `timeout`, `no_capacity`, `failed_precondition`, `lock_conflict`, `not_found`, `unavailable`, `rate_limited`, or `resume_error`.
308
308
* The router and the scheduler both report `no_capacity` for one condition, but they count different events. The scheduler records one sample on `ate.scheduler.assignment.duration` for each resume. The router records one sample for each request. Many requests can join one resume, and one parked request can cause more than one resume. Thus do not compare the two counts directly.
309
-
*`ate.router.resume` indicates the singleflight execution state of actor resumption: `none` (the resume found the actor already running), `triggered` (this request completed a cold activation), `joined` (this request waited on another request's resume, which activated the actor), or `unknown` (the resume did not complete, so whether an activation ran is unknown). `ate.template.atespace` and `ate.template.name` hold `unknown` when the router has no template to name.
309
+
*`ate.router.resume` indicates the singleflight execution state of actor resumption: `none` (the resume found the actor already running), `triggered` (this request completed a cold activation), `joined` (this request waited on another request's resume, which activated the actor), `parked_exhausted` (the request waited out the parking budget and failed with the last capacity error), `parked_rejected` (the parking lot was full, so the request was shed at once), `canceled` (the request ended, by a client disconnect or its deadline, before the resume answered), or `unknown` (the resume failed for another reason, so whether an activation ran is unknown). `ate.template.atespace` and `ate.template.name` hold `unknown` when the router has no template to name.
310
310
311
311
For `ate.imagecache.requests`:
312
312
*`ate.imagecache.outcome` is `hit` when the node holds a complete image record — every layer directory the record names is present — and `miss` when the lookup must pull. A failed lookup is neither: `error` is a failed lookup whatever the cause, and `cancelled` or `timeout` is the caller giving up, as on `ate.router.outcome`. So the hit ratio is `hit / (hit + miss)`, with failures and abandoned lookups out of the denominator.
0 commit comments