Add input identification support to the shipper output#31942
Add input identification support to the shipper output#31942rdner merged 3 commits intoelastic:mainfrom
Conversation
So, we can send the real events to the shipper.
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
| return structpb.NewStructValue(s), nil | ||
| } | ||
|
|
||
| func toShipperEvent(e publisher.Event) (*sc.Event, error) { |
There was a problem hiding this comment.
Not for this review, but it would be interesting to benchmark the conversions to the shipper data types to see what the overhead is. This will be new overhead added to every event sent from every beat.
|
/test |
|
@Mergifyio update |
✅ Branch has been successfully updated |
So, we can send the real events to the shipper.
What does this PR do?
This implements the Input/Stream Identification in the new Shipper Pipeline proposal, so we can start sending events to the shipper server.
Checklist
- [ ] 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 an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues