Overview
Production monitoring is the watching side of Coldtea's lifecycle. It reads a repository and the production signals you connect, then focuses on two things: catching regressions in production, and improving the codebase as it goes.
Signals are optional but they sharpen it
Even though the monitoring agents continually help improve your codebase, sharpening its output by correlating production signals e.g., errors, logs, user feedback makes it sharper.
Reading these signals needs connected providers. Without any, production monitoring still files work from the code alone, but it cannot see production errors, usage, or deploy state.
If you want production in the picture, connect signals first.
Where to go next
- How it works for what one day looks like and what it leaves behind.
- Settings and permissions to set how much runs without you.
- Connect signals to let it read production.
Comments and annotations
Mark an exact spot in the terminal, a diff, a plan, or a live page, write what you mean, and send a batch of comments to the agent at once.
How it works
What one day of production monitoring does: where it looks, what makes something worth filing, and the record a finished day leaves you.