Skip to main content

Documentation Index

Fetch the complete documentation index at: https://metoro.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Incremental Cache

Metoro uses an incremental cache to make repeated historical queries much faster. When you query a long time range, Metoro can reuse work from previous queries instead of recomputing the whole range from scratch. If a later query overlaps with data that has already been queried, Metoro can use the cached parts and only compute the missing parts. For long-running queries, this can provide up to 100x speedups once the relevant historical data has been cached.

​
When it helps

The incremental cache is most useful for expensive queries that are run more than once. Common examples include:
  • Dashboards that refresh over mostly historical time ranges
  • Investigations where several people query the same incident window
  • Saved searches and views that are opened repeatedly
  • Long-range logs, traces, metrics, or Kubernetes resource queries
  • Attribute and filter dropdowns over large time ranges
The first time a query runs, Metoro may still need to compute the result normally. Later queries over the same or overlapping data can be much faster.

​
How to get the most benefit

Use stable query shapes where possible. The cache is most effective when queries reuse the same filters, grouping, attributes, and time ranges. Reopening the same dashboard, refreshing a seven-day query, or sharing a saved investigation view with a teammate are good examples. Queries that constantly change filters or only look at the most recent few minutes are less likely to benefit, because there is less reusable historical work.

​
Fresh data

Metoro avoids serving very recent telemetry from the cache. The newest logs, traces, metrics, and Kubernetes data are queried live so results stay fresh. Historical parts of the same request can still use the incremental cache.

​
What you need to do

Usually, nothing. The incremental cache is automatic. If your query is eligible and overlaps with previously cached work, Metoro will use the cache without requiring any changes to the query.