Pricing

Overview

Stackdriver pricing gives you control over your usage and spend: 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/GB First 50 GB per project July 1, 2018
Monitoring data4 $0.2580/MB: 150–100,000 MB
$0.1510/MB: 100,000–250,000 MB
$0.0610/MB: above 250,000 MB
All GCP metrics2
First 150 MB per billing account
July 1, 2018
Monitoring API calls4 $0.01/1,000 API calls First 1 million API calls July 1, 2018
Trace ingestion3 $0.20/million spans First 2.5 million spans September 30, 2018
Trace retrieval3 $0.02/million spans First 25 million spans September 30, 2018

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 and Monitoring consoles, show you your current usage data. Based on your current usage data, you can reasonably predict your future usage and estimate your Logging and Monitoring bills.

For details, see Estimating your bills.

For Trace, you will be able to see your usage data and estimate your bills in July 2018; Trace pricing will go into effect on September 30, 2018.

Alerting on logs usage

You can create an alerting policy to inform you about when you approach or exceed your logging allotment. To quickly create one, do the following:

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

    Go to Create a Policy

  2. Click Add Condition. You will 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. Under Metric Conditions, select Metric Threshold/Rate Change/Absence. You should see a panel titled Add monitoring.v3 Condition.

  4. Fill in values as follows:

    • Under Find resource type and metric: Set Resource Type to Global and Metric to Monthly log bytes ingested.
    • Set Aggregation to sum.
    • Set Secondary Aggregation to none.
    • Set Aligner to max. The chosen metric, Monthly log bytes ingested, is a GAUGE, and each point is the month-to-date sum.
    • Set Condition triggers if to Any time series violates.
    • Set Condition to is above.
    • Fill in the Threshold (the Monthly log bytes ingested metric is measured in bytes) and duration values as you wish.

      Keep the duration as short as possible. You want to know as soon as possible that the threshold has been crossed, because the ingestion value will continue to increase until it is reset at the end of the month.

    The panel reflects your selected threshold and the recent value of the 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.

  5. Click Save Condition, which displays the Create new alerting policy panel with your completed condition. You can add additional conditions if you wish.

  6. Fill in the Notifications, Documentation, and Name sections of the alerting policy.

  7. 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 free and excluded logs.

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

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

Data retention

Logging data is retained for 30 days.

Free and excluded 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 free and excluded logs:

  • Cloud Audit Logging logs that are enabled by default are free. This includes all GCP Admin Activity audit 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 not free and do count against your free allotment. For more information, see Configuring Data Access Logs.

  • 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.

Reducing 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 do not 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 free. 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 free; API calls to query time series data are charged at a nominal rate after the free allotment limit is reached.

Finally, advanced alerting and notifications are now 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/MB: 150–100,000 MB
$0.1510/MB: 100,000–250,000 MB
$0.0610/MB: > 250,000 MB
First 150 MB 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, see Quotas & Limits.

Data retention

Monitoring data is retained for 6 weeks.

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 (Compute Engine, Kubernetes Engine, App Engine, etc.) 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.33416748MB (350,400 bytes / 1,048,576 bytes/MB)

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.005569458MB (5,840 bytes / 1,048,576 bytes/MB)

Metrics are billed accordingly:

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

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:

MB ingested Rate ($/MB)
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,063MB: 0.33416748MB for one metric * 75,000 (that is, 1,000 resources, 75 metrics)
  • Approximate cost per month: $0.00 (GCP metrics are included free)
MB ingested Rate ($/MB) 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,063MB (same as above)
  • Approximate cost per month: $6,427.55
MB ingested Rate ($/MB) 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: 418MB = 0.005569458MB for one metric * 75,000
  • Approximate cost per month: $69.14
MB ingested Rate ($/MB) 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,084MB: 0.33416748MB for one metric * 500,000
  • Approximate cost per month: $35,890.98
MB ingested Rate ($/MB) 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 simply on the number of trace spans created and retrieved.

Feature Price Free allotment per month Effective date
Trace ingestion $0.20/million spans First 2.5 million spans September 30, 2018
Trace retrieval $0.02/million spans First 25 million spans September 30, 2018

Certain limits also apply to your use of Trace; 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.)

Frequently asked questions

How much will I have to pay for using Stackdriver?

To estimate your Logging and Monitoring costs, see Estimating your bills.

For Trace, you will be able to see your usage data and estimate your bills in July 2018; pricing for Trace goes into effect on September 30, 2018.

How do I understand the details of my usage?

Several metrics make it easier than ever to 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 I associate a Stackdriver account with my project?

For a step-by-step guide to creating and using Stackdriver accounts see Managing Accounts.

What happens if I go over the free allotments?

Stackdriver projects are automatically billed for any usage over your free allotments based on the billing information you set up for your project. You do not lose any logs or metrics. To better understand your potential costs, see Estimating your bills.

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. If you send and then exclude your VPC flow logs from Logging, VPC flow logs charges apply. For more information, see the Google Cloud Platform 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.

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 and Trace, allotments and consumption are calculated per billing account. A billing account can include any number of GCP projects.

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

Send feedback about...

Stackdriver Documentation