Interface: RunMetricContext
Defined in: server/insights/services/query-service.ts:56
Properties
bucket?
optional bucket?: "year" | "month" | "day" | "week" | "quarter";Defined in: server/insights/services/query-service.ts:59
extraLeaves?
optional extraLeaves?: readonly (
| {
field: string;
kind: "condition";
operator: "eq";
value: string | number | boolean;
}
| {
field: string;
kind: "condition";
operator: "neq";
value: string | number | boolean;
}
| {
field: string;
kind: "condition";
operator: "gt";
value: string | number;
}
| {
field: string;
kind: "condition";
operator: "lt";
value: string | number;
}
| {
field: string;
kind: "condition";
operator: "gte";
value: string | number;
}
| {
field: string;
kind: "condition";
operator: "lte";
value: string | number;
}
| {
field: string;
kind: "condition";
operator: "contains";
value: string;
}
| {
field: string;
kind: "condition";
operator: "in";
value: (string | number | boolean)[];
}
| {
field: string;
kind: "condition";
operator: "between";
value: {
from: string | number;
to: string | number;
};
}
| {
field: string;
kind: "condition";
operator: "isNull";
}
| {
field: string;
kind: "condition";
operator: "isNotNull";
})[];Defined in: server/insights/services/query-service.ts:69
Extra condition leaves AND-ed onto the metric, used by dashboard
interactive filters. The dashboard layer hands in only the leaves this
metric's subject can honour (applicableDashboardFilterLeaves); they
are folded flat alongside the metric's static filter and the optional date
range by buildMetricFilter — the leaves are NOT pre-wrapped, so the
result stays a single flat and instead of nesting one group inside
another.
organizationId
organizationId: string;Defined in: server/insights/services/query-service.ts:57
range?
optional range?: {
from: string;
to: string;
};Defined in: server/insights/services/query-service.ts:58
from
from: string;to
to: string;