google-cloud-monitoring 0.38.0 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bcfd03392d8799f7a71bb655875632abbce2bc4a283c637373084349dc86d5cf
-  data.tar.gz: d7bdd47af9c00b35d36fdd1d1008431bb687575a3bd155d438d5e10e88dad4d5
+  metadata.gz: fd54ba8f56a6102bc6660a9c23696596e9f10eebb361b925df8a5aa178bfeec5
+  data.tar.gz: b74d887d821c194c2608c96dcacad842c549fb712bde9aceec8e4b59be65e73d
 SHA512:
-  metadata.gz: 262ab3ce3d0e384233d9b437d6de34b8d1717badaee2b86e5b5eeaf082b52f11111465a1588efbeeaf4d6d1518b8a35b9669a9bc3644657f089e14225e13c973
-  data.tar.gz: 3a91453e0e642e9eb337ba9a3348467772aab6acf13f8f7f9a1b98f0787b5002981bff5b899c56cd33f7eb77d6699af002e0ad32fa2fec3c03d8f0c3c88acad4
+  metadata.gz: 90367a4b3a1f82ba0183cae76a1b00a8a1513ad6def35d488b1da80a1ea21e88e2ff65f74919e27b3621e3d1eb1b4bfd10303d72532a9f43ec7d90905aee84cc
+  data.tar.gz: 49c849ca27fbe6fd0ada15fa9fd627acbb7102fca1c7c3ba225084d63b0869cc5d4f20a5f5fe7418d5a63d956ac9780ff24e4b36bc5da1e7eafa0a4d58b1f25d

data/.yardopts

@@ -8,4 +8,5 @@
 -
 README.md
 AUTHENTICATION.md
-LICENSE
+MIGRATING.md
+LICENSE.md

data/AUTHENTICATION.md

@@ -1,16 +1,17 @@
 # Authentication
 
-In general, the google-cloud-monitoring library uses [Service
-Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
-credentials to connect to Google Cloud services. When running within [Google
-Cloud Platform environments](#google-cloud-platform-environments)
-the credentials will be discovered automatically. When running on other
+In general, the google-cloud-monitoring library uses
+[Service Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
+credentials to connect to Google Cloud services. When running within
+[Google Cloud Platform environments](#google-cloud-platform-environments) the
+credentials will be discovered automatically. When running on other
 environments, the Service Account credentials can be specified by providing the
-path to the [JSON
-keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys) for
-the account (or the JSON itself) in [environment
-variables](#environment-variables). Additionally, Cloud SDK credentials can also
-be discovered automatically, but this is only recommended during development.
+path to the
+[JSON keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys)
+for the account (or the JSON itself) in
+[environment variables](#environment-variables). Additionally, Cloud SDK
+credentials can also be discovered automatically, but this is only recommended
+during development.
 
 ## Quickstart
 
@@ -18,7 +19,7 @@ be discovered automatically, but this is only recommended during development.
 2. Set the [environment variable](#environment-variables).
 
 ```sh
-export MONITORING_CREDENTIALS=/path/to/json`
+export MONITORING_CREDENTIALS=path/to/keyfile.json
 ```
 
 3. Initialize the client.
@@ -26,23 +27,14 @@ export MONITORING_CREDENTIALS=/path/to/json`
 ```ruby
 require "google/cloud/monitoring"
 
-client = Google::Cloud::Monitoring::AlertPolicy.new
+client = Google::Cloud::Monitoring.alert_policy_service
 ```
 
-## Project and Credential Lookup
+## Credential Lookup
 
 The google-cloud-monitoring library aims to make authentication
 as simple as possible, and provides several mechanisms to configure your system
-without providing **Project ID** and **Service Account Credentials** directly in
-code.
-
-**Project ID** is discovered in the following order:
-
-1. Specify project ID in method arguments
-2. Specify project ID in configuration
-3. Discover project ID in environment variables
-4. Discover GCP project ID
-5. Discover project ID in credentials JSON
+without requiring **Service Account Credentials** directly in code.
 
 **Credentials** are discovered in the following order:
 
@@ -55,28 +47,24 @@ code.
 
 ### Google Cloud Platform environments
 
-When running on Google Cloud Platform (GCP), including Google Compute Engine (GCE),
-Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud Functions
-(GCF) and Cloud Run, the **Project ID** and **Credentials** and are discovered
-automatically. Code should be written as if already authenticated.
+When running on Google Cloud Platform (GCP), including Google Compute Engine
+(GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
+Functions (GCF) and Cloud Run, **Credentials** are discovered automatically.
+Code should be written as if already authenticated.
 
 ### Environment Variables
 
-The **Project ID** and **Credentials JSON** can be placed in environment
-variables instead of declaring them directly in code. Each service has its own
-environment variable, allowing for different service accounts to be used for
-different services. (See the READMEs for the individual service gems for
-details.) The path to the **Credentials JSON** file can be stored in the
-environment variable, or the **Credentials JSON** itself can be stored for
-environments such as Docker containers where writing files is difficult or not
-encouraged.
-
-The environment variables that google-cloud-monitoring checks for project ID are:
+The **Credentials JSON** can be placed in environment variables instead of
+declaring them directly in code. Each service has its own environment variable,
+allowing for different service accounts to be used for different services. (See
+the READMEs for the individual service gems for details.) The path to the
+**Credentials JSON** file can be stored in the environment variable, or the
+**Credentials JSON** itself can be stored for environments such as Docker
+containers where writing files is difficult or not encouraged.
 
-1. `MONITORING_PROJECT`
-2. `GOOGLE_CLOUD_PROJECT`
-
-The environment variables that google-cloud-monitoring checks for credentials are configured on {Google::Cloud::Monitoring::V3::Credentials}:
+The environment variables that google-cloud-monitoring
+checks for credentials are configured on the service Credentials class (such as
+`::Google::Cloud::Monitoring::V3::AlertPolicyService::Credentials`):
 
 1. `MONITORING_CREDENTIALS` - Path to JSON file, or JSON contents
 2. `MONITORING_KEYFILE` - Path to JSON file, or JSON contents
@@ -87,25 +75,34 @@ The environment variables that google-cloud-monitoring checks for credentials ar
 ```ruby
 require "google/cloud/monitoring"
 
-ENV["MONITORING_PROJECT"]     = "my-project-id"
 ENV["MONITORING_CREDENTIALS"] = "path/to/keyfile.json"
 
-client = Google::Cloud::Monitoring::AlertPolicy.new
+client = Google::Cloud::Monitoring.alert_policy_service
 ```
 
 ### Configuration
 
-The **Project ID** and **Credentials JSON** can be configured instead of placing them in environment variables or providing them as arguments.
+The **Credentials JSON** can be configured instead of placing them in
+environment variables. Either on an individual client initialization:
+
+```ruby
+require "google/cloud/monitoring"
+
+client = Google::Cloud::Monitoring.alert_policy_service do |config|
+  config.credentials = "path/to/keyfile.json"
+end
+```
+
+Or configured globally for all clients:
 
 ```ruby
 require "google/cloud/monitoring"
 
 Google::Cloud::Monitoring.configure do |config|
-  config.project_id  = "my-project-id"
   config.credentials = "path/to/keyfile.json"
 end
 
-client = Google::Cloud::Monitoring::AlertPolicy.new
+client = Google::Cloud::Monitoring.alert_policy_service
 ```
 
 ### Cloud SDK
@@ -134,24 +131,24 @@ To configure your system for this, simply:
 
 ## Creating a Service Account
 
-Google Cloud requires a **Project ID** and **Service Account Credentials** to
-connect to the APIs. You will use the **Project ID** and **JSON key file** to
+Google Cloud requires **Service Account Credentials** to
+connect to the APIs. You will use the **JSON key file** to
 connect to most services with google-cloud-monitoring.
 
-If you are not running this client within [Google Cloud Platform
-environments](#google-cloud-platform-environments), you need a Google
-Developers service account.
+If you are not running this client within
+[Google Cloud Platform environments](#google-cloud-platform-environments), you
+need a Google Developers service account.
 
 1. Visit the [Google Developers Console][dev-console].
-1. Create a new project or click on an existing project.
-1. Activate the slide-out navigation tray and select **API Manager**. From
+2. Create a new project or click on an existing project.
+3. Activate the slide-out navigation tray and select **API Manager**. From
    here, you will enable the APIs that your application requires.
 
    ![Enable the APIs that your application requires][enable-apis]
 
    *Note: You may need to enable billing in order to use these services.*
 
-1. Select **Credentials** from the side navigation.
+4. Select **Credentials** from the side navigation.
 
    You should see a screen like one of the following.
 

data/LICENSE.md

@@ -0,0 +1,201 @@
+                                  Apache License
+                            Version 2.0, January 2004
+                         http://www.apache.org/licenses/
+
+    TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+    1. Definitions.
+
+       "License" shall mean the terms and conditions for use, reproduction,
+       and distribution as defined by Sections 1 through 9 of this document.
+
+       "Licensor" shall mean the copyright owner or entity authorized by
+       the copyright owner that is granting the License.
+
+       "Legal Entity" shall mean the union of the acting entity and all
+       other entities that control, are controlled by, or are under common
+       control with that entity. For the purposes of this definition,
+       "control" means (i) the power, direct or indirect, to cause the
+       direction or management of such entity, whether by contract or
+       otherwise, or (ii) ownership of fifty percent (50%) or more of the
+       outstanding shares, or (iii) beneficial ownership of such entity.
+
+       "You" (or "Your") shall mean an individual or Legal Entity
+       exercising permissions granted by this License.
+
+       "Source" form shall mean the preferred form for making modifications,
+       including but not limited to software source code, documentation
+       source, and configuration files.
+
+       "Object" form shall mean any form resulting from mechanical
+       transformation or translation of a Source form, including but
+       not limited to compiled object code, generated documentation,
+       and conversions to other media types.
+
+       "Work" shall mean the work of authorship, whether in Source or
+       Object form, made available under the License, as indicated by a
+       copyright notice that is included in or attached to the work
+       (an example is provided in the Appendix below).
+
+       "Derivative Works" shall mean any work, whether in Source or Object
+       form, that is based on (or derived from) the Work and for which the
+       editorial revisions, annotations, elaborations, or other modifications
+       represent, as a whole, an original work of authorship. For the purposes
+       of this License, Derivative Works shall not include works that remain
+       separable from, or merely link (or bind by name) to the interfaces of,
+       the Work and Derivative Works thereof.
+
+       "Contribution" shall mean any work of authorship, including
+       the original version of the Work and any modifications or additions
+       to that Work or Derivative Works thereof, that is intentionally
+       submitted to Licensor for inclusion in the Work by the copyright owner
+       or by an individual or Legal Entity authorized to submit on behalf of
+       the copyright owner. For the purposes of this definition, "submitted"
+       means any form of electronic, verbal, or written communication sent
+       to the Licensor or its representatives, including but not limited to
+       communication on electronic mailing lists, source code control systems,
+       and issue tracking systems that are managed by, or on behalf of, the
+       Licensor for the purpose of discussing and improving the Work, but
+       excluding communication that is conspicuously marked or otherwise
+       designated in writing by the copyright owner as "Not a Contribution."
+
+       "Contributor" shall mean Licensor and any individual or Legal Entity
+       on behalf of whom a Contribution has been received by Licensor and
+       subsequently incorporated within the Work.
+
+    2. Grant of Copyright License. Subject to the terms and conditions of
+       this License, each Contributor hereby grants to You a perpetual,
+       worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+       copyright license to reproduce, prepare Derivative Works of,
+       publicly display, publicly perform, sublicense, and distribute the
+       Work and such Derivative Works in Source or Object form.
+
+    3. Grant of Patent License. Subject to the terms and conditions of
+       this License, each Contributor hereby grants to You a perpetual,
+       worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+       (except as stated in this section) patent license to make, have made,
+       use, offer to sell, sell, import, and otherwise transfer the Work,
+       where such license applies only to those patent claims licensable
+       by such Contributor that are necessarily infringed by their
+       Contribution(s) alone or by combination of their Contribution(s)
+       with the Work to which such Contribution(s) was submitted. If You
+       institute patent litigation against any entity (including a
+       cross-claim or counterclaim in a lawsuit) alleging that the Work
+       or a Contribution incorporated within the Work constitutes direct
+       or contributory patent infringement, then any patent licenses
+       granted to You under this License for that Work shall terminate
+       as of the date such litigation is filed.
+
+    4. Redistribution. You may reproduce and distribute copies of the
+       Work or Derivative Works thereof in any medium, with or without
+       modifications, and in Source or Object form, provided that You
+       meet the following conditions:
+
+       (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+       (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+       (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+       (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+       You may add Your own copyright statement to Your modifications and
+       may provide additional or different license terms and conditions
+       for use, reproduction, or distribution of Your modifications, or
+       for any such Derivative Works as a whole, provided Your use,
+       reproduction, and distribution of the Work otherwise complies with
+       the conditions stated in this License.
+
+    5. Submission of Contributions. Unless You explicitly state otherwise,
+       any Contribution intentionally submitted for inclusion in the Work
+       by You to the Licensor shall be under the terms and conditions of
+       this License, without any additional terms or conditions.
+       Notwithstanding the above, nothing herein shall supersede or modify
+       the terms of any separate license agreement you may have executed
+       with Licensor regarding such Contributions.
+
+    6. Trademarks. This License does not grant permission to use the trade
+       names, trademarks, service marks, or product names of the Licensor,
+       except as required for reasonable and customary use in describing the
+       origin of the Work and reproducing the content of the NOTICE file.
+
+    7. Disclaimer of Warranty. Unless required by applicable law or
+       agreed to in writing, Licensor provides the Work (and each
+       Contributor provides its Contributions) on an "AS IS" BASIS,
+       WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+       implied, including, without limitation, any warranties or conditions
+       of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+       PARTICULAR PURPOSE. You are solely responsible for determining the
+       appropriateness of using or redistributing the Work and assume any
+       risks associated with Your exercise of permissions under this License.
+
+    8. Limitation of Liability. In no event and under no legal theory,
+       whether in tort (including negligence), contract, or otherwise,
+       unless required by applicable law (such as deliberate and grossly
+       negligent acts) or agreed to in writing, shall any Contributor be
+       liable to You for damages, including any direct, indirect, special,
+       incidental, or consequential damages of any character arising as a
+       result of this License or out of the use or inability to use the
+       Work (including but not limited to damages for loss of goodwill,
+       work stoppage, computer failure or malfunction, or any and all
+       other commercial damages or losses), even if such Contributor
+       has been advised of the possibility of such damages.
+
+    9. Accepting Warranty or Additional Liability. While redistributing
+       the Work or Derivative Works thereof, You may choose to offer,
+       and charge a fee for, acceptance of support, warranty, indemnity,
+       or other liability obligations and/or rights consistent with this
+       License. However, in accepting such obligations, You may act only
+       on Your own behalf and on Your sole responsibility, not on behalf
+       of any other Contributor, and only if You agree to indemnify,
+       defend, and hold each Contributor harmless for any liability
+       incurred by, or claims asserted against, such Contributor by reason
+       of your accepting any such warranty or additional liability.
+
+    END OF TERMS AND CONDITIONS
+
+    APPENDIX: How to apply the Apache License to your work.
+
+       To apply the Apache License to your work, attach the following
+       boilerplate notice, with the fields enclosed by brackets "[]"
+       replaced with your own identifying information. (Don't include
+       the brackets!)  The text should be enclosed in the appropriate
+       comment syntax for the file format. We also recommend that a
+       file or class name and description of purpose be included on the
+       same "printed page" as the copyright notice for easier
+       identification within third-party archives.
+
+    Copyright [yyyy] [name of copyright owner]
+
+    Licensed under the Apache License, Version 2.0 (the "License");
+    you may not use this file except in compliance with the License.
+    You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.

data/MIGRATING.md

@@ -0,0 +1,361 @@
+## Migrating to google-cloud-monitoring 1.0
+
+The 1.0 release of the google-cloud-monitoring client is a significant upgrade
+based on a [next-gen code generator](https://github.com/googleapis/gapic-generator-ruby),
+and includes substantial interface changes. Existing code written for earlier
+versions of this library will likely require updates to use this version.
+This document describes the changes that have been made, and what you need to
+do to update your usage.
+
+To summarize:
+
+ *  The library has been broken out into multiple libraries. The new gems
+    `google-cloud-monitoring-v3` and `google-cloud-monitoring-dashboard-v1`
+    contain the actual client classes for version V3 of the monitoring service
+    and version V1 of the monitoring-dashboard service, respectively, and the
+    gem `google-cloud-monitoring` now simply provides a convenience wrapper.
+    See [Library Structure](#library-structure) for more info.
+ *  The library uses a new configuration mechanism giving you closer control
+    over endpoint address, network timeouts, and retry. See
+    [Client Configuration](#client-configuration) for more info. Furthermore,
+    when creating a client object, you can customize its configuration in a
+    block rather than passing arguments to the constructor. See
+    [Creating Clients](#creating-clients) for more info.
+ *  Previously, positional arguments were used to indicate required arguments.
+    Now, all method arguments are keyword arguments, with documentation that
+    specifies whether they are required or optional. Additionally, you can pass
+    a proto request object instead of separate arguments. See
+    [Passing Arguments](#passing-arguments) for more info.
+ *  Previously, some client classes included class methods for constructing
+    resource paths. These paths are now instance methods on the client objects,
+    and are also available in a separate paths module. See
+    [Resource Path Helpers](#resource-path-helpers) for more info.
+ *  Previously, clients reported RPC errors by raising instances of
+    `Google::Gax::GaxError` and its subclasses. Now, RPC exceptions are of type
+    `Google::Cloud::Error` and its subclasses. See
+    [Handling Errors](#handling-errors) for more info.
+ *  Some classes have moved into different namespaces. See
+    [Class Namespaces](#class-namespaces) for more info.
+
+### Library Structure
+
+Older 0.x releases of the `google-cloud-monitoring` gem were all-in-one gems
+that included multiple clients for potentially multiple versions of the various
+monitoring-related services. Factory methods such as `Google::Cloud::Monitoring::Metric.new`
+would return you instances of the actual client classes such as
+`Google::Cloud::Monitoring::V3::MetricServiceClient`. These classes were all
+defined in the same gem.
+
+With the 1.0 release, the `google-cloud-monitoring` gem still provides factory
+methods for obtaining clients. (The method signatures will have changed. See
+[Creating Clients](#creating-clients) for details.) However, the actual client
+classes have been moved into separate gems, one per service and version. The
+`Google::Cloud::Monitoring::V3::MetricService::Client` class, along with its
+helpers and data types, is now part of the `google-cloud-monitoring-v3` gem.
+Similarly, the `Google::Cloud::Monitoring::Dashboard::V1::DashboardsService::Client`
+class is part of the `google-cloud-monitoring-dashboard-v1` gem.
+
+For normal usage, you can continue to install the `google-cloud-monitoring` gem
+(which will bring in the various client gems as dependencies) and continue to
+use factory methods to create clients. However, you may alternatively choose to
+install only one of the versioned gems. For example, if you know you will only
+use `V3` of the base monitoring service, you can install `google-cloud-monitoring-v3` by
+itself, and construct instances of the `Google::Cloud::Monitoring::V3::*` client
+classes directly.
+
+### Client Configuration
+
+In older releases, if you wanted to customize performance parameters or
+low-level behavior of the client (such as credentials, timeouts, or
+instrumentation), you would pass a variety of keyword arguments to the client
+constructor. It was also extremely difficult to customize the default settings.
+
+With the 1.0 release, a configuration interface provides control over these
+parameters, including defaults for all instances of a client, and settings for
+each specific client instance. For example, to set default credentials and
+timeout for all Monitoring V3 MetricService clients:
+
+```
+Google::Cloud::Monitoring::V3::MetricService::Client.configure do |config|
+  config.credentials = "/path/to/credentials.json"
+  config.timeout = 10.0
+end
+```
+
+Individual RPCs can also be configured independently. For example, to set the
+timeout for the `create_metric_descriptor` call:
+
+```
+Google::Cloud::Monitoring::V3::MetricService::Client.configure do |config|
+  config.rpcs.create_metric_descriptor.timeout = 20.0
+end
+```
+
+Defaults for certain configurations can be set for all Monitoring versions and
+services globally:
+
+```
+Google::Cloud::Monitoring.configure do |config|
+  config.credentials = "/path/to/credentials.json"
+  config.timeout = 10.0
+end
+```
+
+Finally, you can override the configuration for each client instance. See the
+next section on [Creating Clients](#creating-clients) for details.
+
+### Creating Clients
+
+In older releases, to create a client object, you would use the `new` method
+of modules under `Google::Cloud::Monitoring`. For example, you might call
+`Google::Cloud::Monitoring::Metric.new`. Keyword arguments were available to
+select a service version and to configure parameters such as credentials and
+timeouts.
+
+With the 1.0 release, use named class methods of `Google::Cloud::Monitoring` to
+create a client object. For example, `Google::Cloud::Monitoring.metric_service`.
+You may select a service version using the `:version` keyword argument.
+However, other configuration parameters should be set in a configuration block
+when you create the client.
+
+Old:
+```
+client = Google::Cloud::Monitoring::Metric.new credentials: "/path/to/credentials.json"
+```
+
+New:
+```
+client = Google::Cloud::Monitoring.metric_service do |config|
+  config.credentials = "/path/to/credentials.json"
+end
+```
+
+The configuration block is optional. If you do not provide it, or you do not
+set some configuration parameters, then the default configuration is used. See
+[Client Configuration](#client-configuration).
+
+A similar change was made for the monitoring dashboards service:
+
+Old:
+```
+client = Google::Cloud::Monitoring::Dashboard.new credentials: "/path/to/credentials.json"
+```
+
+New:
+```
+client = Google::Cloud::Monitoring::Dashboard.dashboards_service do |config|
+  config.credentials = "/path/to/credentials.json"
+end
+```
+
+### Passing Arguments
+
+In older releases, required arguments would be passed as positional method
+arguments, while most optional arguments would be passed as keyword arguments.
+
+With the 1.0 release, all RPC arguments are passed as keyword arguments,
+regardless of whether they are required or optional. For example:
+
+Old:
+```
+client = Google::Cloud::Monitoring::Metric.new
+
+name = "projects/my-project"
+
+# The required name argument is positional, while the optional page_size
+# argument is a keyword argument
+response = client.list_metric_descriptors name, page_size: 10
+```
+
+New:
+```
+client = Google::Cloud::Monitoring.metric_service
+
+name = "projects/my-project"
+
+# All arguments are keyword arguments
+response = client.list_metric_descriptors name: name, page_size: 10
+```
+
+In the 1.0 release, it is also possible to pass a request object, either
+as a hash or as a protocol buffer.
+
+New:
+```
+client = Google::Cloud::Monitoring.metric_service
+
+request = Google::Cloud::Monitoring::V3::ListMetricDescriptorsRequest.new(
+  name: "projects/my-project",
+  page_size: 10
+)
+
+# Pass a request object as a positional argument:
+response = client.list_metric_descriptors request
+```
+
+Finally, in older releases, to provide call options, you would pass a
+`Google::Gax::CallOptions` object with the `:options` keyword argument. In the
+1.0 release, pass call options using a _second set_ of keyword arguments.
+
+Old:
+```
+client = Google::Cloud::Monitoring::Metric.new
+
+name = "projects/my-project"
+
+options = Google::Gax::CallOptions.new timeout: 10.0
+
+response = client.list_metric_descriptors name, page_size: 10, options: options
+```
+
+New:
+```
+client = Google::Cloud::Monitoring.metric_service
+
+name = "projects/my-project"
+
+# Use a hash to wrap the normal call arguments (or pass a request object), and
+# then add further keyword arguments for the call options.
+response = client.list_metric_descriptors(
+  { name: name, page_size: 10 },
+  timeout: 10.0)
+```
+
+### Resource Path Helpers
+
+The client library includes helper methods for generating the resource path
+strings passed to many calls. These helpers have changed in two ways:
+
+* In older releases, they are _class_ methods on the client class. In the 1.0
+  release, they are _instance_ methods on the client. They are also available
+  on a separate paths module that you can include elsewhere for convenience.
+* In older releases, arguments to a resource path helper are passed as
+  _positional_ arguments. In the 1.0 release, they are passed as named _keyword_
+  arguments. Some helpers also support different sets of arguments, each set
+  corresponding to a different type of path.
+
+Following is an example involving using a resource path helper.
+
+Old:
+```
+client = Google::Cloud::Monitoring::UptimeCheck.new
+
+# Call the helper on the client class
+name = Google::Cloud::Monitoring::V3::UptimeCheckServiceClient.
+         uptime_check_config_path("my-project", "my-uptime-check")
+
+response = client.get_uptime_check_config name
+```
+
+New:
+```
+client = Google::Cloud::Monitoring.uptime_check_service
+
+# Call the helper on the client instance, and use keyword arguments
+name = client.uptime_check_config_path project: "my-project",
+                                       uptime_check_config: "my-uptime-check"
+
+response = client.get_uptime_check_config name: name
+```
+
+Because helpers take keyword arguments, some can now generate several different
+variations on the path that were not available under earlier versions of the
+library. For example, `get_uptime_check_config` can generate paths with either
+a project, an organization, or a folder as the parent resource.
+
+New:
+```
+client = Google::Cloud::Monitoring.uptime_check_service
+
+# Create paths with different parent resource types
+name = client.uptime_check_config_path project: "my-project",
+                                       uptime_check_config: "my-uptime-check"
+# => "projects/my-project/uptimeCheckConfigs/my-uptime-check"
+name = client.uptime_check_config_path folder: "my-folder",
+                                       uptime_check_config: "my-uptime-check"
+# => "folders/my-folder/uptimeCheckConfigs/my-uptime-check"
+```
+
+Finally, in the 1.0 client, you can also use the paths module as a convenience module.
+
+New:
+```
+# Bring the path helper methods into the current class
+include Google::Cloud::Monitoring::V3::UptimeCheckService::Paths
+
+def foo
+  client = Google::Cloud::Monitoring.uptime_check_service
+
+  # Call the included helper method
+  name = uptime_check_config_path project: "my-project",
+                                  uptime_check_config: "my-uptime-check"
+
+  response = client.get_uptime_check_config name: name
+
+  # Do something with response...
+end
+```
+
+### Handling Errors
+
+The client reports standard
+[gRPC error codes](https://github.com/grpc/grpc/blob/master/doc/statuscodes.md)
+by raising exceptions. In older releases, these exceptions were located in the
+`Google::Gax` namespace and were subclasses of the `Google::Gax::GaxError` base
+exception class, defined in the `google-gax` gem. However, these classes were
+different from the standard exceptions (subclasses of `Google::Cloud::Error`)
+thrown by other client libraries such as `google-cloud-storage`.
+
+The 1.0 client library now uses the `Google::Cloud::Error` exception hierarchy
+for consistency across all the Google Cloud client libraries. In general, these
+exceptions have the same name as their counterparts from older releases, but
+are located in the `Google::Cloud` namespace rather than the `Google::Gax`
+namespace.
+
+Old:
+```
+client = Google::Cloud::Monitoring::Metric.new
+
+name = "projects/my-project"
+
+begin
+  response = client.list_metric_descriptors name, page_size: 10
+rescue Google::Gax::Error => e
+  # Handle exceptions that subclass Google::Gax::Error
+end
+```
+
+New:
+```
+client = Google::Cloud::Monitoring.metric_service
+
+name = "projects/my-project"
+
+begin
+  response = client.list_metric_descriptors name: name, page_size: 10
+rescue Google::Cloud::Error => e
+  # Handle exceptions that subclass Google::Cloud::Error
+end
+```
+
+### Class Namespaces
+
+In older releases, some data type (protobuf) classes were located under the module
+`Google::Monitoring`. In the 1.0 release, these classes have been moved into the
+same `Google::Cloud::Monitoring` module by the client object, for consistency.
+
+In older releases, the client object was of classes with names like:
+`Google::Cloud::Monitoring::V3::MetricServiceClient`.
+In the 1.0 release, the client object is of a different class:
+`Google::Cloud::Monitoring::V3::MetricService::Client`.
+Note that most users will use the factory methods such as
+`Google::Cloud::Monitoring.metric_service` to create instances of the client object,
+so you may not need to reference the actual class directly.
+See [Creating Clients](#creating-clients).
+
+In older releases, the credentials object was of class
+`Google::Cloud::Monitoring::V3::Credentials`.
+In the 1.0 release, each service has its own credentials class, e.g.
+`Google::Cloud::Monitoring::V3::MetricService::Credentials`.
+Again, most users will not need to reference this class directly.
+See [Client Configuration](#client-configuration).