[aws_ecs_otel] create new alert assets

[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)

No issues found on modified lines!

---

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.

[github-actions]

TL;DR

elastic-package lint failed before tests ran because the new packages/aws_ecs_otel package does not include the required docs/ directory. Add packages/aws_ecs_otel/docs/README.md for the new content package and rerun the package check.

Remediation

• Add packages/aws_ecs_otel/docs/README.md with a short overview of the AWS ECS OpenTelemetry assets, expected datasets (aws.ecs.otel), and setup/usage guidance, following the pattern used by other AWS OTel content packages such as packages/aws_cloudtrail_otel/docs/README.md.
• Validate with elastic-package lint from packages/aws_ecs_otel or rerun .buildkite/scripts/test_one_package.sh packages/aws_ecs_otel origin/main a78325e7f11be9b95c2723b1fb751401a2109ae3.

Investigation details

Root Cause

This is a package configuration/structure issue. The PR adds a new content package at packages/aws_ecs_otel/manifest.yml, but the package tree at commit a78325e7f11be9b95c2723b1fb751401a2109ae3 contains only LICENSE.txt, changelog.yml, img/, kibana/, and manifest.yml; there is no docs/ directory. Existing comparable OTel packages include docs/README.md, for example packages/aws_cloudtrail_otel/docs/README.md.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/44586
• Job/step: Check integrations aws_ecs_otel
• Command: .buildkite/scripts/test_one_package.sh packages/aws_ecs_otel origin/main a78325e7f11be9b95c2723b1fb751401a2109ae3
• Key log excerpt:

Lint the package
Error: checking package failed: linting package failed: found 1 validation error:

   1. expecting to find [docs] folder in folder [/opt/buildkite-agent/builds/.../elastic/integrations/packages/aws_ecs_otel]

Verification

• Not run locally: the workspace is not checked out to the PR package contents, so I verified the PR tree through repository contents and the Buildkite log instead.

---

What is this? | From workflow: PR Buildkite Detective

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

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 5c021db

History

• 💚 Build #44661 succeeded 08119bb
• 💔 Build #44649 failed 0e14b75
• 💔 Build #44586 failed a78325e

[elastic-vault-github-plugin-prod]

Package aws_ecs_otel - 0.2.0 containing this change is available at https://epr.elastic.co/package/aws_ecs_otel/0.2.0/