This page describes the pricing of Google Stackdriver, the integrated monitoring, logging, and diagnostics suite for applications running on Google Cloud Platform (GCP) and Amazon Web Services (AWS).

Storage and network usage are calculated in binary gigabytes (GB), where 1GB is 230 bytes. This unit of measurement is also known as a gibibyte (GiB). Similarly, 1TB is 240 bytes, i.e. 1024 GB.

Stackdriver account service tiers

Stackdriver accounts control access to Stackdriver features and billing. A Stackdriver account can be a single GCP project or it can contain multiple GCP projects and AWS accounts. You can have any number of Stackdriver accounts.

Stackdriver offers Basic and Premium service tiers for each Stackdriver account. There are no charges for the Basic Tier, but there are some limits to Stackdriver's functionality.

The following table shows the features available in the Basic and Premium service tiers:

Feature Basic Tier Premium Tier
Price Free $8.001 per chargeable resource2 per month (prorated hourly)
Supported clouds GCP only GCP and AWS
Logs allotment3 50 GB per project per month 50 GB per project per month plus 14.25 MB per chargeable resource2 per hour
Logs retention:
 Admin activity audit logs
 Data access audit logs
 Non-audit logs

400 days
7 days
7 days

400 days
30 days
30 days
User-defined metric allotment See Quotas See Quotas
Metric data retention 6 weeks 6 weeks
Alerting policies Some limitations4 No limitations
Stackdriver VM agents Logging agent only Logging agent and Monitoring agent
Stackdriver Error Reporting, Stackdriver Debugger, and Stackdriver Trace For applications on GCP For applications on GCP and AWS (if supported)
Cloud Console Mobile App Included Included

1 If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
2 Chargeable resources include VM instances and other listed resources. For more details, see Chargeable resources.
3 Your logs are free up to the allotment. Audit logs that are enabled and ingested by default are always free and do not count against the allotment. For more details, see Log allotments and overage charges.
4 Alerting and notification limitations.

Free trial and start of billing

Every new Stackdriver account receives a 30-day free trial of the Premium service tier.

Before your account's trial period expires, you must choose a service tier by upgrading to the Premium Tier or allowing your account to revert to the Basic Tier:

  • If you choose the Premium Tier, you are billed for your chargeable resources, starting after the free trial expires.

  • If you choose the Basic Tier, you are not billed. However, you lose access to Premium Tier services, including AWS monitoring and logging, the longer logs retention period, and the use of the Monitoring agent.

For more information, see Service tiers and Frequently asked questions on this page.

Chargeable resources

Resources are chargeable only if they are in a running or runnable state.

In the Premium Tier, your Stackdriver account is charged $8.00 per month, prorated hourly, for the following resources in the GCP project(s) and AWS account(s) associated with your Stackdriver account.

To estimate the Premium Tier pricing for your own system, use the Stackdriver Pricing Calculator.

GCP chargeable resources

  • Each App Engine standard environment instance (running, not idle)
  • Each Compute Engine VM instance
  • Each Container Engine node instance in a cluster
  • Each Cloud SQL instance

AWS chargeable resources

  • Each Amazon EC2 VM instance
  • Each Elastic Load Balancer (ELB)
  • Each Elasticache cluster
  • Each RDS instance
  • Ten (10) SQS queues
  • Each SNS topic
  • Each DynamoDB table

Stackdriver Logging services

Stackdriver charges for the volume of logs exceeding the logs allotment limit. All logs received by Stackdriver except the following count towards the logs allotment limit.

Following are the limits and charges for using Stackdriver Logging in the Basic and Premium service tiers:

Feature Basic Tier1 Premium Tier
Logs allotment 50 GB per project per month 50 GB per project per month plus 14.25 MB per chargeable resource per hour
Logs overage charges $0.502 per GB (opt-in3) $0.502 per GB
Logs retention:
 Admin activity audit logs
 Data access audit logs
 Non-audit logs

400 days
7 days
7 days

400 days
30 days
30 days
1 The Basic Tier limits also apply to projects that are not associated with Stackdriver accounts.
2 If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
3 Basic Tier users who want to pay logs overage charges should click Turn on billing in their Stackdriver account's Settings > Billing page. For more information, see Exceeding your logs allotment.

Free logs

There are some kinds of logs that are always free and don't count toward your allotment in either the Basic or Premium tiers. Free logs include the following:

  • Cloud Audit Logging logs that are enabled by default. 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 what are provided by default. Those logs do count toward your allotment and overage charges. 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. Excluded log entries do not appear in Stackdriver Logging. For more information, see Excluding Logs.

Calculating your logs allotment

Basic Tier. Projects in the Basic Tier and projects not associated with a Stackdriver account have their logs usage and overages computed as follows:

  1. Your project's logs usage is calculated each hour. The usage is deducted from your remaining monthly allotment. Free logs do not count toward your allotment.

  2. If you go over your monthly allotment, then your project is charged for the excess logs only if you opt in for overage charges in your Stackdriver account's Settings > Billing page. If you do not opt in, then Stackdriver excludes your excess log entries. Exceeding your logs allotment will not cause your free logs to be excluded.

Premium Tier. Projects in the Premium Tier have an additional allotment of 14.25 MB per chargeable resource per hour, which is approximately 10 GB per chargeable resource per month. This allotment is shared among other projects within a single Stackdriver account, but it must be used in the hour it is granted—it is not carried forward. Usage and overages are computed as follows:

  1. The hourly per-resource logs allotment is computed for each project based on the number of chargeable resources in the project. The allotment is applied to the hourly logs usage for that project. Free logs do not count against the allotment.

  2. If a project has less logs usage than its per-resource allotment during the hour, then that project's remaining allotment is available to offset the logs usage in other projects in the same Stackdriver account.

  3. If any project has logs usage that was not offset by the per-resource allotment, then that usage is deducted from the project's remaining monthly logs allotment. If the remaining monthly allotment is not sufficient, then the project is charged for the excess logs.

  4. In the next hour, each project receives a new per-resource logs allotment, even if the project was charged overages in the previous hour.

Exceeding your logs allotment

This information applies to all projects, regardless of service tier. When you approach your monthly logs limit, Stackdriver displays a warning notification in your project. When the allotment limit is exceeded, one of two things happen:

  • If you are paying for logs overage charges, then you are billed for the extra log entries, which continue to flow into Stackdriver Logging. This applies both in Premium Tier projects and in Basic Tier projects that opt in to logs overage charges on their Stackdriver account's Settings > Billing page.

  • If you are not paying for logs overage charges, then Stackdriver Logging discards excess log entries coming into your project. Free logs are not discarded.

Regardless of service tier, 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 selectively discard less important log entries, minimizing overage charges for the remaining 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.


Suppose your project is in the Basic Tier and you do not opt in for logs overage charges. Suppose also that your project receives roughly the same amount of logs each day, ignoring free logs, and that the project reaches its Basic Tier allotment limit at midnight before March 28. At that time, Stackdriver begins discarding all excess log entries, even though about 75% of your March logs have already been removed under the 7-day retention policy. On April 1, Stackdriver stops discarding log entries and you see the April 1 log entries in your project. However, there is still a 4-day gap in the logs from March 28 until April 1.

Exporting logs

For instructions how to export logs, see Exporting Logs. There is no Stackdriver charge for exporting logs, but the services that receive your exported logs charge you for the usage.

Stackdriver Logging processes export requests as soon as log entries arrive, before Stackdriver Logging makes any decisions about retaining the log entries based on retention periods, logs allotments, or exclusions.

Stackdriver Monitoring services

Premium Tier accounts have full access to Stackdriver Monitoring for their GCP and AWS resources. Basic Tier customers cannot monitor AWS resources and have other limitations described below.

To use Stackdriver Monitoring, your GCP projects and AWS accounts must be associated with a Stackdriver account. Other Stackdriver products do not require a Stackdriver account, but without an account you are subject to Basic Tier service restrictions. For more information, see Managing Accounts.

Metric allotments and overage charges

Stackdriver Monitoring defines over a thousand built-in metrics. Your access to built-in metrics depends on your service tier, but there is no limit on your use of the metrics you have access to. For a complete list of built-in metrics, see Metrics List.

User-defined metrics, including custom metrics and user-defined logs-based metrics, are available to Premium Tier Stackdriver accounts. You can access user-defined metrics in your Basic Tier Stackdriver account by clicking Turn on billing in the account's Settings > Billing page.

Stackdriver continues to postpone charges for custom and user-defined logs-based metrics, in both the Basic and Premium Tiers, as listed in the notice at the top of this page. The following allotment and overage charges are not yet in effect and are future-facing examples:

Feature Basic Tier Premium Tier
Built-in metric availability GCP metrics GCP metrics, AWS metrics, and Stackdriver Monitoring agent metrics
User-defined metric allotment None 500 time series per chargeable resource, plus
250 metric types per project
User-defined metric overage charges Opt in2 $0.101 per time series per month, plus
$1.00 per metric descriptor per month
Metric data retention 6 weeks 6 weeks
1 If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
2 To use any user-defined metrics in the Basic Tier, you must opt in to pay for them at the overage rate listed for the Premium Tier. To opt in, see the Settings > Billing page of your Stackdriver account.

The time series allotment is pooled across resources in the same project. For example, in a project with one custom metric and two chargeable resources, the custom metric can have up to 1,000 time series without going over the allotment.

For an introduction to metrics, see Metrics, Time Series, and Resources. To use custom and logs-based metrics, see Custom Metrics and Logs-based Metrics.

Alerting and notification limitations

For an explanation of alerting policies and notifications, see Introduction to Alerting.

In the Basic Tier, you can use only the Metric Threshold, Metric Absence, and Uptime Check conditions in your Stackdriver Monitoring alerting policies. In the Premium Tier, you can also use Metric Rate of Change, Group Aggregate Threshold, and Process Health.

In the Basic Tier, you can use only Email and Cloud Console Mobile App notifications in your Stackdriver Monitoring alerting policies. In the Premium Tier, you can also use SMS, PagerDuty, Webhooks, SNS, HipChat, Campfire, and Slack.

Frequently asked questions

How do I select my service tier?

Change your service tier in the billing page of your Stackdriver account. When you create a new Stackdriver account, it is in the Premium Tier for a 30-day free trial. After that, your account and the projects it monitors revert to the Basic Tier unless you upgrade. For more information about changing tiers, see Managing Service Tiers.

What if my project is not associated with a Stackdriver account?

Without a Stackdriver account, your project has the Basic Tier log allotment and retention period, and has access to Basic Tier services from Stackdriver Logging, Stackdriver Error Reporting, Stackdriver Debugger, and Stackdriver Trace. You cannot use Stackdriver Monitoring, upgrade to the Premium Tier, or sign up to accept overage charges.

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.

How much do I have to pay for the Premium Tier?

You can estimate the cost by looking at your current usage in the Stackdriver Resource Usage page and by putting those values into the Google Cloud Platform Pricing Calculator.

After the free trial expires, does my Stackdriver account change to the Basic Tier?

Yes. If you intend to upgrade, do it before your trial expires to avoid the risk of losing log entries when your logs retention period drops to the Basic Tier levels. If you upgrade before your free trial ends, you are not charged until the end of the free trial period.

Can I have some Stackdriver accounts in the Premium Tier and others in the Basic Tier?


Can I select which resources to monitor in my Stackdriver account?

Not at present. All resources created in the projects within your Stackdriver account are monitored.

Can I change the service tier of individual projects in a Stackdriver account?

No. All the projects monitored by a single Stackdriver account share the account's service tier and other Stackdriver billing options. However, you can move projects to different Stackdriver accounts with different service tiers.

If I upgrade to the Premium Tier, can I later change back to the Basic Tier?

Yes. When you return to the Basic Tier, you immediately lose access to Premium-only features and your logs are subject to the shorter retention period.

Can I add custom and logs-based metrics to my Basic Tier account?

Yes. You must opt in to pay metric overage charges in your Basic Tier account. Go to your Stackdriver account's Settings > Billing page.

What happens if I go over my allotments in the Premium Tier?

Premium Tier Stackdriver accounts are automatically billed for logs and metric overages. You do not lose any logs or metrics.

Will I lose access to all my logs beyond the 50 GB Basic Tier limit?

If you are in the Basic Tier and you do not opt in to pay overage fees, then you will lose access to the excess log entries in Stackdriver Logging. There are two ways you can retain access to your logs without paying overage fees:

  • Use exclusion filters to discard logs that are less important to you, so that the remaining logs are under the free logs limit.

  • Export your log entries out of Stackdriver Logging, so that you have access to your log entries even though they are not in Stackdriver Logging. The service that stores your exported logs charges you for the space.

I have a large volume 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?

Use exclusion filters to discard log entries that are less important to you. 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.

To review the amount of logs coming into your project, see the Stackdriver Logging Resource Usage page:

Go to the Logging Resource Usage page

Will services that send logs to my project receive an error when my allotment is exceeded?

No. Services that send log entries to your project cannot determine whether the entries are stored in Stackdriver Logging.

What about GCP features that are in Beta release?

GCP Beta features might be exempted from the pricing or other limitations of the service tiers. For more information, see the documentation for the Beta feature.

Send feedback about...

Stackdriver Documentation