Skip to content

Conversation

@onewland
Copy link
Contributor

@onewland onewland commented Oct 27, 2025

I want to start emitting how many events by type are being processed by the EAP consumer. I'm dividing that up into 3 changes:

  1. (this change) change how we build BytesInsertBatch to support a builder pattern (so it's more simple to omit dataset-specific fields)
  2. start keeping track of how many items by type are being processed in the EAPItems processor: feat(eap): record item type counts in batches #7481
  3. emit the actual metric at the end of a batch write

@onewland onewland marked this pull request as ready for review November 19, 2025 18:12
@onewland onewland requested a review from a team as a code owner November 19, 2025 18:12
@onewland onewland merged commit 2724c04 into master Nov 19, 2025
34 of 35 checks passed
@onewland onewland deleted the ref/builder-pattern-for-bytes-insert-batch branch November 19, 2025 19:35
onewland added a commit that referenced this pull request Nov 25, 2025
Emit how many events by type are being processed by the EAP consumer.
This is being split into 3 changes:

- change how we build BytesInsertBatch to support a builder pattern (so
it's more simple to omit dataset-specific fields):
#7479 (merged)
- (this change) start keeping track of how many items by type are being
processed in the EAPItems processor
- emit the actual metric at the end of a batch write
onewland added a commit that referenced this pull request Dec 2, 2025
Emit how many events by type are being processed by the EAP consumer.
This is being split into 3 changes:

- change how we build BytesInsertBatch to support a builder pattern (so
it's more simple to omit dataset-specific fields):
#7479 (merged)
- start keeping track of how many items by type are being processed in
the EAPItems processor: #7481
- (this change) emit the actual metric at the end of a batch write
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants