[muskan-agarwal26]

Proposed commit message

• Updated changelog description as mentioned in the comment

[elastic-vault-github-plugin-prod]

Reviewers

Buildkite won't run for external contributors automatically; you need to add a comment:

• /test : will kick off a build in Buildkite.

NOTE: https://github.com/elastic/integrations/blob/main/.buildkite/pull-requests.json contains all those details.

[efd6]

    - description: Initial release.
      type: enhancement
      link: https://github.com/elastic/integrations/pull/16599
    - description: Add support for identity data stream.
      type: enhancement
      link: https://github.com/elastic/integrations/pull/16620

[efd6]

Thanks

[muskan-agarwal26]

@efd6 , could you please merge this PR as well.

[efd6]

/test

[github-actions]

TL;DR

The Check integrations axonius job failed, but the provided log excerpt only contains teardown/artifact-upload output and does not include the failing assertion. Based on current evidence, this looks like a transient system/infrastructure failure rather than a regression from this PR’s changelog-only change.

Remediation

• Re-run the failed Buildkite step (Check integrations axonius) to confirm whether this was transient.
• If it fails again, attach the failing JUnit artifact content (especially axonius-system-*.xml) or the full pre-teardown log segment so we can pinpoint the exact failing test/assertion.

Investigation details

Root Cause

No deterministic code-level root cause is visible in the available Buildkite log capture. The log starts at teardown and ends with generic exit status output, without the original error stack/assertion.

Also, the PR delta is changelog-only (packages/axonius/changelog.yml), and package validation succeeds locally for this branch/commit.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/42463
• Job/step: Check integrations axonius
• Key log excerpts:
  • /tmp/gh-aw/buildkite-logs/integrations-check-integrations-axonius.txt:73 → --- [axonius] failed
  • /tmp/gh-aw/buildkite-logs/integrations-check-integrations-axonius.txt:76-78 → generic exit only (Error: The command exited with status 1)
  • /tmp/gh-aw/buildkite-logs/integrations-check-integrations-axonius.txt:91-119 → artifacts uploaded after failure (including axonius-system-*.xml), but failing assertion text is not present in this log file.
• Code change inspected:
  • packages/axonius/changelog.yml:1-9 (only PR-modified file)

Verification

• Ran local package lint/build check for the PR branch via CI helper functions (use_elastic_package + check_package axonius): passed.
• Full Buildkite package test flow could not be faithfully replayed in this environment due missing Buildkite runtime env setup in the wrapper script (YQ_VERSION/pipeline env expectations).

Follow-up

If the retry still fails, we should classify based on the first failing assertion from axonius-system-*.xml (test bug vs infra). Right now, available evidence best fits infrastructure/transient or flaky system test.

Note

🔒 Integrity filter blocked 3 items

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

• [Axonius][identity] Update changelog description #18839 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #18839 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [Axonius][identity] Update changelog description #18839 issue_read: 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.

[efd6]

@muskan-agarwal26 This is failing due to a mismatched assert.hit_count. This suggest that the situation on feature/axonius-0.1.0 is incorrect. Can you look into that?

[muskan-agarwal26]

Thanks @efd6 , the failure was due to mismatched assert.hit_count in network, I have resolved it.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: dc1236d

History

• 💔 Build #42463 failed 46248b2
• 💔 Build #42458 failed 46248b2

[muskan-agarwal26]

@efd6 , could you please merge this now?