InfrastructureSubsection
Monitoring
Two pages with a clean line between them. Logging owns the record — what gets written down and whether a question asked three weeks later has an answer. Alerting starts where a condition has to reach a person, which makes it a question about interrupting somebody rather than about thresholds. Read them in that order: you cannot alert usefully on data you never structured.
What is inside
Every page in this group, with what each one covers.
Where to start
Elsewhere in the section
- InfrastructureInfrastructure is everything that turns code into something running that you can observe, change and roll back. This section covers 11 topics in four groups: DevOps and the pipeline that builds one artifact and promotes it unchanged, the three major clouds and how each contains a mistake, MLOps — the same problems again for a model instead of a binary — and the monitoring that makes an incident answerable at three in the morning.
- DevOpsGetting a change from a developer’s machine to a running system, repeatably and without ceremony. Three topics that stack: the pipeline that decides whether a change is safe, the image format that makes "it works on my machine" a testable claim, and the scheduler that keeps the result running. Each page is about the mechanism rather than a tool’s configuration syntax, which is what transfers when you change tools.
- MLOpsEverything that has to be true before a model is allowed near production, and everything that keeps being true afterwards. Three topics: the pipeline that makes a training run reproducible, the serving path where latency and cost become somebody’s problem, and the index that makes similarity search fast enough to use. Running an LLM feature specifically is LLMOps, in Development.
Found this useful?
Share it with someone who is working on the same problem.