ClickHouse sink blog update

[nikbhintade]

Add restart-/reorg-resistance and Prometheus storage-name label note. Clarify env vars required in both .env (local) and Envio Cloud dashboard (hosted), with envio dev spinning up local ClickHouse Docker alongside.

Summary by CodeRabbit

• Documentation
  • Updated ClickHouse storage tutorial with clarified environment variable setup instructions for local .env configuration
  • Added details on restart and reorganization resistance, plus crash recovery via checkpointing
  • Documented new storage-name label in Prometheus metrics for improved monitoring granularity

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
envio-docs	Ready	Preview, Comment	May 5, 2026 9:43am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2572e7c4-7528-4d29-acd8-ef6772334915

📥 Commits

Reviewing files that changed from the base of the PR and between 8b2c5a7 and 422df6e.

📒 Files selected for processing (1)

• blog/2026-04-24-clickhouse-storage.md

---

📝 Walkthrough

Walkthrough

Updates a ClickHouse storage tutorial blog post to clarify restart and crash recovery behavior, add Prometheus metrics labeling, and reword setup instructions to emphasize local environment variable configuration via .env file instead of Envio Cloud-specific deployment.

Changes

Documentation Update

Layer / File(s)	Summary
Tutorial Content blog/2026-04-24-clickhouse-storage.md	Added explanation of restart/reorg resistance, checkpoints for clean crash recovery, and Prometheus storage-name label for monitoring separation; rewrote environment setup instructions to describe local .env configuration and Docker container startup with envio dev; removed "on your Envio Cloud deployment" phrasing from replication description.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A blog post finds its way,
With docs that now make clear the day,
ClickHouse runs local, strong, and true,
Crash-resistant through and through!
Prometheus labels shine so bright,
The storage path is set just right. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'ClickHouse sink blog update' directly and clearly summarizes the main change—updating the ClickHouse sink documentation in a blog post.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch nb/clickhouse-blog-update

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}