Draft Monitors

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Overview

Draft Monitors let you safely create, refine, and test alerts without triggering notifications.

Whether you’re experimenting with thresholds, iterating on complex queries, or collaborating with teammates, drafts give you a clean, isolated space to work that is free from the noise of unfinished or test monitors. Also, Draft Monitors help reduce alert fatigue during development and ensure only fully vetted monitors go live.

Ideal for engineers and SREs managing alert workflows, Draft Monitors provide clarity across multiple teams and a sure path from idea to reliable alert.

Create a draft monitor

To create and store monitors in a draft state:

  1. Navigate to Monitors > New Monitor.
  2. Configure the monitor (add your query, specify conditions, and optionally set notifications). Notification handles set in a draft are only used after the monitor is published.
  3. Click Save as Draft. No alerts are sent from this draft monitor.
Save as Draft button in the monitor creation interface

Publish a draft monitor

When your monitor is ready:

  1. Open the draft from Monitors List by using the draft status facet or filter by status:draft.
  2. Review the configuration.
  3. Click Publish Monitor.
  4. This publishes your monitor and begins alerting based on your conditions.

Manage draft monitors

Find draft monitors from the Monitors List by using the draft status facet or filter by draft_status:draft. Drafts appear with a Draft label on the monitor status page and in the monitor list. Drafts expire after 6 months without updates, but you can delete draft monitors at any time.

Permissions

Anyone with edit permissions can update a draft monitor. You can use events to preview how often the monitor would have triggered without sending actual notifications.

Best practices

  • Use drafts for peer reviews: Collaborate before pushing changes live.
  • Avoid noise in production: Test alert conditions safely in a draft first.
  • Track your work: Use clear names and tags for drafts during development.
  • Limit stale drafts: Review and clean up old drafts to reduce clutter.

Further reading

PREVIEWING: patrickliang/add_double_dash_on_cluster_agent_commands