What is logging-metrics-correlation?

A set of rules for recording AWS Lambda metrics and carrying a request ID through services such as SQS, SNS, DynamoDB, and HTTP. It also includes example CloudWatch Logs Insights queries for following one request.

Use it to add custom CloudWatch metrics, attach useful filtering dimensions, pass correlation IDs between services, and search all related log entries.

It helps connect logs, metrics, and traces that belong to the same request. This makes it easier to investigate failures and measure business events in serverless applications.

logging-metrics-correlation — Cursor rule by GoranErhartic

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/logging-metrics-correlation

Clone the repo

git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 377 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.

Model	Per session	Once invoked
Fable 5	$0.00022	$0.00377
Opus 5	$0.00011	$0.00188
Sonnet 5	$0.00004	$0.00075
Haiku 4.5	$0.00002	$0.00038

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

Security

Grade A, and why

logging-metrics-correlation 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 3d 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/logging-metrics-correlation.mdc · 34 lines

What it actually says

Lambda Metrics & Correlation ID

Metrics (Powertools)

Setup: new Metrics({ serviceName, namespace, defaultDimensions: { environment } }); singleton
Publish: metrics.addMetric(name, unit, value); metrics.addDimension(key, value) for filtering; flush automatically at handler end (or manual)
Units: Use MetricUnit.Count, Milliseconds, etc.; custom metrics for business events (e.g. ListingCreated, OrderProcessed)
Dimensions: Add dimensions (e.g. listingType, status) for filtering in CloudWatch; avoid high cardinality (e.g. user id) unless needed

Correlation ID

Propagation: Extract from API Gateway request header, SQS message envelope, or SNS message attributes; set on logger (e.g. logger.appendKeys({ correlationId })); pass to downstream (HTTP header, SNS/SQS attributes)
Logs: Include correlationId in every log line (Powertools Logger with appendKeys or injectLambdaContext)
X-Ray: Add correlationId as annotation on segment/subsegment for trace correlation

Log Insights

Query by correlationId: fields @message, @timestamp | filter correlationId = "value" | sort @timestamp
Combine with trace ID for full request flow across Lambdas

Conventions

One correlationId per request/message; propagate to all Lambdas and logs; record key business metrics with dimensions

Anti-Patterns

No correlationId propagation; high-cardinality dimensions; missing metrics for critical paths

See also: logging-setup.mdc, logging-tracing.mdc, sqs-processing.mdc

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.

3d ago First seen · 34 lines · 22 tokens per session scan A 46d283336780

Subscribe to this mod's changes

logging-metrics-correlation is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 377 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.

Analytics and metrics Cloud DevOps and cloud

aws-ecs

Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.

sanjeed5/awesome-cursor-rules-mdc · 2,640 tokens

redteam-compute

Compute security sub-agent for an Azure red team engagement. Covers VMs, VMSS, App Service, and Functions. Finds disk encryption gaps, exposed managed identities, plaintext secrets, runCommand exposure, FTP/remote-debug, and missing auth. Containers and Kubernetes (AKS, ACR, Container Apps/Instances) are owned by the…

Contoso-State/red-team-agent-orchestration · 85 tokens

logging-metrics-correlation