List Custom Metrics
List custom metrics with optional filters.
The three applicability filters exist so a picker can stop offering metrics that cannot produce a result. Both re-evaluate fetchers called this with {} and filtered on status === "active" alone, so the phone page's menu listed booking-only and formula metrics. Choosing one succeeded silently and wrote nothing: the job enqueued, enqueued_count counted the logs truthfully, and the per-log gate metric_applies_to_log dropped every one of them.
Filtered server-side rather than in the picker, because there are four consumers and client-side filtering is how they drift — GET /log-columns already made this argument and has been filtering by applies_to_* since it shipped.
Query parameters
Only metrics that can score this subject. A voice-only metric on a text log renders dashes at best and, offered in a re-evaluate menu, enqueues a job that writes nothing.
Only metrics that can score this subject. A voice-only metric on a text log renders dashes at best and, offered in a re-evaluate menu, enqueues a job that writes nothing.
Only metrics of this compute type. Re-evaluation scores MODEL metrics; a FORMULA metric is derived from other metrics and is excluded by the candidate query long before any worker sees it.
Only metrics with (or without) an active revision. A metric with none has no prompt to run, so re-scoring it is a no-op.
Only metrics with (or without) an active revision. A metric with none has no prompt to run, so re-scoring it is a no-op.
Response
Successful Response
Changes
No recorded changes to this endpoint across all 1 revision of this API.