Skip to content

docs: add WASM filter emitter as the recommended approach for telemetry and billing attribution#177

Merged
JoseSzycho merged 3 commits into
feat/service-catalog-registration-designfrom
feat/wasm-metering-alternative
Jun 9, 2026
Merged

docs: add WASM filter emitter as the recommended approach for telemetry and billing attribution#177
JoseSzycho merged 3 commits into
feat/service-catalog-registration-designfrom
feat/wasm-metering-alternative

Conversation

@JoseSzycho

@JoseSzycho JoseSzycho commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

This PR adds a new alternative to the metering design document.

Related to:

@kevwilliams

Copy link
Copy Markdown

Very nice approach

@scotwells scotwells left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When we get to a scale that aggregation is necessary, we'll add aggregation as a platform capability in the pipeline instead of something that's envoy specific. There's a lot this proposal isn't considering around the durability needs of the pipeline when something goes wrong.

At the current scale, per-request events without aggregation will be just fine.

@JoseSzycho

Copy link
Copy Markdown
Contributor Author

@scotwells thanks for the review. I just updated the doc to leave the recommendation as it was before (Option A).

@JoseSzycho JoseSzycho requested a review from scotwells June 9, 2026 16:33
@JoseSzycho

Copy link
Copy Markdown
Contributor Author

@kevwilliams @scotwells just updated the doc that Option A with out aggregation would be fine as an initial implementation.

@JoseSzycho JoseSzycho merged commit 8b96dc4 into feat/service-catalog-registration-design Jun 9, 2026
10 checks passed
@JoseSzycho JoseSzycho deleted the feat/wasm-metering-alternative branch June 9, 2026 16:59
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.

3 participants