Skip to content

docs(readme): explain the supervisor, build and config - #157

Merged
catinspace-au merged 6 commits into
mainfrom
docs/readme-human
Nov 13, 2026
Merged

catinspace-au merged 6 commits into
mainfrom
docs/readme-human

Conversation

@catinspace-au

Copy link
Copy Markdown
Contributor

The README opens with the supervisor's role around Vector, the build, the two transports and the config cascade in about 530 words. Endpoints, the metrics merge, reload and the chart stay in docs/internals.md. The README links there.

The working guide moved to CONTRIBUTING.md. The crate description matches the GitHub description.

The README opens with the supervisor's role around Vector, the build, the two transports and the config cascade in about 530 words. Endpoints, the metrics merge, reload and the chart stay in docs/internals.md. The README links there.

The working guide moved to CONTRIBUTING.md. The crate description matches the GitHub description.
The cascade now lists the working directory's .env between the environment and the config file. The readiness row says /readyz proves the child is alive after spawn and the sink isn't stalled. It proves nothing about traffic. The docs site link is an autolink for markdownlint.
The bite table wrongly says a ${VAR} credential reaches the broker. The loader refuses any credential holding ${ before Vector starts.
The version pin, unwired config key and auto-commit rows describe current behaviour. Old measurements and dates are removed.
The README says hot reload needs enabling. Changes that fail validation are never sent. It names metrics.vector_metrics_address as the exporter address setting. The address stays on loopback.
The validator note counts eight ignored cases across two files. The lag-trigger row says the default scales on CPU alone. A deployment can add a pressure trigger through keda.extraTriggers if needed.
@catinspace-au
catinspace-au merged commit 47cc1e4 into main Nov 13, 2026
13 checks passed
@catinspace-au
catinspace-au deleted the docs/readme-human branch November 13, 2026 03:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant