Repository navigation
docs: update Agent Relay SIEM alert messages for v0.15.0 #31985
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -75,21 +75,22 @@ Claude Code adds `claude_tag_channel_user`, and Cursor adds `cursor_pool`, `reli | |
|
|
||
| ## Failure and rebuild fields | ||
|
|
||
| | Field | Meaning | | ||
| |------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | `error` | Error detail on most `WARN` and `ERROR` records, such as a failed claim, identity lookup, build, or delete | | ||
| | `retryable` | `true` when the provider retries or the user can try again. `false` when an administrator must fix configuration or identity. | | ||
| | `message` | Cursor: the exact text shown to the user when Agent Relay fails the claim | | ||
| | `detail` | Cursor: the local reason for a failed claim. It's never sent to Cursor and is truncated at 512 characters. | | ||
| | `stage` | Cursor: the step where the claim failed, such as `owner` or `building` | | ||
| | `reason` | Reaper: why it deleted the workspace, such as `the runner exited with status 1`. Cursor refusals: `no_email`, `no_match`, `inactive`, or `dormant`. | | ||
| | `job_status` | The final provisioner job status of a failed build, such as `failed` or `canceled` | | ||
| | `job_error` | Coder's error summary for a failed build | | ||
| | `build_status` | The latest build's status when Agent Relay rebuilds a workspace or the reaper evaluates it | | ||
| | `deadline` | Claude Code: when Anthropic stops waiting for a runner. Logged when the deadline passes before dispatch. | | ||
| | `status` | Reaper: the runner status the workspace reported, such as `working`, `done 1`, `failed <reason>`, or `orphaned` | | ||
| | `age` | Reaper: time elapsed after the workspace's latest build was created | | ||
| | `failed_deletes` | Reaper: how many delete builds have failed in a row for the workspace | | ||
| | Field | Meaning | | ||
| |-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | `error` | Error detail on most `WARN` and `ERROR` records, such as a failed claim, identity lookup, build, or delete | | ||
| | `retryable` | `true` when the provider retries or the user can try again. `false` when an administrator must fix configuration or identity. | | ||
| | `message` | Cursor: the exact text shown to the user when Agent Relay fails the claim | | ||
| | `detail` | Cursor: the local reason for a failed claim. It's never sent to Cursor and is truncated at 512 characters. | | ||
| | `stage` | Cursor: the step where the claim failed, such as `owner` or `building` | | ||
| | `reason` | Reaper: why it deleted the workspace, such as `the runner exited with status 1`. Cursor refusals: `no_email`, `no_match`, `inactive`, or `dormant`. | | ||
| | `job_status` | The final provisioner job status of a failed build, such as `failed` or `canceled` | | ||
| | `job_error` | Coder's error summary for a failed build | | ||
| | `build_status` | The latest build's status when Agent Relay rebuilds a workspace or the reaper evaluates it | | ||
| | `deadline` | Claude Code: when Anthropic stops waiting for a runner. Logged when the deadline passes before dispatch. | | ||
| | `status` | Reaper: the runner status the workspace reported, such as `working`, `done 1`, `failed <reason>`, or `orphaned` | | ||
| | `agent_lifecycle` | The workspace agent's lifecycle state, such as `starting` or `ready`, on `workspace built, runner handoff` and reaper records. Empty when no agent is connected. `starting` means startup scripts are still running, and `start_error` or `start_timeout` means they failed. | | ||
| | `age` | Reaper: time elapsed after the workspace's latest build was created | | ||
| | `failed_deletes` | Reaper: how many delete builds have failed in a row for the workspace | | ||
|
|
||
| Claude Code nack records don't repeat the failure reason. | ||
| Find it in the `error` or `reason` field of the `WARN` record written just before the nack. | ||
|
|
@@ -223,14 +224,14 @@ Some conditions, such as a stranded Cursor claim, appear only in logs. | |
| | Page when sustained | `pool failed verification, retrying` | Both | `pool`, `template` | A bad API key or environment key, a template without the Agent Relay module, or an organization problem. Alert after several records in a row. | | ||
| | Rate threshold | `nacked spawn hint` | Claude Code | `pool`, `retryable` | Sessions handed back to Anthropic. `retryable: false` ends the session and needs an administrator. | | ||
| | Rate threshold | `failed the claim upstream, the user sees the message` | Cursor | `pool`, `retryable`, `stage` | Users saw a failure. `retryable: false` needs an administrator. `retryable: true` usually means a transient or capacity problem. | | ||
| | Rate threshold | `workspace build failed, reporting retryable and deleting` | Both | `job_error` | A template or infrastructure failure, such as exhausted quota. Agent Relay deletes the workspace right away, so `job_error` might be the only record of why. | | ||
| | Rate threshold | `workspace build passed the session deadline, reporting retryable and deleting` | Both | `pool` | Builds take longer than the pool's `dispatch_deadline`. | | ||
| | Rate threshold | `workspace build failed` | Both | `job_error` | A template or infrastructure failure, such as exhausted quota. Agent Relay deletes the workspace right away, so `job_error` might be the only record of why. | | ||
| | Rate threshold | `workspace build passed the session deadline, reporting failure` or `workspace build succeeded after the session deadline` | Both | `pool` | Builds take longer than the pool's `dispatch_deadline`. | | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Blocking: This row now lists two different outcomes under one "Why":
Fix either by adding a sentence to |
||
| | Rate threshold | `session did not finish cleanly, reporting and deleting` (`reaper`) | Both | `reason` | Runners that exited non-zero, couldn't start, stopped unexpectedly, or never started. | | ||
| | Ticket | `session owner is unresolvable, nacking non-retryable` | Claude Code | `org_service_name` | A Claude user has no active Coder account in the pool's organization, or a Claude Tag channel session arrived without `claude_tag_channel_user`. | | ||
| | Ticket | `request owner cannot be served, refusing the request` | Cursor | `reason` | A Cursor request has no email, no matching Coder account in the organization, or a suspended or dormant account. | | ||
| | Ticket | `work order failed verification, nacking non-retryable` | Claude Code | `pool` | Agent Relay rejected the Anthropic-signed work order. `error` gives the reason. | | ||
| | Ticket | `workspace delete keeps failing, leaving it for an operator` (`reaper`) | Both | `workspace_id` | The reaper stopped retrying after repeated delete failures. Clean up the workspace by hand. | | ||
| | Ticket | `delete workspace failed, leaving for reconciliation` or `delete workspace failed, retrying next sweep` | Both | `workspace_id` | A workspace might still be running and using resources. | | ||
| | Ticket | `delete workspace failed, leaving it for the reaper` or `delete workspace failed, retrying next sweep` | Both | `workspace_id` | A workspace might still be running and using resources. | | ||
| | Dashboard | `resolved session owner`, `claimed pending request`, `workspace build created`, `workspace built, runner handoff`, or `deleting workspace` | Both | `pool`, `client_platform` | The normal session lifecycle, for volume and funnel views. | | ||
|
|
||
| ## Retention and privacy | ||
|
|
||
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.
Blocking: This locates
agent_lifecycleby quotingworkspace built, runner handoffas the lookup key, but the page's own "Match rules" section a few headings down saysmsgtext can change between Agent Relay releases and warns readers not to rely on it that way. Tying the field's provenance to an unstablemsgstring is evidence (which code path emits it), not the reader-facing fact of when the field is present (docs/.style/content-guidelines.md#evidence-justifies-a-claim-and-does-not-belong-in-the-claim). (Reader Advocate)Separately, in the same cell, "
start_errororstart_timeoutmeans they failed" has no clean antecedent for "they": the clause-2 subject (start_error/start_timeout) is singular and isn't itself the thing that "failed," so the reader has to reach back into the prior clause's object ("startup scripts") to resolve it (docs/.style/style-guide/voice-and-tone.md#give-each-pronoun-one-clear-referent). (Copy Editor)Combining both fixes: