monitoring

A set of AWS CloudWatch monitoring rules for watching Lambda functions, SQS queues, and DynamoDB, with SNS notifications and optional dashboards. CloudWatch is AWS's service for collecting metrics and raising alerts.

In plain words
What is it for?
Use it to define monitoring alarms and notifications in AWS CDK, including alerts for Lambda errors and duration, SQS queue depth, and DynamoDB throttling.
Why use it?
It helps you notice function failures, throttling, slow execution, and growing queues before they become harder to diagnose.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/goranerhartic/cursor-development-rules/monitoring
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,131 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.01131
Opus 5 $0.00012 $0.00566
Sonnet 5 $0.00005 $0.00226
Haiku 4.5 $0.00002 $0.00113

Measured 2d ago against content hash d1e093438762, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

monitoring scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/languages/aws-lambda/monitoring.mdc · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CloudWatch Monitoring

Overview

Add CloudWatch Alarms for Lambda errors, throttles, duration, SQS queue depth, and DynamoDB throttles. Notify via SNS for critical failures. Use CDK to define alarms and optional dashboards.

Lambda Alarms

// cdk/lib/stacks/monitoring-stack.ts

import { Stack, StackProps, Duration } from "aws-cdk-lib";
import { Construct } from "constructs";
import {
  Alarm,
  ComparisonOperator,
  TreatMissingData,
  Stats,
} from "aws-cdk-lib/aws-cloudwatch";
import { SnsAction } from "aws-cdk-lib/aws-cloudwatch-actions";
import { Topic } from "aws-cdk-lib/aws-sns";
import { Function as LambdaFunction } from "aws-cdk-lib/aws-lambda";

interface MonitoringStackProps extends StackProps {
  lambdaFunctions: LambdaFunction[];
  alarmTopic?: Topic;
}

export class MonitoringStack extends Stack {
  constructor(scope: Construct, id: string, props: MonitoringStackProps) {
    super(scope, id, props);

    const alarmTopic =
      props.alarmTopic ??
      new Topic(this, "AlarmTopic", { displayName: "Real Estate Alarms" });

    for (const fn of props.lambdaFunctions) {
      new Alarm(this, `${fn.node.id}Errors`, {
        alarmName: `${fn.functionName}-errors`,
        metric: fn.metricErrors({ period: Duration.minutes(1) }),
        threshold: 5,
        evaluationPeriods: 1,
        comparisonOperator: ComparisonOperator.GREATER_THAN_THRESHOLD,
        treatMissingData: TreatMissingData.NOT_BREACHING,
      }).addAlarmAction(new SnsAction(alarmTopic));

      new Alarm(this, `${fn.node.id}Throttles`, {
        alarmName: `${fn.functionName}-throttles`,
        metric: fn.metricThrottles({ period: Duration.minutes(1) }),
        threshold: 1,
        evaluationPeriods: 1,
        comparisonOperator: ComparisonOperator.GREATER_THAN_THRESHOLD,
        treatMissingData: TreatMissingData.NOT_BREACHING,
      }).addAlarmAction(new SnsAction(alarmTopic));

      const timeoutMs = fn.timeout?.toMilliseconds() ?? 30000;
      new Alarm(this, `${fn.node.id}Duration`, {
        alarmName: `${fn.functionName}-duration`,
        metric: fn.metricDuration({ period: Duration.minutes(1), statistic: Stats.P99 }),
        threshold: timeoutMs * 0.8,
        evaluationPeriods: 2,
        comparisonOperator: ComparisonOperator.GREATER_THAN_THRESHOLD,
        treatMissingData: TreatMissingData.NOT_BREACHING,
      }).addAlarmAction(new SnsAction(alarmTopic));
    }
  }
}

Read the full file on GitHub · 144 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 144 lines · 24 tokens per session scan A d1e093438762

Subscribe to this mod's changes

monitoring is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 1,131 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.