Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT]: Support CloudEvents as a usage data format for ingestion #1986

Open
mostafa opened this issue May 3, 2024 · 2 comments
Open

[FEAT]: Support CloudEvents as a usage data format for ingestion #1986

mostafa opened this issue May 3, 2024 · 2 comments

Comments

@mostafa
Copy link

mostafa commented May 3, 2024

Is your feature request related to a problem? Please describe.

I would like to be able to send CloudEvents and possibly CDEvents to the events controller to update billable metrics.

Describe the solution you'd like

A simple solution is to accept CloudEvents (using the Ruby SDK) for usage data along with the current usage data format with the option to include the fields of the internal events in CloudEvents' data field, and possibly fully transition to CloudEvents at some point.

Describe alternatives you've considered

The current way is to convert CloudEvents to the usage data format before ingestion.

Additional context

OpenMeter already supports CloudEvents, but I prefer to see this feature in this product. Also, I'd be happy to implement it myself, with minimal guidance.

@jdenquin
Copy link
Contributor

jdenquin commented May 7, 2024

@michaelponrajah should we add it into our roadmap?

@jdenquin
Copy link
Contributor

👋 @mostafa Sorry for the delay, we've been pretty busy on a lot of topics and supporting CloudEvents was not in our roadmap.
If you still need it you can create a new controller where we support the format of CloudEvents spec and adapt it to our internal event system.

Happy to help on our Slack Community if you need me!

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

No branches or pull requests

2 participants