-
Notifications
You must be signed in to change notification settings - Fork 86
Feat: Metering and Billing customer entity #3540
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
Changes from all commits
cdb2d04
892261a
a933a4e
d4b346c
63716b3
9f6f135
286eb1b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,180 @@ | ||
| --- | ||
| title: "Customers and usage attribution" | ||
| content_type: reference | ||
| description: "Learn how Customers and usage attributes work in {{site.konnect_short_name}} Metering and Billing and how they access features." | ||
| layout: reference | ||
| products: | ||
| - metering-and-billing | ||
| tools: | ||
| - konnect-api | ||
| works_on: | ||
| - konnect | ||
| breadcrumbs: | ||
| - /metering-and-billing/ | ||
| related_resources: | ||
| - text: "{{site.konnect_short_name}} Metering and Billing" | ||
| url: /metering-and-billing/ | ||
| --- | ||
|
|
||
| ## What is a customer? | ||
|
|
||
| Customers represent individuals or organizations that subscribe to plans, gain access to features, and are invoiced for their consumption. | ||
|
|
||
| Billable events ingested into Metering & Billing always include a subject field that represents metered entities within your system, such as {{site.base_gateway}} [Consumers](/gateway/entities/consumer/), [Dev Portal applications](/dev-portal/self-service/), or [subjects](#what-is-a-subject) or entities outside of {{site.konnect_short_name}}. | ||
|
|
||
| A customer can have **one or many** usage attributes assigned, allowing you to group usage and billing. For example, if a customer has multiple departments that are producing usage, you could create two usage attributes for each department that are assigned to one customer. | ||
|
|
||
| {% mermaid %} | ||
| flowchart TB | ||
| %% Left side | ||
| Customer[Customer] | ||
| Subject[Subject] | ||
| UsageEventsLeft[Usage Events] | ||
|
|
||
| Customer -->|1:n| Subject | ||
| Subject -->|1:n| UsageEventsLeft | ||
|
|
||
| %% Right side | ||
| ACME[ACME Inc.] | ||
| Dept1[Department 1] | ||
| Dept2[Department 2] | ||
| UsageEvents1[Usage Events] | ||
| UsageEvents2[Usage Events] | ||
|
|
||
| ACME --> Dept1 | ||
| ACME --> Dept2 | ||
|
|
||
| Dept1 --> UsageEvents1 | ||
| Dept2 --> UsageEvents2 | ||
| {% endmermaid %} | ||
|
|
||
| Use the following table to help you determine the best way to map your customers to usage attributes: | ||
|
|
||
| {% table %} | ||
| columns: | ||
| - title: You want to... | ||
| key: use-case | ||
| - title: Then use... | ||
| key: recommendation | ||
| rows: | ||
| - use-case: | | ||
| Attribute Kong AI Gateway token usage to customers. | ||
| recommendation: "[Consumers](/gateway/entities/consumer/)" | ||
| - use-case: | | ||
| Attribute {{site.base_gateway}} API request usage to customers. | ||
| recommendation: "[Consumers](/gateway/entities/consumer/)" | ||
| - use-case: | | ||
| Attribute {{site.konnect_short_name}} Dev Portal application requests to customers. | ||
| recommendation: "[Applications](/dev-portal/self-service/)" | ||
| - use-case: | | ||
| Attribute usage from sources outside of {{site.base_gateway}} and {{site.konnect_short_name}} to customers. | ||
| recommendation: "[Subjects](#what-is-a-subject)" | ||
| {% endtable %} | ||
|
|
||
| ### What is a subject? | ||
|
|
||
| Subjects represent the entity that consumes metered resources in {{site.konnect_short_name}} Metering and Billing. Billable events ingested to Metering and Billing have a subject associated with them. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Metering & Billing |
||
|
|
||
| A subject can represent any unique event in your system, such as: | ||
| * Customer ID or User ID | ||
| * Hostname or IP address | ||
| * Service or application name | ||
| * Device ID | ||
|
|
||
| The subject model is intentionally generic, enabling flexible application across different metering scenarios. | ||
|
|
||
|
|
||
|
|
||
| #### Data ingestion | ||
|
|
||
| When shipping data to {{site.konnect_short_name}}, you must include the subject within the events payload: | ||
|
|
||
| ```ts | ||
| { | ||
| "specversion": "1.0", | ||
| "type": "api-calls", | ||
| "id": "00002", | ||
| "time": "2023-01-01T00:00:00.001Z", | ||
| "source": "service-0", | ||
| "subject": "customer-1", | ||
| "data": {...} | ||
| } | ||
| ``` | ||
|
|
||
| ## Create a customer | ||
|
|
||
| To create a customer in {{site.konnect_short_name}}, do the following: | ||
|
|
||
| {% navtabs "customer" %} | ||
| {% navtab "Consumer" %} | ||
|
|
||
| 1. In the {{site.konnect_short_name}} sidebar, click **Metering & Billing**. | ||
| 1. In the Metering & Billing sidebar, click **Billing**. | ||
| 1. Click **Create Customer**. | ||
| 1. In the **Name** field, enter your customer's name. | ||
| 1. Select **Consumers**. | ||
| 1. In the **Include usage from** dropdown, search for your Consumer. | ||
| 1. Click **Save**. | ||
|
|
||
| {% endnavtab %} | ||
| {% navtab "Application" %} | ||
|
|
||
| 1. In the {{site.konnect_short_name}} sidebar, click **Metering & Billing**. | ||
| 1. In the Metering & Billing sidebar, click **Billing**. | ||
| 1. Click **Create Customer**. | ||
| 1. In the **Name** field, enter your customer's name. | ||
| 1. Select **Applications**. | ||
| 1. In the **Include usage from** dropdown, search for the Dev Portal application. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we call it Dev Portal or Developer Portal?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @hekike It's Dev Portal |
||
| 1. Click **Save**. | ||
|
|
||
| {% endnavtab %} | ||
| {% navtab "Subject" %} | ||
|
|
||
| {:.warning} | ||
| > **Important:** During the billing beta, customers are limited to **one subject**. Support for multiple subjects will be available in the future. | ||
|
|
||
| Subjects are created when you create the customer. To create a customer associated with a subject, send a `POST` request to the `/api/v1/customers` endpoint: | ||
|
|
||
| ``` | ||
| curl https://openmeter.cloud/api/v1/customers \ | ||
| --request POST \ | ||
| --header 'Content-Type: application/json' \ | ||
| --header 'Authorization: Bearer $KONNECT_TOKEN' \ | ||
| --data '{ | ||
| "name": "", | ||
| "description": "", | ||
| "metadata": { | ||
| "externalId": "019142cc-a016-796a-8113-1a942fecd26d" | ||
| }, | ||
| "key": "", | ||
| "usageAttribution": { | ||
| "subjectKeys": [ | ||
| "$YOUR-SUBJECT" | ||
| ] | ||
| }, | ||
| "primaryEmail": "", | ||
| "currency": "USD", | ||
| "billingAddress": { | ||
| "country": "US", | ||
| "postalCode": "", | ||
| "state": "", | ||
| "city": "", | ||
| "line1": "", | ||
| "line2": "", | ||
| "phoneNumber": "" | ||
| } | ||
| }' | ||
| ``` | ||
|
|
||
| Replace `$KONNECT_TOKEN` with your [{{site.konnect_short_name}} personal or system access token](/konnect-api/#system-accounts-and-access-tokens). | ||
|
|
||
| {:.info} | ||
| > {{site.konnect_short_name}} Metering and Billing will also automatically create a subject for you when you ingest an usage event for a new subject. | ||
|
|
||
| {% endnavtab %} | ||
| {% endnavtabs %} | ||
|
|
||
|
|
||
| ## Schema | ||
|
|
||
| [Insert Schema here](https://openmeter.io/docs/api/cloud#tag/customers) | ||
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Metering & Billing