Yes, by “API path” I mean the matched FastAPI route template, not the concrete
request path.
For example, a request to:
/api/v2/dags/example_dag/dagRuns/manual__2026-07-07/taskInstances/extract
would emit:
route="/api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}"
So dag_id/task_id/dag_run_id values are not included in the metric tag, keeping
cardinality bounded.
On 2026/07/07 12:54:54 Ash Berlin-Taylor wrote:
>
>
> > On 7 Jul 2026, at 13:52, Henry Chen <[email protected]> wrote:
> >
> > Following Vincent’s suggestion, we drop the proxy-name mapping
> > entirely and use the API path directly as the metric tag.
>
> Can you give more example of what this looks like with paths that have
> parameters in it, such as dag_id or task_id etc.
>
>
> -ash
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
