Skip to main content

​
Workspace Usage

Here, you can have an overview of your usage over the current billing cycle. A graph displays the number of Requests, Retrievals, and Cache over time in your workspace. These are tracked across all Playground, Experiment, Deployment, and Agent and show an aggregated view of all events. At the top-right of the graph, you can see your current usage against your plan capacity. When going beyond capacity, additional events are added to your billing cycle.
Billing Pn

From the billing page, see the Storage Usage and Plan Usage, along with the current subscription.

An additional view of the current events can be seen from your main Dashboard.
Billing Dashboard 314

View workspace usage in your Dashboard

​
Understanding Trace Storage Usage

Our platform stores distributed traces received through OpenTelemetry:
  1. Each trace is composed of one or more spans, which represent individual operations or segments of a request.
  2. Each span is encoded as JSON data before being stored.
  3. Once encoded, we apply an indexing layer on top of the raw data. This indexing allows for fast search and filtering across large trace datasets.
To account for both the raw and indexed data, we estimate total storage consumption as: 
total_storage = (raw_bytes * 1.7)
In other words, the indexed representation roughly doubles the storage footprint compared to the raw JSON data.
Using OpenTelemetry, some exporters send incremental payloads which might result in sudden increases.
  • This means each new span can contain data from previous messages as well.
  • This results in larger payloads over time, and consequently, sudden jumps in reported storage usage.
  • Check your exporter configuration when dealing with sudden increases.
To reduce storage usage, consider:
  • Sampling fewer spans per trace.
  • Filtering out high-volume, low-value telemetry data.
  • Using compression or limiting payload size before sending.
These optimizations can help maintain observability while keeping your storage footprint efficient.

​
Understanding Events

A single Deployment invoke contains multiple events, each event will incur costs reflected in your Billing and Plan Usage. To understand better the events held within your Deployments, lookup Analytics and explore the events embedded into each generation.

Each trace and event detail will hold usage and billing information.

​
Rate Limits

Our APIs are protected through Rate Limits on a per-account basis to ensure fair and efficient use of the API. This helps maintain optimal performance and prevent server overload, while also protecting against potential abuse and limiting costs effectively. When reaching rate limit, API calls are denied with a 429 Too Many Requests response.
SubscriptionRate Limit
Developer50 API calls/day
EnterpriseCustom
To learn more about the Orq.ai Pricing options or to upgrade your plan, see Our Pricing Page.