Pricing

Overview

Stackdriver pricing gives you control over your usage and spending: you pay only for what you use.

Our free usage allotments let you get started with no upfront fees or commitments. There are no longer any premium-only features or allotments.

Stackdriver Pricing

Feature Price1 Free allotment per month Effective date
Logging3 $0.50/GiB First 50 GiB per project July 1, 2018
Monitoring data4 $0.2580/MiB: 150–100,000 MiB
$0.1510/MiB: 100,000–250,000 MiB
$0.0610/MiB: above 250,000 MiB
All [GCP metrics]2
First 150 MiB per billing account
July 1, 2018
Monitoring API calls4 $0.01/1,000 API calls First 1 million API calls July 1, 2018
Trace ingestion5 $0.20/million spans First 2.5 million spans November 1, 2018
Trace spans scanned5 $0.02/million spans First 25 million spans To be announced

See Pricing Notes at the end of this page.

For details on the Stackdriver products' features and pricing, see these sections:

Controlling your costs

The Cloud Billing Reports page, as well as the Logging, Monitoring, and Trace consoles, show your current usage data. Based on your current usage data, you can reasonably predict your future usage and estimate your Stackdriver bills.

For details, see estimating your bills.

Alert on Stackdriver usage

You can create an alerting policy that monitors your Stackdriver usage and alerts you when you approach the threshold for billing. The example illustrates an alerting policy for Stackdriver Logging usage. If you want to create an alerting policy for Stackdriver Trace usage, replace Monthly log bytes ingested with Monthly trace spans ingested.

For example, to create an alerting policy for Logging usage, do the following:

  1. In the Stackdriver Console, go to Alerting > Create a Policy.

    Go to Create a Policy

  2. Click Add Condition. You see a note indicating that you are using the new UI for conditions or an invitation to try it. You must use the new condition editor to create this alerting policy; see Managing Alerting Policies for details.

  3. Click Add Condition. A note indicating that you are using the new UI for conditions displays or you see an invitation to try it. You must use the new condition editor to create this alerting policy. See Managing Alerting Policies for details.

  4. Under Metric Conditions, select Metric Threshold/Rate Change/Absence.

  5. In the Add monitoring.v3 Condition panel, fill in the following values:

    • In the Find resource type and metric field, enter Global and then enter Monthly log bytes ingested. This metric is a gauge, and each point is the month-to-date sum.
    • Under Aggregation, fill in the following values:

      • From the Aligner drop-down list, select max.
      • From the Reducer drop-down list, select sum.
      • In the Alignment Period box, enter 60.
    • From the Condition triggers if drop-down list, select Any time series violates.

    • From the Condition drop-down list, select is above.

    • Fill in the Threshold.

    • From the For drop-down list, select the duration. The duration should be at least 30 minutes. This is the minimum duration recommended by Stackdriver Logging for the Monthly log bytes ingested metric.

    Billing legends data

    Note that the default view is 1 hour. If there is no data point in the last hour, you might not see a line on the chart. Zoom out to 1d (1 day) or 1w (1 week) to see the line graph.

  6. Click Save Condition. The Create new alerting policy panel displays your completed condition.

  7. Complete the Notifications, Documentation, and Name sections of the alerting policy.

  8. Click Save Policy.

For more information on creating alerting policies, see Introduction to Alerting.

Logging details

For pricing purposes, Logging measures the quantity of log data loaded and processed by Logging or other GCP services. This pricing applies to all log data except for non-chargeable logs.

Feature Price 1, 3 Free allotment per month
Logging $0.50/GiB First 50 GiB per project

Certain limits also apply to your use of Logging; for more details, including data retention periods, see Quotas & Limits.

Non-chargeable logs

Logging charges for the volume of log data that exceeds the free monthly logs allotment. All logs received by Logging count towards the logs allotment limit, except for the following:

  • Cloud Audit Logging logs that are enabled by default are non-chargeable. This includes all GCP Admin Activity audit logs, System Event logs plus GCP Data Access audit logs from Google BigQuery only.

    You can configure your project to receive Data Access audit logs beyond those that are provided by the default configuration, but those logs are chargeable and do count against your free allotment. For more information, see Configuring Data Access Logs.

  • Access Transparency logs are non-chargeable. See the Access Transparency logs documentation for more information.

  • Excluded logs. Logging gives you the ability to manually identify and exclude less important log entries from your project, thus reducing your usage. For more information, see Excluding Logs.

Reduce your logs usage

You can take advantage of two free services in Logging to reduce your logs usage and preserve log entries that might otherwise be lost:

Logs exclusion lets you completely exclude log entries matching a specific filter or sample certain messages so that only a sampled percentage of the messages appear in the Logging Logs Viewer. Excluded log entries don't count against your allotment. You can export your excluded log entries to retain access to them outside of Logging. For instructions on how to exclude logs, see Excluding Logs.

Logs export lets you export log entries out of Logging before they are discarded because either you have exceeded your logs allotment or you have marked the log entries for exclusion. There is no Stackdriver charge for exporting logs, but the services that receive your exported logs charge you for the usage. For instructions how to export logs, see Exporting Logs.

You can also immediately disable all logs ingestion. For instructions, see Stopping all logs ingestion.

Monitoring details

Metric data from GCP metrics is non-chargeable.

Metric data from non-GCP metrics is priced by volume on a sliding scale. Non-GCP metrics include agent metrics, user-defined metrics (custom.googleapis.com/..., external.googleapis.com/..., logging.googleapis.com/user/...), and AWS metrics.

API calls to write time series data are non-chargeable; API calls to query time series data are charged at a nominal rate after the free allotment limit is reached.

Uptime checks, including uptime checks metric data, advanced alerting, and notifications are non-chargeable and available to everyone.

Feature Price 1, 4 Free allotment per month
All GCP metrics2 Free Unlimited
Agent metrics,
User-defined metrics,
and AWS metrics
$0.2580/MiB: 150–100,000 MiB
$0.1510/MiB: 100,000–250,000 MiB
$0.0610/MiB: > 250,000 MiB
First 150 MiB per billing account
API usage (read) $0.01/1,000 API calls First 1 million API calls
API usage (write) Free Unlimited

Certain limits also apply to your use of Monitoring; for more details, including data retention periods, see Quotas & Limits.

Pricing examples

The following examples illustrate how to get an estimate of costs for collecting metric data. These are intended to illustrate the new metrics pricing; for comprehensive estimates, use the Pricing Calculator.

The basic scenario is this: You have some number of monitored resources, such as Compute Engine, Google Kubernetes Engine, or App Engine, that are writing data from some number of metrics each month.

The variables across the scenarios include:

  • The number of resources.
  • The number of metrics.
  • Whether the metrics are GCP metrics or not.
  • The rate at which the metric data is written.

Common background

Each metric datapoint written is assumed to be 8 bytes in size, except each distribution point is 80 bytes.

There are roughly 730 hours (365 days / 12 months * 24 hours) in a month, or 43,800 minutes.

For one metric writing data at the rate of 1 datapoint/minute for one month:

  • Total datapoints is: 43,800
  • Total volume ingested is:
    • 350,400 bytes (43,800 datapoints * 8 bytes)
    • 0.33416748 MiB (350,400 bytes / 1,048,576 bytes/MiB)

For one metric writing data at the rate of 1 datapoint/hour for one month:

  • Total datapoints is: 730
  • Total volume ingested:
    • 5,840 bytes (730 datapoints * 8 bytes)
    • 0.005569458 MiB (5,840 bytes / 1,048,576 bytes/MiB)

Metrics are billed accordingly:

Feature Rate ($/MiB) Free allotment per month
All GCP metrics Free Unlimited
Agent metrics,
User-defined metrics,
and AWS metrics
$0.2580/MiB: 150–100,000 MiB
$0.1510/MiB: 100,000–250,000 MiB
$0.0610/MiB: > 250,000 MiB
First 150 MiB

Another way to look at the pricing for non-GCP metrics is by accumulating ingestion, which is useful in understanding how costs per month are computed:

MiB ingested Rate ($/MiB)
The first 150 0.00
The next 99,850 0.258
The next 150,000 0.151
Above 250,000 0.061

Examples

Scenario 1: You have 1,000 resources, each writing 75 metrics. These are GCP metrics only, writing at the rate of 1 datapoint/minute.

  • Monthly ingestion: 25,063 MiB: 0.33416748 MiB for one metric * 75,000 (that is, 1,000 resources, 75 metrics)
  • Approximate cost per month: $0.00 (GCP metrics are included free)
MiB ingested Rate ($/MiB) Cost ($)
unlimited 0.00 $0.00
Total 25,063 $0.00

Scenario 2: You have 1,000 resources, each writing 75 metrics. These are non-GCP metrics, writing at the rate of 1 datapoint/minute.

  • Monthly ingestion: 25,063 MiB (same as above)
  • Approximate cost per month: $6,427.55
MiB ingested Rate ($/MiB) Cost ($)
150 0.00 $0.00
24,913 0.258 $6,427.55
Total 25,063 $6,427.55

Scenario 3: You have 1,000 resources, each writing 75 metrics. These are non-GCP metrics, writing at the rate of 1 datapoint/hour.

  • Monthly ingestion: 418 MiB = 0.005569458 MiB for one metric * 75,000
  • Approximate cost per month: $69.14
MiB ingested Rate ($/MiB) Cost ($)
150 0.00 $0.00
267 0.258 $69.14
Total 417 $69.14

Scenario 4: You have 1 resource writing 500,000 metrics. These are non-GCP metrics, writing at the rate of 1 datapoint/minute.

  • Monthly ingestion: 167,084 MiB: 0.33416748 MiB for one metric * 500,000
  • Approximate cost per month: $35,890.98
MiB ingested Rate ($/MiB) Cost ($)
150 0.00 $0.00
99,850 0.258 $25,761.30
67,084 0.151 $10,129.68
Total 167,084 $35,890.98

Trace details

Trace charges are based on the number of trace spans ingested and scanned:

Feature Price5 Free allotment per month Effective date
Trace ingestion $0.20/million spans First 2.5 million spans November 1, 2018
Trace spans scanned $0.02/million spans First 25 million spans To be announced

Certain limits apply to the use and retention of Trace data. For more details, see Quotas & Limits.

Pricing examples

  • If you ingest 2 million spans in a month, your cost is $0. (Your first 2.5 million spans ingested in a month are free.)
  • If you ingest 14 million spans in a month, your cost is $2.30. (Your first 2.5 million spans ingested in a month are free. The remaining spans' cost is calculated as 11.5 million spans * $0.20 = $2.30.)
  • If you ingest 1 billion spans in a month, your cost is $199. (Your first 2.5 million spans in a month are free. The remaining spans' cost is calculated as 997.5 million spans * $0.20 = $199.)

Monitor your trace usage

To view the total Trace spans ingested for the current month and the previous month, go to Trace Overview. For more information, see view your billing data.

To view the number of Trace spans ingested, as a function of time, see view detailed Stackdriver usage in Metrics Explorer for details.

You can also create an alerting policy on the metric Monthly trace spans ingested.

Reduce your trace usage

To control Trace span ingestion volume, you can manage your trace sampling rate to balance how many traces you need for performance analysis with your cost tolerance.

For high-traffic systems, most customers can sample at 1 in 1,000 transactions, or even 1 in 10,000 transactions, and still have enough information for performance analysis.

Sampling rate is configured with the Stackdriver Trace client libraries.

Frequently asked questions

How much will I have to pay for using Stackdriver?

To estimate your Stackdriver costs, see Estimating your bills.

How do I understand the details of my usage?

Several metrics let you drill into and understand your logs and metrics volume using Metrics Explorer. See View detailed Stackdriver usage in Metrics Explorer for details.

If you’re interested in an even deeper analysis of your logs usage, you can analyze your log volume using logs-based metrics in Cloud Datalab. See this GCP blog post for more information.

How do Workspaces affect billing?

For the most part, Workspaces don't affect billing. Logs and metrics are charged at the GCP project that receives the data, whether or not there is an associated Workspace.

In the case of monitoring AWS accounts, you must use a Workspace to get an AWS connector project for the AWS account. The connector project holds the logs and monitoring data for the AWS account.

What happens if I go over the free allotments?

Stackdriver projects are automatically billed for any usage over your free allotments. You don't lose any logs or metrics. To better understand your potential costs, see Estimating your bills.

You can create an alerting policy that monitors Stackdriver usage and notifies you when you approach the threshold for billing.

I have a large number of GCP logs in my project(s) that I do not use. I am concerned about charges for these logs. How do I avoid this?

You can exclude logs to control which logs are ingested into Logging. See Reducing your logs usage for details.

Will services that send logs to my project receive an error if logs are excluded?

No. Services that send log entries cannot determine whether the log entries are ingested into Logging or not.

Will I be charged twice for Virtual Private Cloud flow logs?

If you send your VPC flow logs to Logging, VPC flow logs generation charges are waived, and only Logging charges apply. However, if you send them and then exclude your VPC flow logs from Logging, VPC flow logs charges apply. For more information, see the GCP Pricing Calculator for Networking.

Pricing notes

1 For pricing purposes, all units such as MB and GB represent binary measures. For example, 1 MB is 220 bytes. 1 GB is 230 bytes. These binary units are also known as mebibyte (MiB) and gibibyte (GiB), respectively. Note also that MB and MiB, and GB and GiB, are used interchangeably.

2 There is no charge for [GCP metrics] that are measured at up to 1 datapoint per minute, the current highest resolution. In the future, metrics measured at higher resolutions might incur a charge.

3 In Stackdriver Logging, allotments and consumption are calculated per GCP project.

4 In Stackdriver Monitoring, allotments and consumption are calculated per billing account. A billing account can include any number of GCP projects.

5 In Stackdriver Trace, allotments and consumption are calculated per billing account. A billing account can include any number of GCP projects. Stackdriver Trace span pricing doesn't apply to spans generated by App Engine Standard. These spans are non-chargeable. Trace spans created by instrumentation you add to your App Engine Standard application are subject to ingestion charges.

Was this page helpful? Let us know how we did:

Send feedback about...

Stackdriver Documentation