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

Billing RDS #554

Open
pierreozoux opened this issue Jan 7, 2019 · 1 comment
Open

Billing RDS #554

pierreozoux opened this issue Jan 7, 2019 · 1 comment

Comments

@pierreozoux
Copy link

I'm a multi-tenant openshift admin.
I'm working on figuring out the best way to provide RDS as a service for our users, and it will probably be with some kind of form of operators.

Then, the next natural question is how do I charge back my customers.

This is how I stumbled upon this project.

We already developed an internal tool for charge back. It is based on prometheus data.
Basically if I had an exporter that would tell me how many CRDs are there, on which namespace, and some details about it, I should be fine.

I'm investigating if the operator metering could help me. And is it made for my usage?

Thanks a lot for you insight!

@chancez
Copy link
Contributor

chancez commented Jan 7, 2019

That would definitely work well with the way metering currently works! You would end up creating a ReportPrometheusQuery CR which defines the Prometheus query to run periodically to import data, then you can define ReportGenerationQueries and Reports to further post-process it using SQL.

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