[aws_ec2_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_ec2_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: 1cb97b2

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/19459 in the following file(s):

• packages/aws_ec2_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

The Buildkite failures are caused by package metadata mismatches, not test/runtime code: aws_ec2_otel is missing from .github/CODEOWNERS, and its changelog entry links to PR #1 instead of this PR. Updating those two files should unblock CI.

Remediation

• Add a CODEOWNERS entry for the new package (for example: /packages/aws_ec2_otel @elastic/obs-infraobs-integrations``) or change packages/aws_ec2_otel/manifest.yml owner to a team already mapped in `.github/CODEOWNERS`.
• Update packages/aws_ec2_otel/changelog.yml to use https://github.com/elastic/integrations/pull/19459 (or an issue URL if that was intended).
• Re-run the Buildkite checks Check go sources and Check changelog PR links.

Investigation details

Root Cause

1. Configuration mismatch (CODEOWNERS validation)
   packages/aws_ec2_otel/manifest.yml declares:

   • owner.github: elastic/obs-infraobs-integrations (line 29)

   The failing check reports this owner is not mapped for this package in .github/CODEOWNERS:

   • error checking manifest 'packages/aws_ec2_otel': owner "elastic/obs-infraobs-integrations" ... is not in ".github/CODEOWNERS"

   This indicates the new package path is missing from CODEOWNERS.

2. Changelog PR link mismatch
   packages/aws_ec2_otel/changelog.yml contains:

   • link: https://github.com/elastic/integrations/pull/1 (line 6)

   CI expects links in modified changelog entries to match this PR:

   • expected https://github.com/elastic/integrations/pull/19459

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/44315
• Jobs/steps:
  • :white_check_mark: Check go sources (.buildkite/scripts/check_sources.sh)
  • :scroll: Check changelog PR links (.buildkite/scripts/check_changelog_entries.sh)
• Key log excerpts:

Error: error validating packages in directory 'packages': error checking manifest 'packages/aws_ec2_otel': owner "elastic/obs-infraobs-integrations" defined in "packages/aws_ec2_otel/manifest.yml" is not in ".github/CODEOWNERS"

ERROR: unexpected link: 'https://github.com/elastic/integrations/pull/1'
       expected:         'https://github.com/elastic/integrations/pull/19459'

Verification

• Not run in this detective workflow (read-only analysis from Buildkite logs + repository contents at commit 1cb97b27a98cfeb98941fec7c56d8cabeb623551).

Follow-up

• If you intentionally want a non-PR changelog link, switch it to an issue URL (.../issues/<n>) as suggested by the CI output.

Note

🔒 Integrity filter blocked 3 items

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

• [aws_ec2_otel] create new slo and alerts #19459 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19459 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19459 search_issues: 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.