Get Agent Observability Config

Scope for a dashboard read.

project_ids and log_stream_ids are both optional: omitted means every project in the caller's org, and every dashboard-eligible run within it. Supplying either outside the caller's org is rejected rather than silently narrowed, so a wrong scope surfaces as an error instead of a quietly smaller number.

Both are typed as UUIDs so a malformed ID is rejected here, at the edge. As plain strings they reached Postgres as a comparison against a UUID column and surfaced as a 500.

What the dashboard's pickers can offer, and what to chart by default.

The selection is not persisted server-side: the client sends metric_keys on the trends request and owns the user's choice. evaluator_metric_keys is a deterministic default so a client with no stored selection still renders a populated chart.

available_evaluator_metrics is the org's whole scorer registry, deliberately not the set of keys seen in the window — a window-derived list changes size with the time range, so the same org offered 5 evaluators at 7 days and 45 at 90. The defaults stay window-derived, so they chart evaluators that actually ran.

available_log_streams covers every stream in the selected projects and is deliberately not narrowed by the request's own log_stream_ids — otherwise picking a stream would collapse the picker to that one entry and the user could never widen the selection again.

available_projects is the picker's own source of truth rather than the host's paginated project list, which would silently omit projects past its first page — including ones holding data.