Add a Usage Reporting and Billing page#34254
Conversation
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
ptgott
added
backport/branch/v12
no-changelog
|
🤖 Vercel preview here: https://docs-33au27086-goteleport.vercel.app/docs/ver/preview |
|
I took a look per @zmb3 's request; no comments from my side. |
There was a problem hiding this comment.
This is only accurate for on-prem, since all Cloud versions of Teleport will send individual anonymized events when they happen rather than aggregating them in counts.
There was a problem hiding this comment.
How should this be corrected then?
There was a problem hiding this comment.
I'm not quite sure how we should word it - especially since usage events on Cloud are actually more extended than just the ones that we use for billing - but the gist is that in Cloud we keep an anonymized log of each individual "billing" event when it happens and then we count and sum over the billing period, whereas for on-prem (only Enterprise, currently) the Teleport cluster does a first aggregation step on a 15-min basis and we receive the pre-aggregated counts of events per user, which we then count or sum over the billing period.
There was a problem hiding this comment.
Ok, @ptgott can we just change "a count" to "an anonymized log"?
There was a problem hiding this comment.
How important is it to customers that we describe the precise nature of the data, i.e., whether we aggregate it on the Teleport Cloud infra vs. whether it comes pre-aggregated from the customer's Teleport deployment? If it's important to specify, it looks like "anonymized log" is only accurate for Teleport Cloud.
I'll suggest:
- For each Teleport user, the anonymized user name and a count of interactions
with infrastructure resources enrolled in your Teleport cluster.
Self-hosted Teleport deployments aggregate interaction data before it reaches Teleport Cloud.
Teleport Cloud accounts provide this information as an anonymized log, which
Teleport aggregates over the billing period.There was a problem hiding this comment.
@bl-nero when we get to the implementation of RFD 0014e we should update this to mention that the HMAC key might be in the license file instead.
|
This looks good to me. I'm not sure how to address @espadolini comment about roll-ups but once it is it can be deployed. |
|
🤖 Vercel preview here: https://docs-b260h5fyd-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/34220-usage
branch
from
290035e to
36724f7
Compare
|
🤖 Vercel preview here: https://docs-3mzvxbgvd-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-lo3qyodvb-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/34220-usage
branch
from
4ea8a2e to
379fe19
Compare
|
🤖 Vercel preview here: https://docs-12i0rsexh-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/34220-usage
branch
from
379fe19 to
4c0aecb
Compare
|
🤖 Vercel preview here: https://docs-mt8onzbe9-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/34220-usage
branch
from
4c0aecb to
5011d77
Compare
|
🤖 Vercel preview here: https://docs-h3pbk4e0t-goteleport.vercel.app/docs/ver/preview |
Closes #34220 Add a docs page to the Home section that describes the way we calculate customer usage data and billing for commercial editions of Teleport.
- Remove specific edition names - Clarify counts
Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
ptgott
force-pushed
the
paul.gottschling/34220-usage
branch
from
5011d77 to
212aabc
Compare
|
🤖 Vercel preview here: https://docs-5jva7utw8-goteleport.vercel.app/docs/ver/preview |
5 participants
Closes #34220
Add a docs page to the Home section that describes the way we calculate customer usage data and billing for commercial editions of Teleport.