github.com/elastic/beats/v7/x-pack/metricbeat/tests/integration TestMetricbeatOTelE2E

[v1v]

Flaky Test

• Test Name: TestMetricbeatOTelE2E
• Scope: github.com/elastic/beats/v7/x-pack/metricbeat/tests/integration
• File: N/A
• Location: N/A
• Buildkite Link: https://buildkite.com/organizations/elastic/analytics/suites/beats/tests/e1031fe7-bff1-86e8-9217-b9523a8925a6
• Flaky Instances: 1
• Latest Occurrence: 2026-03-31T11:57:52.356Z

Details

{
  "id": "e1031fe7-bff1-86e8-9217-b9523a8925a6",
  "web_url": "https://buildkite.com/organizations/elastic/analytics/suites/beats/tests/e1031fe7-bff1-86e8-9217-b9523a8925a6",
  "scope": "github.com/elastic/beats/v7/x-pack/metricbeat/tests/integration",
  "name": "TestMetricbeatOTelE2E",
  "location": null,
  "file_name": null,
  "instances": 1,
  "latest_occurrence_at": "2026-03-31T11:57:52.356Z",
  "most_recent_instance_at": "2026-03-31T11:57:52.356Z",
  "last_resolved_at": null,
  "ownership_team_ids": [],
  "failure_examples": []
}

[github-actions]

tl;dr: This looks like an auto-generated flaky-test signal, not a clear oblt-actions defect; the best next step is to route/track it in elastic/beats and only change this action if you want better metadata rendering (null → N/A) or owner mapping.

Recommendation

Keep issue #868 as a tracking signal and investigate the flaky test in elastic/beats first.

In oblt-actions, only consider follow-up changes if desired:

1. normalize location: null to N/A in issue text, and
2. add explicit scope→owner routing (currently absent).

Findings

• Issue creation/update is driven by buildkite/flaky-report/buildkite_flaky_report.py.
• Title and dedupe are based on scope + test_name:
  • buildkite/flaky-report/buildkite_flaky_report.py:150-155
  • buildkite/flaky-report/buildkite_flaky_report.py:197-205
• Existing-open issue => comment; closed/missing => new issue:
  • buildkite/flaky-report/buildkite_flaky_report.py:264-281
• No owner/team mapping logic in action code (no usage of ownership_team_ids or file_name in main script).
• location extraction currently keeps None when key exists with null value:
  • buildkite/flaky-report/buildkite_flaky_report.py:157-164
• Test workflow confirms this action is intended to auto-create flaky issues with label/prefix:
  • .github/workflows/test-buildkite-flaky-report.yml:49-51

Related precedent in beats:

• elastic/beats#45631 tracked similar Metricbeat OTel flaky behavior and was closed after fixes.

Verification

I ran local checks in this workspace:

$ python - <<'PY'
import importlib.util
p='buildkite/flaky-report/buildkite_flaky_report.py'
s=importlib.util.spec_from_file_location('b',p)
m=importlib.util.module_from_spec(s); s.loader.exec_module(m)
print(m.GitHubIssueManager._extract_test_info({'name':'T','scope':'S','location':None,'web_url':'u'}))
PY
('T', 'S', None, 'u')

$ rg -n "file_name|ownership_team_ids" buildkite/flaky-report/buildkite_flaky_report.py
No matches found.

(Unable to run full pytest suite directly here without extra environment setup; triage conclusions above are based on direct code-path inspection and command output.)

Detailed Action Plan

1. Confirm whether this flaky signal reproduces in elastic/beats CI for TestMetricbeatOTelE2E and collect latest failing logs from Buildkite suite URL in the issue body.
2. In beats, inspect x-pack/metricbeat/tests/integration OTel E2E test setup for race/timing/environmental instability.
3. If you want better auto-generated issue readability in oblt-actions, patch:
   • buildkite/flaky-report/buildkite_flaky_report.py:157-164
   • use test_data.get("location") or DEFAULT_NA (and optionally include file_name in fields).
4. If routing is desired, add explicit scope→team mapping input/logic in:
   • buildkite/flaky-report/action.yml
   • buildkite/flaky-report/buildkite_flaky_report.py
   • and tests in buildkite/flaky-report/buildkite_flaky_report_tests.py.
5. Keep dedupe behavior as-is unless there is evidence of duplicate spam; current logic already comments on open matches and recreates only after closure.

Related Items

Type	Link / File	Relevance
Issue	#868	Current auto-generated flaky report
Issue	elastic/beats#45631	Similar Metricbeat OTel flaky issue precedent
File	buildkite/flaky-report/buildkite_flaky_report.py:150-155	Issue title format (scope test)
File	buildkite/flaky-report/buildkite_flaky_report.py:197-205	Existing issue lookup logic
File	buildkite/flaky-report/buildkite_flaky_report.py:264-281	Create-vs-comment behavior
File	buildkite/flaky-report/buildkite_flaky_report.py:157-164	Null handling for location
File	.github/workflows/test-buildkite-flaky-report.yml:49-51	Expected flaky label/prefix behavior

Note

🔒 Integrity filtering filtered 43 items

Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.

• issue:github.com/elastic/beats/v7/x-pack/metricbeat/tests/integration TestMetricbeatOTelE2E #868 (issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:elastic/oblt-actions#unknown (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:github.com/elastic/beats/v7/x-pack/metricbeat/tests/integration TestMetricbeatOTelE2E #868 (list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:filebeat.tests.system.test_registrar.Test test_rotating_file #867 (list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:[FLAKY TEST] github.com/elastic/beats/v7/x-pack/metricbeat/module/cockroachdb/status TestFetch #866 (list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:[aw] Agent Suggestions failed #856 (list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:[oblt-aw][autodoc] Fix actionable documentation errors in action READMEs #533 (list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:[aw] No-Op Runs #528 (list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:[oblt-aw] Control Plane Dashboard #526 (list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• issue:v2 #126 (list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• #49827 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• #49042 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• #17965 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• #47528 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• #26727 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• #47193 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
• ... and 27 more items

---

What is this? | From workflow: Observability Agentic Workflow Entrypoint

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