Business metrics

Insights shows a fixed set of metrics for each supported integration. Their calculations are defined in code and remain consistent across the dashboard, chat, operator, and department agents. There is no custom metric or formula editor.

The overview starts with compact, collapsed integration groups. Expand one to load its complete metric inventory, including metrics that are still collecting or need attention. Only the open group queries values, so metrics do not delay the initial page. One integration opens at a time; the URL preserves that selection. Loading and retry states stay inside the open group, and the other integrations remain accessible. Recently opened results are reused for up to thirty seconds; changing the history range loads that range only for the open integration. Accounts, resources, environments and currencies stay separate. Equal-sized cards show each resource’s value, reporting date and a compact trend. Choose Details to expand a metric beneath its row; the surrounding summary cards keep their size. One metric expands at a time.

Use Trend, Values and Source in the expanded panel to inspect the chart, exact values, coverage, definition and query receipt. Open history opens the full explorer; All metrics returns to the overview. Collapse with Less, the panel’s close button, or Escape while focus is inside the panel. Keyboard focus returns to the selected card. Connected integration cards also offer View metrics to open their connector’s overview directly.

Overview values are the latest available daily, weekly or monthly observations within the selected range, not totals for that entire range. Their reporting periods and coverage remain visible. A gap in the latest period is shown even when an earlier value is available. If a query cannot finish, its card shows the availability state and its expanded details keep the full reason. Other metrics remain available; open its history to retry or narrow the range.

Each result names its source, metric version, currency, reporting timezone, coverage and last update. Missing data appears as a gap, not zero. Hover or focus a chart point to inspect its exact value. Connecting a system does not guarantee reporting permission or historical data.

Collection and refresh

Built-in collectors refresh hourly and retain separate progress for historical backfill. Choose Refresh metrics to request earlier collection. Repeated requests share the same pending work; they do not create duplicate jobs, bypass provider backoff, or spend a task action. The reporting status shows whether collection is queued, in progress, incomplete, or needs connection settings.

Agents can request the same refresh with oblivectl insight refresh, optionally for one connector. A task can schedule its analysis at the frequency you choose and read these shared results each time. Fresh collection is asynchronous; an agent must inspect coverage and timestamps before claiming that new numbers are available.

Shared access and stable meaning

Every enabled agent in the organization can read its shared aggregate metrics. Permission to call a live integration or read raw customer records is separate. Disabled connections and current resource restrictions still apply. One organization’s agents cannot read another organization’s metrics.

Agents can consult retained history for planning and evaluating business operations, with up to twelve months per query. This query bound is not a retention limit. A rise or fall after an operation is evidence to investigate, not proof that the operation caused it. Compare compatible definitions, periods and populations, record when the intervention happened, and use a control or experiment where possible before claiming a causal effect.

GitHub reports cover the repositories selected in integration settings. Database reports use the selected collections, indexed fields or explicit numeric keys. These settings restrict the fixed collector; they do not define arbitrary new formulas. PostHog reports fixed activity metrics, and Meta uses the documented default attribution. Product-specific activation and retention definitions are not inferred from unknown events.

Saved query receipts preserve the exact results and their provenance. Historical definitions remain immutable. Existing custom definitions are retired from new queries; their retained receipts remain readable subject to current access. If a code-owned calculation changes, it receives a new version instead of silently changing a previously published result.