fix: updated kibana version & enable_request_tracer default set to false

[Bharatkk-metron]

Change Type

• Bug

Proposed commit message

In Ref to : #19246

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

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

[infra-vault-gh-plugin-prod]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[efd6]

/test

[github-actions]

TL;DR

Buildkite failed in Check integrations doppel because package lint could not find a changelog entry for the current manifest version. The immediate fix is to reorder packages/doppel/changelog.yml so the newest version (0.1.1) is first.

Remediation

• Move the 0.1.1 block above 0.1.0 in packages/doppel/changelog.yml (this repo expects newest versions at the top).
• Re-run package lint for doppel (or rerun the Buildkite job) after reordering.

Investigation details

Root Cause

This is a configuration/metadata failure in package changelog ordering, not a code runtime failure.

• packages/doppel/manifest.yml:4 sets version: 0.1.1.
• packages/doppel/changelog.yml:1 starts with 0.1.0, and 0.1.1 appears later at packages/doppel/changelog.yml:6.
• In this repository, changelogs are expected with newer versions first (see header convention in other packages: # newer versions go on top).

With 0.1.1 not first, lint reports that the current manifest version has no matching changelog entry.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/43723
• Job/step: Check integrations doppel (.buildkite/scripts/test_one_package.sh packages/doppel origin/main 2e385ea20b28aed81b362a4f3d234ec240708572)
• Key log excerpt:

  Error: checking package failed: linting package failed: found 1 validation error:
     1. current manifest version doesn't have changelog entry
  

Verification

• Not run locally end-to-end in this environment because the Buildkite helper script depends on CI-provided environment variables (YQ_VERSION).

Follow-up

If this still fails after reorder, check for formatting drift in changelog.yml (unexpected indentation or malformed YAML around the 0.1.1 entry).

Note

🔒 Integrity filter blocked 2 items

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

• fix: updated kibana version & enable_request_tracer default set to false #19251 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19251 pull_request_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]

New version at the top.

[Bharatkk-metron]

Moved the new version at top. Thank you!

[Bharatkk-metron]

@efd6 Could you please run test again? Thank you!

[efd6]

/test

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 7e83e2a

History

• 💔 Build #43723 failed 2e385ea

[elastic-vault-github-plugin-prod]

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

[Bharatkk-metron]

Hi @efd6 ,

Thank you so much for you help in getting this PR merged.

We've performed the sanity testing and now all app features and working as expected.

Could you please help us to resolve this issue #19227 and get the app ready for users in production?

Thanks!