Identifying metrics/alarms related to service health

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.

{{Service1}} is the target package name, for which missing alarms and metrics need to be identified. {{Service2}} is the reference package name, which follows best practices for service health monitoring. {{ALARM_TYPE}} is the AWS resource type. E.g. File Descriptor, Garbage collection. The code for the reference and target packages need to be converted to a structured format and appended to the prompt.

Utility to convert code packages to a structured format: packages/GenAICDKAnalyzer/blobs/mainline/–/codebase_to_text.py Sample usage of the utility: packages/GenAICDKAnalyzer/blobs/6aec4cd1b96c975dff5f1a8950b1b0ab70be7399/–/main.py#L184