{"slug": "show-hn-agentic-telemetry-simple-observability-tool-for-agentic-system", "title": "Show HN: Agentic Telemetry – Simple Observability Tool for Agentic System", "summary": "A developer released Agentic Telemetry, a minimal alpha observability collector for agentic systems that stores events in SQLite and uses only the Python standard library. The service runs via `python3 server.py`, listens on http://127.0.0.1:8000 by default, and exposes a POST /v1/events endpoint accepting one event or a JSON array of up to 100 events, with event_type and run_id required. The dashboard summarizes runs, agents, errors, activity over the last 24 hours, and activity by agent from the latest 1,000 events, refreshing every 10 seconds; authentication, retention policies, distributed deployment, and metric aggregation are not included.", "body_md": "A lightweight telemetry collector for agentic systems. It stores events in SQLite and lets you inspect activity by run or agent. It uses only the Python standard library.\n\n```\npython3 server.py\n```\n\nBy default, the service listens on `http://127.0.0.1:8000` and creates `telemetry.db` in the current working directory. Configure `TELEMETRY_HOST`, `TELEMETRY_PORT`, or `TELEMETRY_DB` to change these defaults.\n\nOpen `http://127.0.0.1:8000/` to view the dashboard. It summarizes runs, agents, errors, activity over the last 24 hours, and activity by agent from the latest 1,000 events. Filter the event stream by run, event type, or text. The dashboard refreshes every 10 seconds.\n\n```\ncurl -X POST http://127.0.0.1:8000/v1/events \\\n  -H 'Content-Type: application/json' \\\n  -d '{\n    \"event_type\": \"tool_call.completed\",\n    \"run_id\": \"run-123\",\n    \"agent_id\": \"researcher\",\n    \"parent_agent_id\": \"orchestrator\",\n    \"task_id\": \"task-7\",\n    \"status\": \"success\",\n    \"attributes\": {\"tool\": \"web_search\", \"duration_ms\": 240}\n  }'\n```\n\nThe endpoint accepts one event or a JSON array of up to 100 events. `event_type` and `run_id` are required. If omitted, `id` and `timestamp` are generated by the service. Event names are up to the sender; examples include `agent.started`, `agent.handoff`, `tool_call.completed`, and `llm.response`.\n\n```\ncurl 'http://127.0.0.1:8000/v1/events?run_id=run-123&limit=100'\n```\n\nCombine any of these filters: `run_id`, `agent_id`, `event_type`, `task_id`, and `status`. The default `limit` is 100 and the maximum is 1,000. Use `GET /health` for a health check.\n\nAn event can include `id`, `timestamp`, `event_type`, `run_id`, `agent_id`, `parent_agent_id`, `task_id`, `status`, and `attributes`. For agent handoffs, use the same `run_id` and record the source agent or handoff details in `parent_agent_id` and `attributes`.\n\nThis is a minimal alpha release. Authentication, retention policies, distributed deployment, and metric aggregation are not included. The service listens on the loopback address by default for local development.", "url": "https://wpnews.pro/news/show-hn-agentic-telemetry-simple-observability-tool-for-agentic-system", "canonical_source": "https://github.com/yuyalapis/agentic-telemetry", "published_at": "2026-10-05 15:16:03+00:00", "updated_at": "2026-10-05 15:20:45.887843+00:00", "lang": "en", "topics": ["ai-agents", "mlops", "developer-tools", "ai-tools"], "entities": ["Agentic Telemetry", "SQLite", "Python"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/show-hn-agentic-telemetry-simple-observability-tool-for-agentic-system", "markdown": "https://wpnews.pro/news/show-hn-agentic-telemetry-simple-observability-tool-for-agentic-system.md", "text": "https://wpnews.pro/news/show-hn-agentic-telemetry-simple-observability-tool-for-agentic-system.txt", "jsonld": "https://wpnews.pro/news/show-hn-agentic-telemetry-simple-observability-tool-for-agentic-system.jsonld"}}