EvSnow

EvSnow streams events from Azure Event Hubs into Snowflake with checkpointing, configuration validation, and operational observability.

Start With First Run

Start here when you want one Event Hub, one Snowflake target, one checkpoint table, and a repeatable local smoke test.

Go to First run to install EvSnow, configure one local pipeline, validate the settings, and run it.

Start first run Set up Event Hub Set up Snowflake

Other Paths

• Set up Snowflake from scratch: Snowflake quickstart
• Set up Azure Event Hubs from scratch: Event Hub quickstart
• Configure key-pair authentication: Snowflake key-pair auth
• Tune runtime settings: Configuration
• Check every Snowflake object and grant: Complete Snowflake setup
• Inspect Iceberg data with DuckDB: DuckDB Iceberg guide
• Run contributor checks: Testing

What EvSnow Connects

flowchart LR
    eventhub["Azure Event Hubs"] --> consumer["EvSnow consumer"]
    consumer --> checkpoint["Checkpoint backend"]
    consumer --> pipe["Snowpipe Streaming"]
    pipe --> snowflake["Snowflake table or Snowflake-managed Iceberg table"]
    consumer --> logs["Logfire and local logs"]

The Event Hub consumer reads from configured partitions. EvSnow writes data through Snowpipe Streaming and records progress in a control backend. Later runs resume from saved checkpoints.

Runtime Choices

flowchart TD
    start["Pick checkpoint backend"] --> smoke{"Local smoke test?"}
    smoke -- yes --> standard["Snowflake standard control table\nlocal_single_consumer_smoke"]
    smoke -- no --> multi{"Multiple consumers or failover?"}
    multi -- yes --> hybrid["Snowflake Hybrid Table\ndurable ownership"]
    multi -- no --> postgres["Postgres backend\npassword or Azure token auth"]

The local tutorial uses a Snowflake standard control table and local_single_consumer_smoke. Production deployments should use durable ownership with a Snowflake Hybrid Table or the Postgres control-table backend.

After First Run

Use the Snowflake setup pages when you need to create or audit account objects. Use the configuration reference when you are changing pipeline behavior. Use the how-to guides for operational tasks after the first pipeline works.

Documentation Provenance

Parts of this documentation were drafted with assistance from Codex and GPT-5.5, then reviewed against the EvSnow project.