Production Observability

Stand up cloud-native dashboards, logs, alerts, and notification wiring for a small service so teams can see errors and latency before customers report them.

Step 1 of 1

Choose cloud

Choose an option to continue.

Frequently asked questions

Does this deploy an application?
It deploys only the smallest service hook needed to demonstrate log, metric, and trace wiring. Bring your real service names, metric filters, and alert thresholds before using the blueprint for production traffic.
Where does the notification email come from?
Each starter reads a Pulumi config value named notificationEmail. Set it to the address or distribution list your team controls before running pulumi up.
Does this include incident management or on-call rotation?
No. The blueprint stops at cloud-native email notification targets so you can connect your own incident workflow later without adding another platform to the starter.
What should I tune first?
Tune the error threshold, latency threshold, evaluation window, and dashboard widgets to match your service baseline after the first few deploys.
How do I clean it up?
Run pulumi destroy from the same stack, then remove any email subscription confirmation or notification channel that your cloud provider leaves pending outside Pulumi state.