Skip to main content

docs/telemetry.md

Metadata​

  • Purpose: Project documentation source file.
  • Domain: documentation
  • Language: md
  • Bytes: 3990
  • Lines: 98
  • Content hash (short): 5fec2119
  • Source (start): docs/telemetry.md:1
  • Source (end): docs/telemetry.md:98

Indexed Symbols​

No indexed functions/methods detected in this file.

Markdown Headings (if applicable)​

  • H1: Telemetry and Endpoint Automation (line 1)
  • H2: Event schema types (line 3)
  • H2: Ingest path (line 11)
  • H2: Enrollment and visibility APIs (line 28)
  • H2: Admin/Ops UI expectations (line 34)
  • H2: Reliability controls (line 46)
  • H2: How metrics are measured (line 54)
  • H2: How a system hooks into Anchor (line 64)
  • H2: Control-center telemetry integration (line 77)

Source Preview​

# Telemetry and Endpoint Automation

## Event schema types

- `HostHeartbeat`
- `PatchCompliance`
- `BackupFailure`
- `ServiceDegraded`
- `PipelineFailure`

## Ingest path

1. Edge agent buffers telemetry locally.
2. Agent flushes payload to `POST /api/v1/events/ingest` over HTTPS with:
   - `Authorization: Bearer <edge enrollment token>`
   - `x-workspace-id: <workspace uuid>`
   - `Idempotency-Key: <uuid>`
3. Gateway validates JWT role/scope, idempotency key, and event schema contract.
4. Routed actions are persisted to `outbox_events`.
5. Outbox dispatcher forwards actions to AgentField reasoners.
6. AgentField completion callbacks persist workflow and audit evidence records.

Note:

- mTLS is supported at ingress/network layer when enabled by platform infra policy.