Consumers
- Applies to
- Gatewayruntime for API, AI, and MCP gateways
- Hosting
- Managed EdgeManaged DedicatedSelf-Hosted
The Consumers section breaks traffic down by API consumer: anyone calling your gateway, whether authenticated or anonymous. Use it to see who your noisiest callers are, who's hitting errors, and which consumers experience the slowest latency.
When to use this
- Find the top API consumers by request volume.
- Identify which consumer is responsible for a 4xx or 5xx surge.
- Compare latency experience across consumers (for example, paid vs free tier).
Summary KPIs
| Name | What it measures |
|---|---|
| Requests | Total requests across all consumers in the window. |
| Client Errors | Request-weighted 4xx rate across consumers (high-traffic consumers count more). See Metrics glossary. |
| Server Errors | Request-weighted 5xx rate. Secondary: count of consumers with at least one 5xx. |
| Consumers | Distinct consumers (authenticated plus anonymous). |
| Total Errors | Combined 4xx + 5xx count. Secondary: consumers affected. |
Charts
Request Volume. Stacked bars by status class. The chart title updates to reflect the active consumer filter so you can tell at a glance whether you're looking at one consumer or all of them.
Consumer Error Rates. 4xx and 5xx over time. What to look for: a sustained 4xx rate from one consumer usually points to a broken integration on their side.
Consumer Latency Over Time. P50, P95, P99 lines.
Consumer table
| Column | Notes |
|---|---|
| User | Consumer identity. Anonymous requests show Anonymous · No auth. |
| Requests | Count with an inline volume bar. |
| Client Errors % | 4xx percentage. |
| Server Errors % | 5xx percentage. |
| Avg / P95 / P99 | Latency percentiles. |
| 4xx sparkline | Inline trend over the window. |
| 5xx sparkline | Inline trend over the window. |
The table is searchable and sortable on any column (default: requests descending). Clicking a row filters the entire section to that consumer. Show more loads the next 50.
Consumer details
Select the Consumer details icon next to a consumer to open a panel that shows who the consumer is, without leaving Analytics. The panel looks the consumer up by name across your project's environments, and shows:
- API key consumer: the environment the consumer belongs to, its key managers, and its tags. If the consumer exists in more than one environment, pick the environment to view. Open in API Keys opens the API Keys list filtered to the consumer, and Edit consumer opens its edit dialog.
- Monetization customer: when the consumer's key managers match a monetization customer, the customer's plan and status, with links to Open customer and Open subscription. If no customer matches, Search customers opens the Customers page filtered by the key manager's email.
The panel also has Show only this consumer's traffic, which filters the section to that consumer.
You can open the panel from:
- The consumer tables on Overview and Consumers.
- The Consumers breakdown on Requests, and the consumer tables on GraphQL and MCP.
- A consumer filter pill. A pill that matches one exact consumer has a details icon, so tabs without a consumer table, such as Cache and Origins, can open it too. A pill that matches a pattern has none.
- A request's User field in the log details of a project's logs.
If no API key consumer has the name, the panel says so. The request may have been authenticated another way, such as a JWT, or the consumer may have been deleted. Anonymous requests have no details.
The panel isn't available on AI Gateway projects, whose consumers are apps, or at account scope.
Filters
The filter bar applies. originHost doesn't apply in this section. See
Shared controls.
Troubleshooting
Everything is showing as Anonymous. If your gateway isn't authenticating requests, or your auth policy isn't attaching a consumer identity, every request falls into the Anonymous · No auth bucket. Check your API key or JWT policy configuration.
I clicked a row but the charts didn't change. A row click adds a consumer filter pill. If you don't see the pill in the sticky bar, your click landed on a non-row element. Try clicking the user cell directly.
The 5xx rate here is higher than on Requests. The Consumers KPI is request-weighted across consumers, while the Requests KPI is a flat rate over all requests. They diverge when high-error consumers are a small share of total volume. See Metrics glossary.