Rate Control Dashboard

The Rate Control dashboard shows how your rate control policies behave against real traffic: how much each class receives compared with its limit, how much it throttles, and which classes drop everything they match. It is built from the ingester’s rate control metrics, per stream and class. Kloudfuse’s own control plane class (kfuse_cp_class) is never rate limited and is left out.

Open the dashboard

Open the dashboard in the Kloudfuse UI (the /f interface); it is not designed for the legacy UI.

  1. In the top navigation, click Dashboards.

  2. Search for Rate Control. The dashboard is in the kfuse-ingest-v2 folder.

Use the Organization, Cluster, Stream, and Class variables to narrow the dashboard.

Class types

The dashboard groups classes by their configured limit:

Limited

Classes with a limit above 0, including default. Traffic over the limit (or the burst) is throttled.

Drop-all

Classes with a limit of 0. Every data point they match is dropped, so they work as filters rather than limits.

Unconfigured

Classes that drop data but have no configured limit: a class rule names a class that the policy does not define, so everything it matches is dropped. This is usually a missing or misspelled class.

A class with no limit and no drops means rate control is off for that stream.

Rows

Row What it shows

Summary

For the selected time range: data points Offered to rate control (allowed + dropped), Allowed, Dropped, and the Drop Ratio. Drops are split into Throttled (over a class’s limit) and Filtered (by drop-all and unconfigured classes). The current number of Limited, Drop-all, and Over Limit classes, the highest Top Use of any limited class, the Total Limit of the selected classes, and the number of Unconfigured classes.

Classes

A table with one line per class: its configured limit now (Drop all for a limit of 0, No limit for an unconfigured class) and its traffic over the selected time range.

Limited Classes

Per limited class, over time: Limit Use (data offered ÷ the configured limit; over 100% the class is throttled), data offered, allowed, and throttled, and the throttled ratio. Default Class Share shows how much of each stream’s traffic no class rule matched; a high share means the custom classes cover little of the traffic.

Drop-all & Unconfigured Classes

Data dropped by drop-all classes and by unconfigured classes, and the share of each stream’s traffic they drop.

Limits

The configured limit per class over time (steps show policy changes), the limit enforced by each ingester, and the number of ingesters enforcing a policy per stream.

Rate-limited by Agent

Metrics, logs, events, and RUM data dropped by rate control, split by the agent that sent it. Requires Kloudfuse 4.4.0 or later. Traces are not broken down by agent.

Read the dashboard

  • A class drops data at well under 100% limit use. Each ingester enforces its own share of the class limit, and a class’s burst is proportional to its whole-percent share of the stream’s rate. Uneven load across ingesters, or a class with less than 1% of the stream’s rate, can throttle before the class reaches its total limit. See How rate control works.

  • Unconfigured is above 0. Check the policy for a class that a rule refers to but that does not exist, and add it or fix the name.

  • A drop-all class you did not expect. Classes created for an ingestion API key start with a limit of 0. See Classes created from ingestion API keys.

  • Default Class Share is high. Most traffic falls into the default class; add label matchers or classes if you meant to limit sources separately.

The burst size is not shown on the dashboard.

Next steps