Observability
Observability on ClickHouse: why a columnar database changes the game
Why more and more observability platforms store logs, traces and metrics in ClickHouse: columnar storage, compression, SQL, costs, and an overview of the …
Guides & insights
Observability
Why more and more observability platforms store logs, traces and metrics in ClickHouse: columnar storage, compression, SQL, costs, and an overview of the …
Observability
ClickHouse's official observability stack: all-in-one installation, the HyperDX interface (search, traces, sessions, dashboards), correlation between sign…
Observability
Send logs and traces to ClickHouse with the OpenTelemetry exporter, understand the table schema, write analytical SQL queries, manage retention (TTL) and …
Observability
Operate ClickHouse for telemetry (replication, disks, merges, object storage, monitoring) and compare SigNoz, ClickStack, the Grafana stack and Elastic to…
Observability
Production checklist for an observability platform on ClickHouse: OpenTelemetry instrumentation, batched ingestion, retention, replication, security and c…
Observability
Link browser requests to back-end traces: TracingInstrumentation, traceparent header propagation, CORS, and navigating in Grafana from the session to the …
Observability
Install CrowdSec with packages or Docker, understand its files, declare the logs to read, enroll the console and deploy several servers.
Observability
The Hub, collections, the parser pipeline and scenarios: install, understand with cscli explain, write your own scenario and test it in simulation.
Observability
Understanding CrowdSec bouncers: where to block, live and stream modes, API keys, decisions API, and setting up the nftables or iptables firewall bouncer.
Observability
Manage decisions with cscli, adapt block duration and type with profiles, avoid false positives with allowlists and enable the AppSec WAF.
Observability
Monitoring CrowdSec: cscli metrics, banned IPs, detected attacks, volume blocked by bouncers, Prometheus metrics, Grafana, alerts and notifications.
Observability
Good habits for running CrowdSec in production: LAPI, keys, false positives, database, upgrades and backups.
Learning never stops