Dagster discovery should treat the webserver as an execution control plane
Dagster webserver discovery tied to GraphQL, code locations, and launch authority.
Tag archive
Dagster webserver discovery tied to GraphQL, code locations, and launch authority.
Dagster returns 1,712 title matches and a single application fingerprint, which means external measurement cannot reliably locate instances of it.
If you run Dagster pipelines in production, you've probably wanted distributed tracing at some point...

Dagster doesn't have a built-in way to get OpenTelemetry traces out of a run. There's an open issue...

Dagster joining Prefect signals the end of standalone orchestrators. The winners will be unified...

TL;DR Dagster AuthKit is a community auth/RBAC wrapper for self-hosted Dagster OSS — no...

A follow-up to the first post about dagster-prometheus-exporter, a small Go binary that polls...

Dagster doesn't expose a /metrics endpoint out of the box. The officially documented way to get...
Your data pipeline orchestrator is the nervous system of your data platform. Every pipeline, every...

Building reliable data platforms rarely fails because of scale alone. More often, reliability...
Introduction Modern data stacks rely on specialized tools for transformation (dbt) and...
This article is a technical companion to our earlier essay on geospatial data orchestration (link:...