// infrastructure / google-cloud

Graylog on Google Cloud

For teams on Google Cloud, Graylog fits naturally on Compute Engine inside your VPC — with GKE and VM logs shipped to it privately.

We deploy Graylog on Compute Engine VMs across zones in a region, with a passthrough Network Load Balancer for TCP and UDP inputs and an HTTPS load balancer or internal access for the web interface.

Running Graylog on VMs rather than inside GKE keeps stateful components simpler to operate. Collection from GKE clusters is handled by DaemonSet collectors shipping over private networking.

// reference build

How a Graylog environment on Google Cloud is typically built

compute

Compute

Machine types sized per role, with memory-heavy shapes for search nodes and no shared-core types for sustained ingest.

storage

Storage

Balanced or SSD Persistent Disk, or Hyperdisk where independent throughput tuning is needed.

networking

Networking

Private VPC subnets, firewall rules per tier using network tags or service accounts, Cloud NAT for egress.

load balancing

Load balancing

Internal or external passthrough Network Load Balancers for TCP/UDP inputs.

backups

Backups

Cloud Storage buckets for snapshots and MongoDB backups, with retention policies.

automation

Automation

Terraform with the Google provider, instance templates, Ansible for configuration.

Google Cloud is a trademark of its respective owner. We are an independent provider and not an official Google Cloud partner. Provider capabilities change; we verify current features and pricing during design.

Planning Graylog on Google Cloud?

Send us your ingest volume and retention requirements and we will outline a topology and sizing for Google Cloud.