LOGIKASign in
On this page

Logika and Google Cloud Observability: pricing compared

These figures are our best estimates from each vendor's public prices, some of which are complicated to calculate. They cover only what the vendor bills for storing and querying observability or analytics data. Logika is one product that covers both, and its price includes its integration with your coding agent and the workflow around it: your agent can wake as soon as something breaks, and even push a fix to production by the time you read the email saying it did.

Prices from Google Cloud Observability's public pricing pages, as read on 27 October 2026, in US dollars per month excluding tax. They are estimates from published list rates, not quotes: discounts, commitments and the way you use a product change the bill. Logika's side is priced from its own tiers, below.

The numbers

Everyday use here is one engineer sending 50 GB a month; each situation below changes one or two of its inputs.

SituationGoogle Cloud ObservabilityLogikaRatio
Everyday use
One engineer sending 50 GB a month, with host metrics sent as OpenTelemetry or Prometheus samples. Logs cost $0.50 per GiB after 50 GiB free with 30 days and querying included, and Google bills each entry with its metadata, which we assume adds 400 bytes to each 1 KB record; spans are $0.20 per million after 2.5 million free. Seats, searches and alerts are not billed today.
$6.06$14Solo0.4×
Host metrics through the Ops Agent
The same 300 series on each of two hosts collected by the Ops Agent, Google's default VM agent. Those metrics are metered by bytes (8 bytes a point) at $0.258 per MiB after 150 MiB free, instead of $0.06 per million samples.
$16.82$14Solo1.2×
A metric tagged by customer
A request counter gets a customer label: 200 customers × 10 endpoints × 3 status codes make 6,000 series. Sent as samples once a minute, each series adds 43,200 samples a month at $0.06 per million.
$21.61$14Solo1.5×
A 3-day traffic spike
Three days at 10× the normal volume add 45 GB. Log ingest is billed at $0.50 per GiB and spans at $0.20 per million with no spending cap, so the extra volume is billed in full.
$16.53$10.56–$16.53$14Solo1.2×

Everyday use here is five engineers sending 200 GB a month; each situation below changes one or two of its inputs.

SituationGoogle Cloud ObservabilityLogikaRatio
Everyday use
Five engineers sending 200 GB a month, with host metrics sent as OpenTelemetry or Prometheus samples. Logs cost $0.50 per GiB after 50 GiB free with 30 days and querying included, and Google bills each entry with its metadata, which we assume adds 400 bytes to each 1 KB record; spans are $0.20 per million after 2.5 million free. Seats, searches and alerts are not billed today.
$63.58$44.95–$63.58$49Team1.3×
Host metrics through the Ops Agent
The same 300 series on each of five hosts collected by the Ops Agent, Google's default VM agent. Those metrics are metered by bytes (8 bytes a point) at $0.258 per MiB after 150 MiB free, instead of $0.06 per million samples.
$149$130–$149$49Team3.0×
A metric tagged by customer
A request counter gets a customer label: 2,000 customers × 10 endpoints × 3 status codes make 60,000 series. Sent as samples once a minute, each series adds 43,200 samples a month at $0.06 per million.
$219$200–$219$49Team4.5×
A 3-day traffic spike
Three days at 10× the normal volume add 180 GB. Log ingest is billed at $0.50 per GiB and spans at $0.20 per million with no spending cap, so the extra volume is billed in full.
$140$105–$140$49Team2.9×

Everyday use here is 15 engineers sending 500 GB a month; each situation below changes one or two of its inputs.

SituationGoogle Cloud ObservabilityLogikaRatio
Everyday use
15 engineers sending 500 GB a month, with host metrics sent as OpenTelemetry or Prometheus samples. Logs cost $0.50 per GiB after 50 GiB free with 30 days and querying included, and Google bills each entry with its metadata, which we assume adds 400 bytes to each 1 KB record; spans are $0.20 per million after 2.5 million free. Seats, searches and alerts are not billed today.
$197$150–$197$149Business1.3×
Host metrics through the Ops Agent
The same 300 series on each of 12 hosts collected by the Ops Agent, Google's default VM agent. Those metrics are metered by bytes (8 bytes a point) at $0.258 per MiB after 150 MiB free, instead of $0.06 per million samples.
$455$408–$455$149Business3.1×
A metric tagged by customer
A request counter gets a customer label: 10,000 customers × 10 endpoints × 3 status codes make 300,000 series. Sent as samples once a minute, each series adds 43,200 samples a month at $0.06 per million.
$974$928–$974$149Business6.5×
A 3-day traffic spike
Three days at 10× the normal volume add 450 GB. Log ingest is billed at $0.50 per GiB and spans at $0.20 per million with no spending cap, so the extra volume is billed in full.
$388$300–$388$149Business2.6×

How these are priced

How Google Cloud Observability prices

Google Cloud Observability has no plans, no seats and no query fees. Each product is metered by volume, as listed on its pricing page:

  • Cloud Logging is $0.50 per GiB, which includes 30 days of storage and all querying. The first 50 GiB a month are free for each project. Keeping logs longer than 30 days is $0.01 per GiB-month.
  • What a GiB of logs is. Google bills the stored log entry, not only the line your application wrote. Its log volume documentation says the billable volume "includes bytes that are required for serialization and metadata": the resource labels, log name, timestamps, severity and insert id Google adds to every entry. It publishes no size for that metadata; its own example shows Kubernetes stdout entries of 700 to 900 bytes each. We assume 400 bytes an entry on top of each 1 KB record, and show the bill without it as the low end of the range.
  • Cloud Trace is $0.20 per million spans after 2.5 million free a month per billing account. Traces are kept 30 days.
  • Cloud Monitoring bills metrics in two ways. Metrics sent as Prometheus or OpenTelemetry (OTLP) samples are $0.06 per million samples. Metrics from the Ops Agent, custom metrics and metrics written through the Monitoring API are billed by bytes: $0.258 per MiB after 150 MiB free, counting 8 bytes for each point.
  • Alerting is free today. From 1 September 2027 it is billed at $0.35 per metric referenced a month plus $0.50 per million points returned; our figures do not include that yet.

What arrives by default also counts. On GKE, system and workload logs are collected without setup, and the Ops Agent on a virtual machine collects system logs as well as its byte-metered metrics; Google publishes no typical volume for either, so our figures count only the application's own records. Seats, Log Analytics SQL queries from the console and reads through the Cloud Logging API are not billed, so a coding agent reading logs adds nothing to the bill. Google publishes no spending cap for these products. Our everyday figure sends host metrics as OTLP samples, which is the cheaper of the two ways.

Where the bill grows

Host metrics through the Ops Agent. The Ops Agent is Google's default agent for virtual machines, and its metrics are billed by bytes. Five hosts reporting 300 series a minute write about 494 MiB a month; after the free 150 MiB, that is $0.258 per MiB, more than twenty times the same metrics sent as OTLP samples.

A metric tagged by customer. A request counter with a customer label, for 2,000 customers, 10 endpoints and 3 status codes, makes 60,000 series. Sent as samples once a minute, that is about 2.6 billion samples a month at $0.06 per million. Billed by bytes instead, it would cost many times more.

A 3-day traffic spike. Logs are $0.50 per GiB, metadata included, and spans $0.20 per million, with no cap, so three days at ten times the normal volume are billed in full.

On Logika none of these adds a line to the bill: metric data points are stored raw and count toward the same quota as logs and spans, so many of them shorten the history kept or need a larger tier (the figures here leave their bytes out), and a spike shortens the history kept instead of adding a charge, while ingest above about five times the tier's average rate is throttled and partly dropped.

Reported bills

Wrote that its Cloud Logging cost was about $800 a day, from GKE container logs and load-balancer access logs, and that exclusions and sinks halved it within days.

about $800 a day · Reported by Harness, in its engineering blog, July 2020

Said they had recently found their logging on Google Cloud was costing $3,000 a month.

$3,000 a month · Reported by a Hacker News commenter, June 2022

Reported that successful-request access lines from uvicorn were about 88% of a production deployment's Cloud Logging volume, costing about EUR 1,100 a month.

about EUR 1,100 a month · Reported by a GitHub issue in the open-wearables project, July 2026

Reported that routine messages logged at warning level made about 20 GiB a day of ingest, costing about $10 to $20 a day.

about $10 to $20 a day · Reported by a GitHub issue in the orakl project, September 2026

Said Cloud Monitoring charges ran above $100 a day for several days with no changes on their side, and that support adjusted the bill.

over $100 a day · Reported by a Google Developer forum post, February 2024

What this comparison leaves out

Google Cloud collects metrics and logs from its own services for free or without setup, and offers dashboards, uptime checks, Log Analytics in SQL, error reporting and profiling. Logika also queries its logs in SQL and raises errors as issues, but has no dashboards, uptime checks or profiling, and stores metrics only as raw data points for queries, with no dashboards or alerts on them; it keeps 30 days of raw history at most. Google Cloud Observability is cheaper than Logika for one person: a solo project's logs fit the free 50 GiB a project. For a team of five, the bill depends on the metadata Google adds to each entry, which it does not size: with none it is a little cheaper than Logika, and with the 400 bytes an entry we assume it costs more. Splitting logs across projects, each with its own 50 GiB, lowers the bill further.

Sources

Read on 27 October 2026. Prices change, and we may have misread one. If you find an error, write to support@logika.host and we will correct it.

Google Cloud Observability is a trademark of its owner. Logika is not affiliated with, endorsed by or sponsored by Google Cloud Observability.