# An orders pipeline ships tomorrow as a script with stdout logging and no monitors

Canonical URL: <https://datadriven.io/problems/an-orders-pipeline-ships-tomorrow-as-a-script-with-stdout-lo-ed188b02>

Domain: Pipeline Design · Difficulty: medium

## Problem

An orders pipeline ships tomorrow as a script with stdout logging and no monitors. Make it operable on day one. Add the operational shell (durable logs, metrics, traces with run_id stamped on every artifact). Add the three day-one monitors (did it run, did it succeed, was the output the right size) wired to a paging destination. Route alerts across three severity tiers (page, Slack channel, email digest) so on-call only gets paged for real problems. Author a runbook with the five sections and link every alert to it. The Snowflake mart and dashboard remain on the production read path.

## Related

- [All practice problems](https://datadriven.io/problems)
- [Mock interview mode](https://datadriven.io/interview/an-orders-pipeline-ships-tomorrow-as-a-script-with-stdout-lo-ed188b02)
- [System Design Interview Questions](https://datadriven.io/data-engineering-system-design)
- [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep)
- [Daily Challenge](https://datadriven.io/daily)

---

Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.