Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 5, 2025

Proposed commit message

This PR adds support for input.[input_type].pipelines parameter in beatreceivers. This can be set as custom YAML in integrations such as filestream-integration. This PR ensures we support this behavior in beat receivers

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

None

Author's Checklist

  • [ ]

How to test this PR locally

  1. Create two pipeline on elasticsearch. Can be done via Kibana's dev tools
PUT _ingest/pipeline/error_pipeline
{
  "description": "Add timestamp and remove unwanted fields",
  "processors": [
    {
      "set": {
        "field": "error_key",
        "value": "this is error value"
      }
    }
  ]
}
  1. Start filebeat otel with following config file
filebeat.inputs:
  - type: filestream
    id: filestream-input-id
    enabled: true
    file_identity.native: ~
    prospector.scanner.fingerprint.enabled: false    
    paths:
      - ./test.json

output:
  elasticsearch:
    hosts: ["http://localhost:9200"]
    username: admin
    password: testing

and you can observer the final events have an extra field error_key: error value

Related issues


This is an automatic backport of pull request #47265 done by [Mergify](https://mergify.com).

)

* Add support for pipelines in beatreceivers

(cherry picked from commit e0b9332)

# Conflicts:
#	x-pack/filebeat/tests/integration/otel_test.go
#	x-pack/libbeat/outputs/otelconsumer/otelconsumer.go
#	x-pack/metricbeat/tests/integration/otel_test.go
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Nov 5, 2025
@mergify mergify bot requested a review from a team as a code owner November 5, 2025 13:30
@mergify mergify bot requested review from VihasMakwana and orestisfl and removed request for a team November 5, 2025 13:30
@mergify
Copy link
Contributor Author

mergify bot commented Nov 5, 2025

Cherry-pick of e0b9332 has failed:

On branch mergify/bp/8.19/pr-47265
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit e0b93322d.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   libbeat/otelbeat/beatconverter/beatconverter_test.go
	modified:   libbeat/otelbeat/oteltranslate/outputs/elasticsearch/config_otel.go
	modified:   libbeat/otelbeat/oteltranslate/outputs/elasticsearch/config_otel_test.go
	modified:   x-pack/libbeat/outputs/otelconsumer/otelconsumer_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   x-pack/filebeat/tests/integration/otel_test.go
	both modified:   x-pack/libbeat/outputs/otelconsumer/otelconsumer.go
	both modified:   x-pack/metricbeat/tests/integration/otel_test.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 5, 2025
@github-actions github-actions bot added Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team skip-changelog labels Nov 5, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Nov 5, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@khushijain21 khushijain21 enabled auto-merge (squash) November 6, 2025 06:39
@khushijain21
Copy link
Contributor

Requires #47412

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport conflicts There is a conflict in the backported pull request skip-changelog Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants