Promptz

Identifying metrics/alarms related to AWS Resources

This prompt aims to identify missing metrics/alarms related to AWS Resources in a target package. A reference package is used to limit the response to required metrics/alarms, assuming it follows best practices for the particular resource type setup.

#aws #monitoring #metrics #alarms #cloudwatch #best-practices
Created Mar 13, 2025 • Updated Mar 17, 2025 • by shudabas
Your task is to analyze the code for two services, {{Service1}} and {{Service2}}, and identify any CloudWatch metrics or alarms related specifically to {{ALARM_TYPE}} that are present in {{Service2}} but missing in {{Service1}}. To accomplish this task, follow these steps: 1. Review the code for {{Service2}}, which follows best practices for monitoring infrastructure using CloudWatch metrics and alarms. Take note of the metrics and alarms implemented specifically for {{ALARM_TYPE}}. 2. Carefully examine the code for {{Service1}}. 3. Compare the two code bases and identify any CloudWatch metrics and alarms specifically related to {{ALARM_TYPE}} that are implemented in {{Service2}} but not present in {{Service1}}. 4. Keep in mind that metric and alarm names may be slightly different between the two code packages, but focus on the underlying functionality and severity. 5. If {{Service1}} does not use {{ALARM_TYPE}}, do not list any missing metrics or alarms.

Provide your response in the following format: Provide a list of all metrics and alarms present in {{Service2}} related to {{ALARM_TYPE}}. Treat same alarms of different severity as different. Also mention why each metric and alarm is important. Provide a code reference of where each metric and alarm is present in {{Service2}} and where it can be added in {{Service1}}. <missing_alarms>

  • [First alarm or metric name], [Severity of the alarm in the form SEV_1/SEV_2/SEV_3. Use NA if not specified.], [Brief explanation about why this metric is important]
  • [Second alarm or metric name], [Severity of the alarm in the form SEV_1/SEV_2/SEV_3. Use NA if not specified.], [Brief explanation about why this metric is important] . . . </missing_alarms>

Please provide your response immediately after these instructions, enclosed in the and <missing_alarms></missing_alarms> tags. The code for {{Service2}} is presented below within <{{Service2}}></{{Service2}}> tags. The code for {{Service1}} is presented below within <{{Service1}}></{{Service1}}> tags.

Related Content

Identifying metrics/alarms related to service health

This prompt aims to identify missing metrics/alarms related to service health in a target package. A reference package is used to limit the response to required metrics/alarms, assuming it follows best practices for service health monitoring.

#aws #monitoring #service-health +3 more
by shudabas

Diagrama para draw.io

Permite crear diagramas para draw.io solo , renombrando la extensión del archivo generado a .drawio

#draw.io #diagrams #aws +2 more
by jorgels120878

Markdown Best Practices

I have noticed that the Claude model sometimes creates markdown files with linting issues, which prompted me to create these rules, extracted from the markdown-lint code on GitHub.

#markdown #linting #best-practices +2 more
by walmsles

Find Prompts, Rules & Agents

Search through our comprehensive library for Amazon Q Developer