fix(metering-and-billing): Correct meter payloads and UI steps in M&B onboarding guides [OM-426] - #6533
Open
gergely-kurucz-konghq wants to merge 8 commits into
Open
fix(metering-and-billing): Correct meter payloads and UI steps in M&B onboarding guides [OM-426]#6533gergely-kurucz-konghq wants to merge 8 commits into
gergely-kurucz-konghq wants to merge 8 commits into
Conversation
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
tothandras
approved these changes
Aug 3, 2026
The "Create a meter" step used event_type `request` with only `method` and `route` dimensions, which does not match the events emitted by the Metering & Billing plugin for API Gateway traffic. Update the payload to match the `api_requests` meter template (Kong-env branch): event_type `kong.api_request` and the full dimension set the plugin emits (request/response metadata plus Kong Gateway identifiers). Verified against the plugin source cloudevent.lua (create_api_event, type "kong.api_request").
In the "Create a feature" step, the Meter dropdown referenced a meter
name ("API Gateway Requests") that does not exist; update it to
"API requests" to match the meter created in the previous step.
Also correct the Value field instruction: it is a free-text entry, not
a select, so use "In the Value dropdown menu, enter" instead of
"From the Value dropdown menu, select".
The "Create Customer" flow omitted the mandatory Key field; add a step to enter `kong-air` in the Key field. Also fix the final button label: it reads "Start Subscription", not "Create Subscription" (this also aligns with the LLM traffic guide).
The "Create a meter" step used event_type `prompt` with only `model` and `type` dimensions, which does not match the events emitted by the Metering & Billing plugin for LLM traffic. Update the payload to match the `llm_tokens` meter template (Kong-env branch): event_type `kong.llm_request` and the full dimension set the plugin emits (request/LLM metadata plus Kong Gateway identifiers), with `$.tokens` as the value property. Verified against the plugin source cloudevent.lua (create_ai_event, type "kong.llm_request").
In the "Create a feature" step, the Meter dropdown referenced a meter
name ("AI Gateway Tokens") that does not exist; update it to
"LLM Tokens" to match the meter created in the previous step.
The "Create Customer" flow omitted the mandatory Key field; add a step to enter `kong-air` in the Key field.
gergely-kurucz-konghq
force-pushed
the
fix/OM-426-mb-onboarding-guides
branch
from
August 3, 2026 11:15
e8faa2c to
b605c09
Compare
gergely-kurucz-konghq
marked this pull request as ready for review
August 3, 2026 11:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Corrects content errors in the two Konnect Metering & Billing onboarding guides found during an onboarding audit.
What
event_type: kong.api_request+ full dimension set.event_type: kong.llm_request+ full dimension set.Why
The old payloads used invalid
event_types (request,prompt) with missing dimensions, so metering would not match plugin events and the tutorials would not produce billable usage. UI labels referenced meters and buttons that don't exist, and the mandatory Key field was omitted.How
Payloads verified against the plugin source
cloudevent.lua(kong.api_request/kong.llm_requestand their emitteddatafields) and theapi_requests/llm_tokensmeter templates. Both pages render-checked locally at127.0.0.1:4000.Files:
app/_how-tos/gateway/get-started-with-metering-and-billing.mdapp/_how-tos/ai-gateway/meter-llm-traffic.mdFixes https://konghq.atlassian.net/browse/OM-426
Preview Links
Checklist
automated_tests: false).descriptionentry in frontmatter.