Ask your infrastructurewhat went wrong.

An agent workspace wiring read-only observability, CI/CD, and infrastructure CLIs into one isolated credential environment so a coding agent can investigate incidents, run RCAs, and understand production behavior.

read-only, always

Scroll to explore

Speaks the language of your stack

GrafanaJenkinsCubeAPMAWSGitHub ActionsKafkaKubernetesRedisMongoDBPostgreSQLMySQLElasticsearch

How an investigation flows

start broad, then narrow

01

Assess

Check Grafana alerts, Jenkins build status, and the CubeAPM service inventory.

grafana alert rule list -o json
02

Investigate errors

Search error traces and related logs, then open the trace waterfall for the affected service.

cubeapm traces search --status error --last 1h
03

Check metrics

Compare error rate, latency, and service health across the incident window.

cubeapm metrics query 'error_rate' --last 1h
04

Check deployments

Review deploy annotations, recent Jenkins builds, build logs, merged pull requests, and releases.

jenkins build list checkout/deploy --limit 5
05

Map dependencies

Trace error propagation through the dependency graph and check the supporting infrastructure.

cubeapm traces get <trace-id> -o json
06

Correlate

Match deployment timestamps with error spikes, Grafana annotations, and cluster events.

kubectl get events -n checkout --sort-by=.lastTimestamp

Everything, in one workspace

A read-only toolbelt for a coding agent that investigates like your best on-call.

01

Incident investigations

Move from an alert to traces, metrics, logs, deployment history, and infrastructure state with a disciplined RCA workflow.

02

Cross-system correlation

Match error and latency windows with builds, releases, cluster events, queue lag, cache health, and database evidence.

03

Read-only safety

Production-only conventions, read-only roles, session safeguards, command allowlists, and approval prompts keep investigations read-shaped.

04

One operations toolbelt

Use twelve wired CLIs plus optional Elasticsearch access without switching credential contexts or stitching together separate workspaces.

One toolbelt, twelve CLIs

twelve CLIs, one session

Correlate the timeline

Wire together twelve read-only CLIs in one isolated credential environment so a coding agent can correlate signals across systems in one session.

correlate the timestamps

incident / checkout correlation view
01Grafana alert
grafana alert rule list -o json

Establish the active alert window.

02Jenkins build
jenkins job list --recursive --status FAILURE -o json

Compare build start and completion times.

03CubeAPM error rate
cubeapm metrics query 'rate(http_requests_total{status=~"5.."}[5m])' -o json

Locate the error spike.

04Kubernetes event
kubectl get events -n checkout --sort-by=.lastTimestamp | tail -30

Check whether the failure lines up with cluster events.

we'll see you on-call

Ready in one command

Clone the workspace, run the idempotent setup script, add credentials, and start investigating.