NeverBlink AI

@neverblinkai

Database reliability and performance, for AI with AI. Currently supporting #ClickHouse #OpenSearch #Elasticsearch.

Joined July 2026

Pinned
NeverBlink AI
@neverblinkai
Aug 25
NeverBlink now supports #ClickHouse: Cloud, self-hosted, and the Kubernetes operator. The worst ClickHouse failures never page you: merge backlogs, stalled TTLs, materialized views dropping data. We catch them while they're still warnings, with the fix attached.
NeverBlink Announces Support for ClickHouse
From neverblink.ai
NeverBlink AI
@neverblinkai
1h
Logs, metrics, and traces used to live in three tools with three formats. OpenTelemetry ended that. Our founder's OpenSearchCon talk covers using OTel with OpenSearch today, and what's on the roadmap. #OpenTelemetry #OpenSearch
NeverBlink AI
@neverblinkai
13h
'CPU is high and nothing is running' on ClickHouse? Background merges are one of the most common causes. That's not overhead you can turn off, it's the write path itself. Rule merges out before you blame queries. #ClickHouse
NeverBlink AI
@neverblinkai
16h
Hiring a generalist SRE and expecting deep Postgres internals is a staffing mistake with a long incident tail. SRE and DBRE share the vocabulary, SLOs, error budgets, toil. They own different parts of the stack.
NeverBlink AI
@neverblinkai
16h
The most common cause of a slow database isn't hardware. It's queries: unindexed, badly shaped, doing far more work than the question requires. Fix the query before you resize the instance.