feat(descriptions): AWS Lambda function descriptions

[pabloDeputter]

Description

Describes HTTP-triggered function.aws spans by the function and the route:
{{faas.name}} {{http.request.method}} {{http.route}}, e.g. checkout GET /orders/{id}. function.azure keeps its previous template as a separate description.

Why

Previously, the description was the function name, the same as the span name, so every HTTP route showed as function.aws checkout in the trace waterfall.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-conventions	Ready	Preview	Oct 14, 2026 3:09pm UTC

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• (attributes) Add http.request.duration by loewenheim in #697

• (descriptions) AWS Lambda function descriptions by pabloDeputter in #720

Bug Fixes 🐛

• (attributes) Apply consistent scrubbing across deprecations by mjq in #692

Internal Changes 🔧

• (repo) Update CODEOWNERS to include @giortzisg by Lms24 in #708

---

_{🤖 This preview updates automatically when you update the PR.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8032d1a. Configure here.}

[cursor]

Missing AWS description fallback templates

Medium Severity

The new function.aws description requires http.request.method and http.route with no fallback. A template only applies when every referenced attribute is present, so non-HTTP Lambda invocations no longer receive a description. The function.gcp rules in the same file fall back to faas.name.

 

^{Reviewed by Cursor Bugbot for commit 8032d1a. Configure here.}