# ClickHouse Bindplane provides blueprints to preprocess and optimize logs and events for ingestion into ClickHouse (and ClickStack). These pipelines help you reduce cardinality, mask PII, deduplicate records, and normalize fields so your data is clean, cost-effective, and query-ready. ### Log hygiene for event storage Use the **Process Logs for ClickHouse** blueprint to build a general-purpose log cleaning pipeline for JSON logs from applications, microservices, and cloud platforms. It parses structured data, filters verbosity, masks PII, removes high-cardinality fields, deduplicates records, and normalizes fields. [See Log Hygiene for Event Storage in ClickHouse for details](#log-hygiene-for-event-storage). ### Pre-processing HTTP logs for monitoring Use the **Process HTTP Logs for ClickHouse** blueprint to normalize HTTP fields, mask sensitive data, reduce high-cardinality identifiers (e.g. request IDs, session tokens), filter health checks, and deduplicate errors. Optimized for web server and application logs. [See Pre-processing HTTP Logs for Monitoring in ClickStack for details.](#pre-processing-http-logs-for-monitoring) {% embed url="" %} ### Storing security events Use the **Process Security Logs for ClickHouse** blueprint to preserve authentication and security events while masking PII (via hashing for forensic use), normalizing to ECS, and deduplicating alerts. Suited for SIEM, cloud audit logs, and identity providers. [See Storing Security Events in ClickHouse using Bindplane for details.](/how-to-guides/partner-integrations/clickhouse/storing-security-events-in-clickhouse-using-bindplane.md) ### Formatting Kubernetes cluster events Use the **Process Kubernetes Cluster Events for ClickHouse** blueprint to filter controller noise, remove high-cardinality object UIDs, map event types to severity, and deduplicate warnings so cluster-level events are efficient to store and query in ClickHouse. [See Formatting Cluster Level Events from Kubernetes for Querying in ClickStack for details.](#formatting-kubernetes-cluster-events) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.bindplane.com/how-to-guides/partner-integrations/clickhouse.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.