Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jacobpevans.com/llms.txt

Use this file to discover all available pages before exploring further.

If an AI agent touched code, there’s a trace.
Every AI coding interaction emits OpenTelemetry — IDE events, model calls, token counts, latency, cost. The Cribl Edge tier collects and reshapes it. Cribl Stream routes it. Splunk indexes it. The VisiCore apps make it readable.

AI telemetry pipeline

Splunk apps

RepoWhat it does
VisiCore_App_for_AI_ObservabilityDashboard Studio v2 dashboards. Cost, usage, performance per model, per project, per developer.
VisiCore_TA_AI_ObservabilityTechnology add-on. Field aliases, CIM mappings, lookups, search-time transforms.

Cribl Edge packs (collectors)

RepoCollects from
cc-edge-claude-code-otelClaude Code (OTEL hooks)
cc-edge-copilot-otelGitHub Copilot Chat (OTLP gRPC)
cc-edge-vscode-ioVS Code (logs + telemetry)
cc-edge-gemini-antigravity-ioGemini Antigravity
cc-edge-the-mac-pack-iomacOS system health (auxiliary signal)
cc-edge-macos-systemmacOS-native system events

Cribl Stream collectors

RepoWhat it does
cc-stream-github-copilot-rest-ioGitHub Copilot usage metrics via REST API. Per-org / per-seat usage data.

Why per-tool packs

Each AI coding tool emits slightly different telemetry shapes. Per-tool packs keep the parsing and enrichment isolated; a Copilot schema change shouldn’t break the Claude pipeline. The shared CIM mapping in VisiCore_TA_AI_Observability is where the normalization happens.

What’s next

Phase B will expand each pack into its own page with the field map, sample event, and dashboard screenshots. For now, each repo’s README.md documents the collection details.