Prompt
I'm building a service with staging and production and need separate monitors
Latest observation
Nov 13, 2026
OpenAI APIWeb search: off
A clean way to do this is to create separate monitors for staging and production, and make the environment explicit in both the monitor name and the scope/query.
Recommended setup
1) Use separate monitor names
Examples:
API latency - stagingAPI latency - production
This makes alerts and dashboards immediately understandable.
2) Scope each monitor to the right environment
How you do this depends on your observability tool, but the pattern is usually:
- Production monitor: query only prod hosts/services/tags
- Staging monitor: query only staging hosts/services/tags
For example, if your metrics include an env tag:
- production filter:
env:prod - staging filter:
env:staging
3) Use different alert thresholds if needed
Staging is often noisier and less stable, so you may want:
- more lenient thresholds
- lower notification priority
- alerts routed to a different channel
Example:
- production: page on-call
- staging: notify Slack only
4) Group by environment in dashboards
If you want one dashboard, show both environments separately:
- same chart
- split by
env - or two panels, one for staging and one for production
If you’re using Datadog
A common pattern is to create monitors with queries like:
- Production
avg(last_5m):avg:myapp.request.latency{env:prod} > 500
- Staging
avg(last_5m):avg:myapp.request.latency{env:staging} > 1000
Best practice
If staging and production are truly different operationally, keep:
- separate monitors
- separate alert routing
- separate runbooks if behavior differs
If you want, I can help you design the exact monitor structure for your stack, e.g. Datadog, Prometheus, CloudWatch, or Grafana.