Upcoming Pricing

What's changing

Under the new and simple Stackdriver pricing, you have control over your usage and spend, paying only for what you use.

Our free allocation lets you get started with no upfront fees or commitments. Stackdriver’s current tiered system is replaced with a single pricing structure; there are no premium features. You get the advanced alerting and notification options you need to monitor your cloud applications, as well as the flexibility to create monitoring dashboards. Some retention periods are also extended.

New Stackdriver Pricing

Feature Price1 Free allotment per month Effective date
Stackdriver Logging $0.50/GB First 50 GB/project June 30, 2018
Stackdriver Monitoring data $0.2580/MB: 150–100,000MB
$0.1510/MB: 100,000–250,000MB
$0.0610/MB: >250,000 MB
All GCP metrics2
Non-GCP metrics: <150MB
June 30, 2018
Stackdriver Monitoring API calls $0.01/1,000 API calls First 1 million API calls June 30, 2018
Stackdriver Trace ingestion $0.20/million spans First 2.5 million spans September 30, 2018
Stackdriver Trace retrieval $0.02/million spans First 25 million spans September 30, 2018

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

Estimating your future bills

The Cloud Billing Reports page, as well as the Stackdriver Logging and Monitoring consoles, show you your current usage data. Based on your current usage data, you can reasonably predict your future usage and then estimate your Stackdriver Logging and Monitoring bills, according to the new pricing and in advance of billing enforcement.

There are several ways to access your Logging and Monitoring usage data, depending on the aggregation you prefer:

  • To view Stackdriver usage by billing account:

    • From anywhere in the GCP Console, open the left-side menu and select Billing.
    • If you have more than one billing account, select Go to linked billing account to view the current project's billing account. To locate a different billing account, select Manage billing accounts and choose the account for which you'd like to see usage reports.
    • Select Reports from the left-side menu.
    • Select Group By > SKU from the right-side menu. This menu may be hidden; you can access it by clicking the Show Filters button at the top right of the console.
    • Select Log Volume (Stackdriver Logging usage), Metric Volume, and Monitoring API Requests (Stackdriver Monitoring usage) under the SKUs drop-down menu. You can also select just one of these SKUs if you do not wish to group your usage data.
    • You see your usage data, filtered by the SKUs you selected, in the legends under the stacked line chart, as shown below:

    Billing legends data

  • To view detailed Stackdriver usage in Metrics Explorer:

    • Go to the Monitoring console:

    Go to Monitoring console

    • Select Resources > Metrics Explorer.
    • Under Find resource type and metric, select from the following metrics:
    • Use the Filter, Group By, and Aggregation menus to see usage data by project, if you have multiple projects in your account. You can also use these menus to filter or group by resource or metric labels.
    • You see your usage data, filtered by the metrics you selected, in the legends under the stacked line chart. To learn more about filtering and aggregations in the Metrics Explorer, see Selecting metrics.
  • To view Stackdriver Logging usage by resource type:

    • Go to the Logging console:

    Go to Logging Console

    • Select Logs ingestion in the left-hand column.
    • You see your usage data for the last month and the current month to date, per resource type, in the Logs Ingestion table.
    • Optional: If you click See Bill under Last month's ingested logs volume in the top navigation, you go to the Cloud Billing Reports page, where you can drill down into project-level usage data.
    • Optional: If you want to view this per-resource-type usage data as a time series, click on the overflow menu at the far right of each table entry and select View detailed usage in Metrics Explorer. To learn more about filtering and aggregations in the Metrics Explorer, see Selecting metrics.
  • To view Stackdriver Monitoring usage by monitored project and metric domain:

    • Go to the Monitoring console:

    Go to Monitoring console

    • Select Account Settings from the drop-down menu in the GCP project selector at the top of the page.
    • Select Resource Usage in the left-hand column.
    • You see your usage data for the last month and the current month to date in the Metrics Ingested table.
    • Optional: If you click View Bill to the right of a project name, you go to the Cloud Billing Reports page, where you can drill down into project-level usage per billing account.

Once you have the usage data you want, you can estimate your future bill in two ways:

  • Refer to the New Stackdriver Pricing overview: Compare your current usage data with the prices found in this table to get a reasonable approximation of your future Stackdriver bills.
  • Use the Stackdriver Pricing Calculator:
    • Select the Upcoming Model tab, which reflects the prices found in the new Stackdriver pricing model.
    • Add your current Monitoring usage data to the Metrics section and click Add to estimate.
    • Add your current Logging usage data to the Logs section and click Add to estimate.
    • You see estimates of your future Stackdriver bills to the right of the calculator.

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

Stackdriver Logging details

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

Feature Price1 Free allotment per month Effective date
Stackdriver Logging $0.50/GB First 50 GB/project June 30, 2018

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

Data retention

In the new pricing model, Stackdriver Logging data is retained for 30 days.

Free and excluded logs

Stackdriver Logging charges for the volume of log data that exceeds the free monthly logs allotment. All logs received by Stackdriver 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. Stackdriver 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.

Controlling Stackdriver Logging costs

To review the amount of log data coming into your project, see the Stackdriver Logging Logs Ingestion page:

Go to the Logs Ingestion page

To estimate your Stackdriver Logging costs, according to the new pricing and in advance of billing enforcement, see Estimating your future bills.

Reducing your logs usage

You can take advantage of two free services in Stackdriver 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. You can use the same advanced filter used in queries to exclude only specific logs. You can also choose to sample certain messages so that only a sampled percentage of the messages appear in the Stackdriver 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 Stackdriver Logging. For instructions on how to exclude logs, see Excluding Logs.

Logs export lets you copy log entries out of Stackdriver Logging before they are discarded because they have reached the end of their retention period, because you have exceeded your logs allotment, or because 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.

Stackdriver 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 (both custom metrics and logs-based metrics), 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 Price1 Free allotment per month Effective date
All GCP metrics Free Unlimited June 30, 2018
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 June 30, 2018
API usage (read) $0.01/1,000 API calls First 1 million API calls June 30, 2018
API usage (write) Free Unlimited June 30, 2018

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

Data retention

Stackdriver Monitoring data will continue to be 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.

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

Controlling Stackdriver Monitoring costs

To estimate your Stackdriver Monitoring costs, according to the new pricing and in advance of billing enforcement, see Estimating your future bills.

Stackdriver Trace details

Stackdriver Trace charges simply on the number of trace spans created and retrieved.

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

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

Controlling Stackdriver Trace costs

You will be able to see your Stackdriver Trace usage data and estimate your bills in July 2018; the new pricing for Stackdriver Trace will go into effect on September 30, 2018.

Frequently asked questions

How much will I have to pay for using Stackdriver?

To estimate your Stackdriver Logging and Stackdriver Monitoring costs, according to the new pricing and in advance of the June 30, 2018 billing enforcement, see Estimating your future bills.

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

How do I associate a Stackdriver account with my project?

With your project selected in the Cloud Platform Console, choose Stackdriver > Monitoring and follow the instructions to create a Stackdriver account or to add your project to an existing account. For more information, see Creating a Stackdriver account.

What happens if I go over the free allotments?

Stackdriver accounts 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.

See Controlling Logging Costs and Controlling Monitoring Costs for more details.

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 Stackdriver Logging See Controlling Logging Costs 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 Stackdriver Logging or not.

Pricing notes

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

2 GCP metrics at the current highest resolution, 1 datapoint/minute, and below are free. In the future, higher resolution metrics may incur a charge.

Send feedback about...

Stackdriver Documentation