[aws_rds_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_rds_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: 27d6b21

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

• packages/aws_rds_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 CI checks failed due to package metadata/configuration, not test/runtime code: the new package is missing a CODEOWNERS entry and its changelog points to the wrong PR link. Update those two files and rerun CI.

Remediation

• Add a CODEOWNERS mapping for the new package path in .github/CODEOWNERS:
  • /packages/aws_rds_otel @elastic/obs-infraobs-integrations``
• Fix packages/aws_rds_otel/changelog.yml to reference this PR:
  • link: https://github.com/elastic/integrations/pull/19458
• Push the commit and rerun Buildkite; both failed checks should clear.

Investigation details

Root Cause

1. Check go sources failed because packages/aws_rds_otel/manifest.yml sets owner.github: elastic/obs-infraobs-integrations (line 30), but there is no /packages/aws_rds_otel entry in .github/CODEOWNERS.
2. Check changelog PR links failed because packages/aws_rds_otel/changelog.yml still contains a placeholder PR URL (.../pull/1) on line 5.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/44314
• Job/step: :white_check_mark: Check go sources
• Key log excerpt:

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

• Job/step: :scroll: Check changelog PR links
• Key log excerpt:

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

Verification

• Not run locally in this workflow; diagnosis is based on Buildkite logs and repository contents at commit 27d6b21fefdfacf0df563ca67ad0150a24c8cdb0.

Follow-up

• If the changelog URL intentionally points to an issue, use /issues/<n> format as suggested by the check.

Note

🔒 Integrity filter blocked 3 items

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

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