[aws_lambda_otel] create new slo and alerts

[jakubgalecki0]

Proposed commit message

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 1 suggestion found

💡 Suggestions (1): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
packages/aws_lambda_otel/changelog.yml	1	Elastic.Versions	Use 'later versions' instead of 'newer versions' when referring to versions.

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: caab7dd

Failed CI Steps

• ✅ Check go sources
• 📜 Check changelog PR links

History

[elastic-vault-github-plugin-prod]

Changelog link mismatch — expected https://github.com/elastic/integrations/pull/19456 in the following file(s):

• packages/aws_lambda_otel/changelog.yml

Tip

If expected, add the changelog-link-check:skip label to skip this check. Or, if an issue link was intended, use .../issues/<n> instead.

View Buildkite build
@jakubgalecki0

[github-actions]

TL;DR

Two non-flaky CI checks failed due to package metadata mismatches in this PR: aws_lambda_otel is missing a CODEOWNERS mapping, and its changelog entry links to PR #1 instead of this PR (#19456).

Remediation

• Add a CODEOWNERS entry for the new package path so the manifest owner is mapped (for example: /packages/aws_lambda_otel @elastic/obs-infraobs-integrations``).
• Update packages/aws_lambda_otel/changelog.yml to use https://github.com/elastic/integrations/pull/19456 (or an .../issues/<n> link if that was intended).
• Re-run .buildkite/scripts/check_sources.sh and .buildkite/scripts/check_changelog_entries.sh.

Investigation details

Root Cause

1. Go source check failure (check_sources.sh)

   • Build log reports:
     error checking manifest 'packages/aws_lambda_otel': owner "elastic/obs-infraobs-integrations" defined in "packages/aws_lambda_otel/manifest.yml" is not in ".github/CODEOWNERS"
   • In PR content, packages/aws_lambda_otel/manifest.yml sets:
     • owner.github: elastic/obs-infraobs-integrations (around manifest.yml:29)
   • In repo /.github/CODEOWNERS, there is currently no aws_lambda_otel path entry.

2. Changelog check failure (check_changelog_entries.sh)

   • Build log reports expected link:
     https://github.com/elastic/integrations/pull/19456
   • PR content shows in packages/aws_lambda_otel/changelog.yml:
     • link: https://github.com/elastic/integrations/pull/1 (changelog.yml:5)

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/44311
• Failed jobs:
  • :white_check_mark: Check go sources
  • :scroll: Check changelog PR links
• Key log excerpts:
  • owner "elastic/obs-infraobs-integrations" ... is not in ".github/CODEOWNERS"
  • ERROR: unexpected link: 'https://github.com/elastic/integrations/pull/1' (expected .../pull/19456)

Verification

• Not run locally; analysis based on the Buildkite failure logs and PR file contents.

Follow-up

• After fixing the two metadata entries, a rebuild should clear both failures unless new checks fail downstream.

Note

🔒 Integrity filter blocked 2 items

The following items were blocked because they don't meet the GitHub integrity level.

• [aws_lambda_otel] create new slo and alerts #19456 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19456 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.