Infrastructure
What if a dltHub pipeline fails without errors?
A watchdog to keep all dlt pipelines in line
Posts related to platforms (usually hyperscalers), pipelines (ELT/rETL, streaming, orchestration) and agents
Infrastructure
A watchdog to keep all dlt pipelines in line
Infrastructure
Nobody documents dozens of tables with hundreds of columns by hand. So an agent does it, INFORMATION_SCHEMA keeps it honest, and Teams pings when a source API adds a column
Infrastructure
dltHub ships Slack and email alerts out of the box. My org runs on Teams, so I built the third one myself and wired it into all ~70 pipelines with one decorator shadow.
Infrastructure
Re-using shared patterns in a dlt workspace
Infrastructure
LinkedIn's Marketing API needs a browser to authorize. Scheduled pipelines don't have browsers. I store the refresh token in Snowflake.
Infrastructure
A public contact list sounds easy... until 2,110 websites, four languages, changing staff, and source evidence get involved. π
Infrastructure
Microsoft Planner has no native backup export, so I built a declarative dlt job that writes complete Graph snapshots to Azure Blob. π
Infrastructure
Every opencode session leaves a trail in a local SQLite file. dlt turns it into analytics you actually read.
Infrastructure
Exit code 137 is dlt's way of saying "your RAM and I need to talk"
Lakehouse
MotherDuck shipped agent-native Python pipelines. The obvious thing to run inside one is dlt.
Infrastructure
Bring your own model, ditch the subscription.
Infrastructure
Why let a search engine guess what context your model needs? Perplexity's new Search as Code hands the reins to the agent.