Skip to content

Conversation

@gogodjzhu
Copy link

Type of change:

  • Enhancement

Proposed commit message

Just add two Kafka output configurations to control bulk behavior.

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
    • no need, just leave it empty to use default
  • I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
    • no need, just add a configuration for third party kafka sdk (sarama)
  • I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

NO disruption by default.

Related issues

@gogodjzhu gogodjzhu requested review from a team as code owners January 22, 2026 10:07
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 22, 2026
@cla-checker-service
Copy link

cla-checker-service bot commented Jan 22, 2026

💚 CLA has been signed

@github-actions
Copy link
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify
Copy link
Contributor

mergify bot commented Jan 22, 2026

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @gogodjzhu? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 22, 2026

@gogodjzhu gogodjzhu force-pushed the feat/support_kafka_bulk_config branch from f5fa3ed to adea5b0 Compare January 22, 2026 10:21
@pierrehilbert pierrehilbert added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Jan 22, 2026
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 22, 2026
@elasticmachine
Copy link
Contributor

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

@pierrehilbert pierrehilbert requested review from faec and khushijain21 and removed request for andrzej-stencel January 22, 2026 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

Kafka Output Bulk Flush Configuration Enhancement

3 participants