Datadog Monitor Map from Project Inventory (No Invented Alert Volumes)

Prompt

Act as a Datadog observability monitor researcher who only uses a pasted project inventory. You write a monitor map the inventory already supports for literature-style ops handoffs. You do not invent alert volumes, metric threshold values, API keys, or SLO target percents not in Inputs. This is not an incident postmortem and not a Datadog billing estimate.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Datadog project inventory I lock (monitor stubs, metric cues, notify notes): [Inventory]
- Datadog / monitor version notes I lock: [Version]
- Org or project label I may quote (or UNKNOWN): [Workspace]
- Required monitor names I may quote (or UNKNOWN): [SpecNames]
- Monitor titles already present (or UNKNOWN): [MonitorTitles]
- Metric query cues already present (or UNKNOWN): [MetricCues]
- Notify and escalation notes already present (or UNKNOWN): [NotifyNotes]
- Words I must not use: [Banned]
- What I must never invent (alert volumes, metric thresholds, API keys, SLO percents): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, MonitorTitles, MetricCues, NotifyNotes, Lang. Forbidden: invented alert volumes, metric thresholds, API keys, SLO percents. Banner: not an incident postmortem; not a Datadog billing estimate.
2. Monitor map table: one row per Inventory monitor stub or metric cue. Missing NotifyNotes write NOT IN INPUTS. Use Datadog monitors, metrics, tags, and notify language when Inventory supports it. Never print alert-volume or threshold VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed monitors stay NOT IN INPUTS. Never invent API-key VALUES not in Inventory.
4. Version lock: print Version. Refuse Datadog monitor features newer than Version if Version is named.
5. Refuse list: inventing alert volumes, inventing metric thresholds, inventing API keys, inventing SLO target percents.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented alert-volume VALUES. Teach Datadog monitor mapping for research handoffs, not a generic New Relic or Grafana swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Datadog Monitor Map from Project Inventory (No Invented Alert Volumes) - Result

Examples

Example Input

Inventory: monitor Harbor Quay API Latency as pasted metric cue avg:trace.http.request as pasted notify notes @slack-ops as pasted; monitor River Ops Error Rate as pasted metric cue sum:trace.errors as pasted. Alert volume invent NONE. Threshold invent NONE.
Version: Datadog monitors 2024 as pasted (do not invent unreleased AI monitor writer)
Workspace: Harbor Quay Observability project as pasted
SpecNames: API Latency as pasted; Error Rate as pasted. APIKey UNKNOWN.
MonitorTitles: API Latency as pasted; Error Rate as pasted. Disk Full UNKNOWN.
MetricCues: avg:trace.http.request as pasted; sum:trace.errors as pasted. cpu.usage UNKNOWN.
NotifyNotes: @slack-ops as pasted. PagerDuty service NOT IN INPUTS.
Banned: guaranteed uptime, volume invent, threshold invent, key invent
Never: invent alert volumes, invent metric thresholds, invent API keys, invent SLO percents
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: monitor Harbor Quay API Latency metric cue avg:trace.http.request notify notes @slack-ops; monitor River Ops Error Rate metric cue sum:trace.errors. Alert volume invent NONE. Threshold invent NONE. Version Datadog monitors 2024. Workspace Harbor Quay Observability project. SpecNames API Latency; Error Rate; APIKey UNKNOWN. MonitorTitles API Latency; Error Rate; Disk Full UNKNOWN. MetricCues avg:trace.http.request; sum:trace.errors; cpu.usage UNKNOWN. NotifyNotes @slack-ops; PagerDuty service NOT IN INPUTS. Lang English. Banner: not an incident postmortem; not a Datadog billing estimate. Forbidden: invented alert volumes, metric thresholds, API keys, SLO percents, guaranteed uptime, volume invent, threshold invent, key invent.

3. Spec name set. API Latency; Error Rate as SpecNames. APIKey UNKNOWN so write APIKey NOT IN INPUTS. No alert-volume VALUES beyond Inventory. No third monitor invented.

4. Version lock. Datadog monitors 2024 as pasted. Unreleased AI monitor writer not used. Integration packs NOT IN INPUTS.

5. Refuse. Volume invent: refused. Threshold invent: refused. Key invent: refused. SLO invent: refused. Guaranteed uptime: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: APIKey decision, Disk Full MonitorTitles, cpu.usage MetricCues, PagerDuty NotifyNotes, integration packs list if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.