Skip to content

[docs-patrol] Document BEATS_OTEL_TRACES_DISABLE in Filebeat CEL tracing docs #49782

@github-actions

Description

@github-actions

Recent code changes introduced documentation drift.

Changes Requiring Documentation Updates

1. CEL tracing disable override env var is implemented but not documented in reference docs

Commit(s):

  • fb0542f (https://github.com/elastic/beats/commit/fb0542fabb73d5e0445295df5deb3da41f4a6467)

What changed:

  • CEL tracing support was added.
  • A non-standard override env var was added to disable tracing export per input: BEATS_OTEL_TRACES_DISABLE="cel".
  • Code evidence:
    • x-pack/filebeat/input/cel/doc.go (lines ~146-149) documents this env var in package docs.
    • x-pack/filebeat/otel/trace.go (lines ~127-143) implements parsing of BEATS_OTEL_TRACES_DISABLE.

Documentation impact:

  • docs/reference/filebeat/filebeat-input-cel.md currently says tracing is activated using OTel-standard env vars and does not mention BEATS_OTEL_TRACES_DISABLE.
  • docs/reference/filebeat/ contains no mention of BEATS_OTEL_TRACES_DISABLE.
  • This can mislead operators because the override is a public, user-actionable control that changes behavior.

Suggested Actions

  • Update docs/reference/filebeat/filebeat-input-cel.md to document BEATS_OTEL_TRACES_DISABLE and accepted values (CSV input names such as cel, httpjson).
  • Clarify precedence/interaction with OTEL_TRACES_EXPORTER and other OTel env vars.
  • Add at least one short example showing disabling CEL trace export with the env var.

Note

🔒 Integrity filtering filtered 163 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.

  • #44889 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #48846 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #23575 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #12798 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • issue:#unknown (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • resource:search_pull_requests (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49778 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49777 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49772 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49770 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49769 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49768 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49764 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49763 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49762 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49761 (list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • ... and 147 more items

What is this? | From workflow: Docs Patrol

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

  • expires on Apr 6, 2026, 2:48 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs_teamIndicates that the issue/PR needs a Team:* label

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions