[azure_gateway_otel] [kb-yaml-to-lens] Azure Application Gateway Logs OpenTelemetry Assets - kb-yaml-to-lens

[mykola-elastic]

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

• Update JSON dashboards - fix adHocDataViews - after the PR is approved

How to test this PR locally

Related issues

• Counterpart PR using dashboards as code [azure_gateway_otel] [dashboard as code] Azure Application Gateway Logs OpenTelemetry Assets - Dashboard as code #19011

Screenshots

Overview

WAF

Backend health

[github-actions]

Vale Linting Results

Summary: 1 warning, 4 suggestions found

⚠️ Warnings (1)

File	Line	Rule	Message
packages/azure_gateway_otel/docs/README.md	27	Elastic.DirectionalLanguage	Don't use directional language. Use 'in the preceding section' instead of 'listed above'.

💡 Suggestions (4)

File	Line	Rule	Message
packages/azure_gateway_otel/docs/README.md	11	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
packages/azure_gateway_otel/docs/README.md	21	Elastic.Semicolons	Use semicolons judiciously.
packages/azure_gateway_otel/docs/README.md	23	Elastic.Semicolons	Use semicolons judiciously.
packages/azure_gateway_otel/docs/README.md	35	Elastic.Semicolons	Use semicolons judiciously.

---

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: be75362

Failed CI Steps

• ✅ Check go sources

History

• 💔 Build #42872 failed 14224ae
• 💔 Build #42870 failed b00128d
• 💔 Build #42867 failed 20ae7e7

cc @mykola-elastic

[github-actions]

TL;DR

Buildkite failed in Check go sources because a new package (packages/azure_gateway_otel) is missing a matching owner entry in .github/CODEOWNERS. Add a CODEOWNERS rule for this package and rerun CI.

Remediation

• Add a package-level owner mapping in .github/CODEOWNERS, e.g. /packages/azure_gateway_otel @elastic/obs-infraobs-integrations`` (consistent with manifest.yml owner and nearby Azure OTel package ownership).
• Re-run .buildkite/scripts/check_sources.sh (or full Buildkite) to confirm github.com/elastic/integrations/dev/codeowners.Check passes.

Investigation details

Root Cause

dev/codeowners.Check validates that each package has an explicit owner entry in .github/CODEOWNERS. The new package packages/azure_gateway_otel exists in the failing commit (be75362daf8d0525904ea1499167e3be16070fa9), but there is no corresponding /packages/azure_gateway_otel ... rule in CODEOWNERS.

Relevant evidence in repo state:

• .github/CODEOWNERS:116 has /packages/azure_activity_otel ... and many Azure package entries, but no /packages/azure_gateway_otel entry in that section.
• packages/azure_gateway_otel/manifest.yml exists at the failing commit and declares:
  • owner.github: elastic/obs-infraobs-integrations

Evidence

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

Running dependency: github.com/elastic/integrations/dev/codeowners.Check
Error: error validating packages in directory 'packages': error checking manifest 'packages/azure_gateway_otel': there is no owner for "packages/azure_gateway_otel" in ".github/CODEOWNERS"

Verification

• Not run locally (workspace is not checked out to PR head commit); analysis is based on Buildkite logs + repository content at commit be75362daf8d0525904ea1499167e3be16070fa9.

Follow-up

After adding the CODEOWNERS entry, if the check still fails, verify there are no trailing spaces or pattern typos in the new CODEOWNERS line.

Note

🔒 Integrity filter blocked 5 items

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

• #19010 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [azure_gateway_otel] [kb-yaml-to-lens] Azure Application Gateway Logs OpenTelemetry Assets - kb-yaml-to-lens #19010 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19010 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19011 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #11933 search_pull_requests: 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.

[mykola-elastic]

/test