changelog: security_detection_engine 8.19.33-beta.1 (backport sync from PR #21283)

[github-actions]

Automated changelog sync from backport PR #21283.

Generated by the sync-backport-changelog workflow.

[infra-vault-gh-plugin-prod]

💔 Build Failed

• Buildkite Build
• Commit: 9ba1339

Failed CI Steps

• :elastic-cloud:📊 [security_detection_engine] Test for OOM issues against 9.6.0-SNAPSHOT ECH

History

[github-actions]

TL;DR

The failing Buildkite step is an external FTR OOM test failure (502 Bad Gateway) during prebuilt-rule package install, not a failure introduced by this PR's changelog-only change. Immediate action: re-run the failed OOM test step; if it reproduces, investigate Kibana/EPR availability in that test environment.

Remediation

• Re-run :test_tube: Run FTR OOM tests for build https://buildkite.com/elastic/integrations/builds/49766.
• If the rerun fails again with 502, collect the corresponding Kibana server logs around the failing request in install_prebuilt_rules.ts:133 and validate connectivity/health to the test EPR endpoint ((bkstatefulftr2582epr5e34ee15d688.eproom.estc.dev/redacted)).

Investigation details

Root Cause

The failure is a runtime HTTP gateway error from the downstream FTR test environment, not a repository code regression in this PR.

• Failed assertion from logs:
  • expected 200 "OK", got 502 "Bad Gateway"
  • at x-pack/solutions/security/test/security_solution_api_integration/test_suites/detections_response/rules_management/prebuilt_rules/oom_testing/install_prebuilt_rules/install_prebuilt_rules.ts:133:10
• PR changelog: security_detection_engine 8.19.33-beta.1 (backport sync from PR #21283) #21287 changes only packages/security_detection_engine/changelog.yml (version entry sync), with no executable code/test logic changes.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/49766
• Job/step: :test_tube: Run FTR OOM tests (package version: 9.5.5, EPR: (bkstatefulftr2582epr5e34ee15d688.eproom.estc.dev/redacted))
• Key log excerpt:
  • Error: expected 200 "OK", got 502 "Bad Gateway"
  • ...install_prebuilt_rules.ts:133:10

Verification

• Not run locally (failure occurs in external Buildkite FTR/Kibana OOM environment and is not reproducible from this repo checkout alone).

Follow-up

If this repeats across retries, treat as environment/config instability (Kibana/EPR/proxy under OOM constraints) and escalate with Kibana/FTR environment logs from the failing run.

---

What is this? | From workflow: PR Buildkite Detective

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

[shashank-elastic]

Updating as part of #21304