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
"Amazon Web Services" and "AWS" are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.
For a list of recent changes made to this pricing page, see the Change list.
Beginning October 20, 2016, Stackdriver offers Basic and Premium service tiers for each Stackdriver account:
|Feature||Basic Tier||Premium Tier|
|Price||Free||$8.00 per chargeable resource4, per month (prorated hourly)|
|Supported clouds||GCP||GCP and AWS|
|Logging||5 GB per project1
|10 GB per chargeable resource1
|Custom and logs-based metrics||No allotment2
6-week data retention
|500 time series per chargeable resource, and 250 metric types per project2
6-week data retention
|Alerting policies||Some limitations3||No limitations3|
|Stackdriver VM agents||Logging agent only||Logging and Monitoring agent|
|Error Reporting, Debug, and Trace||All GCP features||All GCP features, plus AWS features if available|
1 Monthly allotment for non-exempt logs. Logs received over
the allotment incur additional charges.
See Log allotments and overage charges.
2 Allotment for custom and logs-based metrics. Metrics above the allotment incur additional charges. See Metric allotments and overage charges.
3 Basic tier accounts have limited alerting conditions and notification channels. See Alerting and notification limitations.
4 Chargeable resources include VM instances and other listed resources. For more information, see Chargeable resources.
Free Premium Trial: Every new Stackdriver account receives a 30-day free trial of the Premium Tier. When the trial expires, you can upgrade to the Premium Tier or choose the Basic Tier. All projects monitored by an account are subject to the account's service tier. For more information, see Frequently-asked questions.
This section contains more details and explanations about Stackdriver pricing.
Start of billing
On December 5, 2016, the free Premium trial period will expire for all Stackdriver accounts that are at least 30 days old. When your Stackdriver account's free trial expires, you must either upgrade your account to the Premium Tier or accept the Basic Tier of service:
If you upgrade to the Premium Tier, you will start to be billed for your chargeable resources when your free trial period ends.
If you choose the Basic Tier, you will not be billed. However, you will lose access to AWS monitoring and logging information; your logs allotment and retention period will be reduced; you won't be able to use the Monitoring agent on your VM instances, and your account will be subject to other Basic Tier limitations.
In the Premium Tier, your Stackdriver account is charged $8.00 per month, prorated hourly, for the following resources. 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 (running)
- Each Container Engine node instance in a cluster
- Each Cloud SQL instance (runnable)
AWS chargeable resources
- Each Amazon EC2 VM instance (running)
- Each Elastic Load Balancer (ELB)
- Each Elasticache cluster
- Each RDS instance
- Ten (10) SQS queues
- Each SNS topic
- Each DynamoDB table
Exempt and non-exempt logs
Each log in Stackdriver Logging is classified as exempt or non-exempt. Exempt logs do not count toward your monthly logs allotment and do not have overage charges if you have exceeded your allotment. The following logs are exempt:
Non-exempt logs count against your monthly logs allotment and any overage charges. All logs not listed as exempt are non-exempt.
Log allotments and overage charges
Stackdriver service tiers include a monthly allotment of non-exempt logs and an overage charge for logs received over that allotment:
|Tier||Retention||Monthly allotment||Overage charge|
|Basic||7 days||5 GB per project||$0.50 per GB|
|Premium||30 days||10 GB per chargeable resource||$0.50 per GB|
Log entries are held in Stackdriver Logging for the retention period and then removed. The logs allotment is a limit on the amount of non-exempt logs that your project receives. In Premium Tier accounts, overage charges are billed automatically. In Basic Tier accounts you must sign up to pay overage charges.
How it works. When you approach your monthly logs limit, your project receives a warning notification. When the allotment limit is reached, one of two things happen:
If you are paying for logs overage charges, you are billed for the extra logs and your non-exempt logs continue to flow into Stackdriver Logging.
If you are not paying for logs overage charges, Stackdriver Logging discards all new, non-exempt log entries coming into your project for the remainder of the month. However, you can still export your non-exempt logs to avoid losing them entirely.
For example, suppose your project is in the Basic Tier and you do not sign up for logs overage charges. Suppose also your project receives roughly the same amount of non-exempt logs each day, and it reaches its Basic Tier allotment limit at the start of March 28. At that time, Stackdriver begins discarding all non-exempt 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 new, non-exempt log entries in your project. However, you still see a 4-day gap in the non-exempt logs, from March 28 until April 1.
In the same example, before you reach your logs allotment limit you can choose to export your non-exempt logs to Google Cloud Storage. In that case, all your non-exempt logs are in Cloud Storage, but you still see a 4-day gap when you look at your logs in Stackdriver Logging. For more information, see Exporting logs.
You can export the logs you receive to services outside Stackdriver Logging, including Google Cloud Storage, Google BigQuery, and Google Cloud Pub/Sub. You can export both exempt and non-exempt logs, even if you are over your monthly log allotment and you choose not to pay overage charges. Exporting logs has no Stackdriver cost, but you will have storage costs from the service storing your logs. For instructions on how to export logs, see Exporting Logs.
Metric allotments and overage charges
Stackdriver measures your use of custom and logs-based metrics and charges for usage above the allotment specified by the service tier. To use any custom and logs-based metrics in the Basic Tier, you must sign up to pay overage charges.
|Basic||6 weeks||none||$0.10 per time series per month, and $1.00 per metric descriptor per month|
|Premium||6 weeks||500 time series per chargeable resource, and 250 metric descriptors per project||$0.10 per time series per month, and $1.00 per metric descriptor per month|
To understand the allotment and overage charges, you must understand how Stackdriver uses metric descriptors and time series:
A metric descriptor defines a metric type and any associated labels used to parameterize the metric. A single metric descriptor can be responsible for any number of time series. For example, only a single descriptor is needed for time series data from all of your VM instances.
A time series holds time-stamped data for the combination of a metric type, a monitored resource such as a VM instance or database, and values for any labels the metric defines. Data points in a time series expire at the end of their retention period.
A logs-based metric is a custom metric descriptor created by Stackdriver Logging. It counts the number of log entries that match a filter.
For example, suppose you have 180 VM instances and you want to write a
custom measurement for each of them every minute. You define a custom metric
custom.googleapis.com/my_measurement. On each VM instance, every
minute, you write a data point to this metric, specifying both the metric's name
and the name of the VM instance. This will create a separate time series for
each VM instance. In the Premium Tier, you have used one time series (out of
500) in each of your 180 chargeable resources, and one metric descriptor (out of
250) in your project. In the Basic Tier, the overage cost for this custom data
is $19.00 per month: $1.00 for the metric descriptor, and $18.00 for the 180
time series. If you stop writing data to the metric, all the time series
eventually expire and you are left with the $1.00 per month charge for the
descriptor, which you can delete.
Alerting and notification limitations
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 notifications in your Stackdriver Monitoring alerting policies. In the Premium Tier, you can also use SMS, Google Cloud Console (mobile app), 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, Error Reporting, Debugger, and 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 for my project?
With your project selected in the Cloud Platform Console, choose Stackdriver > Monitoring and follow the instructions to create a Stackdriver account. For more information, see Creating a Stackdriver account.
How much do I have to pay for the Premium Tier?
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 allotment and retention period drop to the Basic Tier levels.
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?
No. 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 downgrade your account, you immediately lose access to Premium-only features and your logs are truncated to the shorter retention period.
Can I add custom and logs-based metrics to my Basic Tier account?
Yes. You must sign up to pay metric overage charges in your Basic Tier account.
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.
Log allotments are reset at the beginning of each monthly billing period. For example, if you go over your allotment on the last day of the month, then you'll have your full allotment back the next day.
Will I lose access to all my logs beyond the 5 GB Basic Tier limit?
See the example in Logs allotments.
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?
If the GCP logs are classified as exempt, they will not count toward your allotment or cause overage charges. For more information, see Exempt and non-exempt logs. This is a subject that is being reviewed and may change.
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 were accepted, unless the service tries to read back the entries through the Stackdriver Logging API. Discarded entries will not be present, just as they are not visible in the Logs Viewer.
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.
The following changes were made to this pricing page:
December 1, 2016: Clarify that Stackdriver is postponing the introduction of both allotment limits and overage charges.
November 29, 2016: This pricing page has been reorganized. The following information is new:
- Stackdriver billing begins on December 5, 2016 for Stackdriver accounts that have reached the end of their free Premium trial.
- Logs that do not count against the logs allotments are now referred to as exempt. See Exempt and non-exempt logs.
- Stackdriver is not presently charging the overage fees discussed on this page. Customers will be notified before charging begins.