WorkflowFor DevelopersDevOps & CI/CD

Monitoring & Alerting Stack Setup.

When deploying a new application to production and needing visibility from day one.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1950 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
monitoring-alerting-stack-setup-4.md Β· 1950 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: DevOps & CI/CD
- Use case: Monitoring & Alerting Stack Setup
- Source task:
  - Design a monitoring and alerting stack for {{describe_application_language_deployment_platform_scale}}.
  - Step 1: Metrics: select the metrics stack (Prometheus + Grafana / Datadog / New Relic), define the top 10 metrics to instrument, and write example metric code in {{language}}.
  - Step 2: Logging: design structured logging format, log aggregation setup (ELK / Loki / CloudWatch), and define log retention policy.
  - Step 3: Alerting: write alerting rules for the 5 most critical conditions with severity levels and escalation paths.

# Goal
Metrics stack setup, 10 key metrics with instrumentation examples, logging design, and 5 alerting rules with escalation paths.

# Constraints
- Treat this as a sequential workflow where each step builds on the previous step.
- Keep every step clearly labeled and easy to run separately if needed.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Metrics stack setup, 10 key metrics with instrumentation examples, logging design, and 5 alerting rules with escalation paths.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}RoleSRE
{{use_case}}Your specific valuemonitoring & alerting stack setup
{{describe_application_language_deployment_platform_scale}}Describe application language deployment platform scalelanguage
{{language}}LanguagePython

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When deploying a new application to production and needing visibility from day one.

PRO TIP

Define your SLOs before writing alerts β€” alerts should fire when you are burning through error budget, not every time a metric wiggles.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’