Build a ClickHouse analytics pipeline on Google Axion
Introduction
Get started with ClickHouse on Google Cloud C4A Arm virtual machines
Create a Firewall Rule on GCP
Create a Google Axion C4A Arm virtual machine on GCP
Set up Pub/Sub and IAM for ClickHouse on Google Axion
Install ClickHouse
Establish a ClickHouse baseline on Arm
Build a Dataflow streaming ETL pipeline to ClickHouse
Benchmark ClickHouse on Google Axion processors
Next Steps
Build a ClickHouse analytics pipeline on Google Axion
Introduction
Get started with ClickHouse on Google Cloud C4A Arm virtual machines
Create a Firewall Rule on GCP
Create a Google Axion C4A Arm virtual machine on GCP
Set up Pub/Sub and IAM for ClickHouse on Google Axion
Install ClickHouse
Establish a ClickHouse baseline on Arm
Build a Dataflow streaming ETL pipeline to ClickHouse
Benchmark ClickHouse on Google Axion processors
Next Steps
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Select the
c4a-standard-4 machine type (4 vCPUs, 16 GB) in the Google Cloud console when creating the instance. This matches the configuration used in the steps.Open inbound TCP port 8123 by creating a firewall rule in your VPC. This exposes the ClickHouse endpoint required by the path.
Confirm that the logs-topic exists under Pub/Sub → Topics and keep encryption and retention at their defaults. Complete the IAM setup so Dataflow and the VM can access Pub/Sub.
Install the Google Cloud CLI on the VM. Use it to authenticate to GCP, publish Pub/Sub messages, and submit Dataflow jobs.
Verify that events published to Pub/Sub arrive in ClickHouse and then run baseline and analytical queries. Capture query latency metrics, including p95.