Graph Kernel Monitoring Guide

Full HTML reader

Read the full artifact

Extracted abstract or opening context

The Graph Kernel service exposes metrics, structured logs, and health endpoints for production observability. This guide covers monitoring setup, key metrics, alerting, and troubleshooting. | Endpoint | Purpose | Response | |----------|---------|----------| | `GET /health` | Detailed status | Full service state including DB | | `GET /health/live` | Liveness probe | 200 if process is running | | `GET /health/ready` | Readiness probe | 200 if accepting traffic, 503 otherwise | | `GET /health/startup` | Startup probe | 200 when fully initialized | | Metric | Type | Labels | Description | |--------|------|--------|-------------| | `graph_kernel_requests_total` | Counter | path, method, status | Total HTTP requests | | `graph_kernel_request_duration_seconds` | Histogram | path, method | Request latency | | Metric | Type | Description | |--------|------|-------------| | `graph_kernel_slices_generated_total` | Counter | Total slices generated | | `graph_kernel_slice_turns_count` | Histogram | Turns per slice | | `graph_kernel_slice_edges_count` | Histogram | Edges per slice | | `graph_kernel_slice_latency_ms` | Histogram | Slice generation time | | Metric | Type | Labels | Description | |--------|------|--------|-------------| | `graph_kernel_token_verifications_total` | Counter | result | Token verification attempts |

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.