khi
A log viewer for Kubernetes troubleshooting
Runssource: GitHubGoApache-2.0commit d402902ffbc2
Go, Apache-2.0 licensed. The project labels itself: google cloud platform, kubernetes, logging, observability, troubleshooting and visualizer.
khi runs. An Argusic agent installed it in 8 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
make setup completed successfully: npm install, protobuf codegen, backend codegen, MSDF font atlas, Angular production build, and Go compiler all built without errors; all 1417 frontend tests pass; all backend Go tests pass (skipping Cloud Logging tests due to missing GCP credentials); the khi binary runs and serves on port 8081.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Chrome browser installed; frontend tests cannot run2 minutes
- Go compiler not installed; required Go 1.26.01 minute
- Node.js 18.x installed but 26.7.0 required1 minute
- gcloud CLI not installed; cloud logging tests fail without credentials1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- Backend tests: KHI_SKIP_CLOUD_LOGGING=true go test github.com/GoogleCloudPlatform/khi/... exited 0, all 'ok'. Frontend tests: npx ng test --browsers ChromeHeadlessNoSandbox --watch=false exited 0, 1417 SUCCESS. Server launch: timeout 5 ./khi --port 8081 started, printed 'Starting KHI server with listening 127.0.0.1:8081'
- Model tokens used
- 87,685
- Exact commit tested
- d402902ffbc2
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
87,685 Now let me compile my final report. Here's the summary of everything I did and observed: 1. **Install**: Ran `make setup` which successfully completed: npm install (1383 packages), protobu… 2. **Go Tests**: Ran `KHI_SKIP_CLOUD_LOGGING=true go test github.com/GoogleCloudPlatform/khi/...` —… 3. **Frontend Tests**: Ran `npx ng test --browsers ChromeHeadlessNoSandbox` — **1417 SUCCESS**, 0 f… 4. **Server Launch**: `./khi --port 8081` starts successfully, prints info about listening on `loca… **Errors encountered:** - **Go not installed**: Missing Go 1.26.0 compiler. Fix: Downloaded Go 1.26.0 prebuilt binary to `/… - **Node.js version too old** (18.x instead of required 26.7.0). Fix: Downloaded Node 26.7.0 prebui… - **`gcloud` CLI not available**: Some tests require GCP credentials. Fix: Used `KHI_SKIP_CLOUD_LOG… - **Frontend tests need Chrome**: No Chrome binary installed. Fix: Downloaded Chrome for Testing 13… - **Chrome crashpad handler not executable**: Fix: `chmod +x chrome_crashpad_handler`.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 8 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.13 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.11 |
Topics (from GitHub)
google-cloud-platformkubernetesloggingobservabilitytroubleshootingvisualizer
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/khi)Questions
- Does khi run?
- Yes. khi runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test khi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d402902ffbc2. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test khi?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does khi take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does khi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing khi?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for khi?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.