reckon
Integrations

Integrations

The observability, CI/CD, messaging, infrastructure, cache, database, and optional log-store clients wired into reckon.

reckon gives a coding agent one isolated, per-environment workspace for correlating evidence across existing CLIs. It does not wrap these tools in a new binary; the agent calls each client directly as the investigation narrows.

The workspace is read-only by usage. Some upstream clients can mutate production, so credential permissions, client safeguards, approved command shapes, and approval prompts are part of the contract.

Observability & CI/CD

CLIEvidence it covers
grafanaDashboards, datasources, alerts, annotations
cubeapmDistributed traces, PromQL metrics, LogsQL logs
jenkinsJobs, builds, pipelines, logs, nodes
awsCloudWatch metrics and logs, ALB/ELB, ECS, SQS, RDS, S3
ghPull requests, GitHub Actions runs, releases, issues

Message queues

CLIEvidence it covers
kcatKafka metadata and group-less topic reads
rpkKafka consumer-group lag and cluster information

Kubernetes & cache

CLIEvidence it covers
kubectlPod and deployment state, events, rollout history
redis-cliRedis INFO, SLOWLOG, LATENCY, DBSIZE, and SCAN diagnostics

Databases

CLIEvidence it covers
mongoshMongoDB diagnostics through a read-only database role
psqlPostgreSQL diagnostics through a read-only database role
mysqlMySQL diagnostics through a read-only database role and workspace option file
clickhouse clientClickHouse tables, slow queries, metrics, events, and bounded exploratory reads through a read-only role and --readonly=1

Optional log stores

CLIEvidence it covers
esElasticsearch/ELK cluster health, index state, Query DSL, and SQL search

Integration guides

direnv supplies the folder-local environment and jq supports structured output processing; neither is an incident-data integration.