otel(packetbeat): add OTel status reporting and integration tests#51428
Conversation
Thread the OTel status factory wrapper so the receiver can report per-input StatusOK events to the OTel host. Add SetStatusReporter to processor so the wrapper can inject a sub-reporter after runner creation. Also add integration test coverage for the packetbeat OTel receiver: - Rewrite pbreceiver unit tests to replay pre-recorded pcap files (no root/npcap required); add MockHost event history so TestReceiverStatus can verify StatusOK was reported even when the pcap finishes fast - Add docker-compose.yml, GoIntegTest mage target, and CI pipeline step - Add tests/integration/otel_test.go with pcap-based E2E tests (single receiver, multiple receivers, standalone-vs-receiver ES comparison) and explicit live-interface tests that skip without root
🤖 GitHub commentsJust comment with:
|
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThe PR wires OTel status reporting through the Packetbeat beater layer: 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Caution Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted. Error details |
|
@elastic/sec-linux-platform Can I get a review from your team? Thanks. |
nicholasberlin
left a comment
There was a problem hiding this comment.
LGTM (and the bot)
|
@leehinman Could you take a look when you have a chance? Thanks! |
Proposed commit message
Thread the OTel status factory wrapper so the receiver can report per-input StatusOK events to the OTel host. Add SetStatusReporter to processor so the wrapper can inject a sub-reporter after runner creation.
Also add integration test coverage for the packetbeat OTel receiver:
Rewrite pbreceiver unit tests to replay pre-recorded pcap files (no root/npcap required); add MockHost event history so TestReceiverStatus can verify StatusOK was reported even when the pcap finishes fast
Add docker-compose.yml, GoIntegTest mage target, and CI pipeline step
Add tests/integration/otel_test.go with pcap-based E2E tests (single receiver, multiple receivers, standalone-vs-receiver ES comparison) and explicit live-interface tests that skip without root
Checklist
stresstest.shscript to run them under stress conditions and race detector to verify their stability../changelog/fragmentsusing the changelog tool.How to test this PR locally
Related issues