google-cloud-monitoring 0.38.0 → 1.0.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (101) hide show
  1. checksums.yaml +4 -4
  2. data/.yardopts +2 -1
  3. data/AUTHENTICATION.md +51 -54
  4. data/LICENSE.md +203 -0
  5. data/MIGRATING.md +361 -0
  6. data/README.md +34 -50
  7. data/lib/google-cloud-monitoring.rb +6 -5
  8. data/lib/google/cloud/monitoring.rb +255 -443
  9. data/lib/google/cloud/monitoring/dashboard.rb +88 -117
  10. data/lib/google/cloud/monitoring/{v3/doc/google/protobuf/wrappers.rb → dashboard/version.rb} +12 -9
  11. data/lib/google/cloud/monitoring/version.rb +6 -2
  12. metadata +71 -128
  13. data/LICENSE +0 -201
  14. data/lib/google/cloud/monitoring/dashboard/v1.rb +0 -148
  15. data/lib/google/cloud/monitoring/dashboard/v1/credentials.rb +0 -46
  16. data/lib/google/cloud/monitoring/dashboard/v1/dashboards_service_client.rb +0 -457
  17. data/lib/google/cloud/monitoring/dashboard/v1/dashboards_service_client_config.json +0 -51
  18. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/common.rb +0 -394
  19. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/dashboard.rb +0 -53
  20. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/dashboards_service.rb +0 -82
  21. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/layouts.rb +0 -71
  22. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/metrics.rb +0 -151
  23. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/scorecard.rb +0 -102
  24. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/text.rb +0 -43
  25. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/widget.rb +0 -41
  26. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/monitoring/dashboard/v1/xychart.rb +0 -141
  27. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/protobuf/duration.rb +0 -91
  28. data/lib/google/cloud/monitoring/dashboard/v1/doc/google/protobuf/empty.rb +0 -29
  29. data/lib/google/cloud/monitoring/v3.rb +0 -532
  30. data/lib/google/cloud/monitoring/v3/alert_policy_service_client.rb +0 -553
  31. data/lib/google/cloud/monitoring/v3/alert_policy_service_client_config.json +0 -51
  32. data/lib/google/cloud/monitoring/v3/credentials.rb +0 -44
  33. data/lib/google/cloud/monitoring/v3/doc/google/api/distribution.rb +0 -200
  34. data/lib/google/cloud/monitoring/v3/doc/google/api/label.rb +0 -42
  35. data/lib/google/cloud/monitoring/v3/doc/google/api/metric.rb +0 -245
  36. data/lib/google/cloud/monitoring/v3/doc/google/api/monitored_resource.rb +0 -108
  37. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/alert.rb +0 -344
  38. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/alert_service.rb +0 -138
  39. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/common.rb +0 -449
  40. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/group.rb +0 -75
  41. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/group_service.rb +0 -167
  42. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/metric.rb +0 -85
  43. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/metric_service.rb +0 -230
  44. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/mutation_record.rb +0 -29
  45. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/notification.rb +0 -156
  46. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/notification_service.rb +0 -221
  47. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/service.rb +0 -361
  48. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/service_service.rb +0 -197
  49. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/uptime.rb +0 -364
  50. data/lib/google/cloud/monitoring/v3/doc/google/monitoring/v3/uptime_service.rb +0 -136
  51. data/lib/google/cloud/monitoring/v3/doc/google/protobuf/any.rb +0 -131
  52. data/lib/google/cloud/monitoring/v3/doc/google/protobuf/duration.rb +0 -91
  53. data/lib/google/cloud/monitoring/v3/doc/google/protobuf/empty.rb +0 -29
  54. data/lib/google/cloud/monitoring/v3/doc/google/protobuf/field_mask.rb +0 -222
  55. data/lib/google/cloud/monitoring/v3/doc/google/protobuf/struct.rb +0 -74
  56. data/lib/google/cloud/monitoring/v3/doc/google/protobuf/timestamp.rb +0 -113
  57. data/lib/google/cloud/monitoring/v3/doc/google/rpc/status.rb +0 -39
  58. data/lib/google/cloud/monitoring/v3/group_service_client.rb +0 -606
  59. data/lib/google/cloud/monitoring/v3/group_service_client_config.json +0 -56
  60. data/lib/google/cloud/monitoring/v3/metric_service_client.rb +0 -750
  61. data/lib/google/cloud/monitoring/v3/metric_service_client_config.json +0 -66
  62. data/lib/google/cloud/monitoring/v3/notification_channel_service_client.rb +0 -811
  63. data/lib/google/cloud/monitoring/v3/notification_channel_service_client_config.json +0 -76
  64. data/lib/google/cloud/monitoring/v3/service_monitoring_service_client.rb +0 -788
  65. data/lib/google/cloud/monitoring/v3/service_monitoring_service_client_config.json +0 -76
  66. data/lib/google/cloud/monitoring/v3/uptime_check_service_client.rb +0 -550
  67. data/lib/google/cloud/monitoring/v3/uptime_check_service_client_config.json +0 -56
  68. data/lib/google/monitoring/dashboard/v1/common_pb.rb +0 -95
  69. data/lib/google/monitoring/dashboard/v1/dashboard_pb.rb +0 -29
  70. data/lib/google/monitoring/dashboard/v1/dashboards_service_pb.rb +0 -51
  71. data/lib/google/monitoring/dashboard/v1/dashboards_service_services_pb.rb +0 -76
  72. data/lib/google/monitoring/dashboard/v1/drilldowns_pb.rb +0 -17
  73. data/lib/google/monitoring/dashboard/v1/layouts_pb.rb +0 -41
  74. data/lib/google/monitoring/dashboard/v1/metrics_pb.rb +0 -76
  75. data/lib/google/monitoring/dashboard/v1/scorecard_pb.rb +0 -38
  76. data/lib/google/monitoring/dashboard/v1/service_pb.rb +0 -17
  77. data/lib/google/monitoring/dashboard/v1/text_pb.rb +0 -28
  78. data/lib/google/monitoring/dashboard/v1/widget_pb.rb +0 -32
  79. data/lib/google/monitoring/dashboard/v1/xychart_pb.rb +0 -66
  80. data/lib/google/monitoring/v3/alert_pb.rb +0 -87
  81. data/lib/google/monitoring/v3/alert_service_pb.rb +0 -53
  82. data/lib/google/monitoring/v3/alert_service_services_pb.rb +0 -63
  83. data/lib/google/monitoring/v3/common_pb.rb +0 -95
  84. data/lib/google/monitoring/v3/dropped_labels_pb.rb +0 -19
  85. data/lib/google/monitoring/v3/group_pb.rb +0 -24
  86. data/lib/google/monitoring/v3/group_service_pb.rb +0 -73
  87. data/lib/google/monitoring/v3/group_service_services_pb.rb +0 -66
  88. data/lib/google/monitoring/v3/metric_pb.rb +0 -82
  89. data/lib/google/monitoring/v3/metric_service_pb.rb +0 -130
  90. data/lib/google/monitoring/v3/metric_service_services_pb.rb +0 -66
  91. data/lib/google/monitoring/v3/mutation_record_pb.rb +0 -21
  92. data/lib/google/monitoring/v3/notification_pb.rb +0 -47
  93. data/lib/google/monitoring/v3/notification_service_pb.rb +0 -90
  94. data/lib/google/monitoring/v3/notification_service_services_pb.rb +0 -94
  95. data/lib/google/monitoring/v3/service_pb.rb +0 -149
  96. data/lib/google/monitoring/v3/service_service_pb.rb +0 -86
  97. data/lib/google/monitoring/v3/service_service_services_pb.rb +0 -65
  98. data/lib/google/monitoring/v3/span_context_pb.rb +0 -19
  99. data/lib/google/monitoring/v3/uptime_pb.rb +0 -123
  100. data/lib/google/monitoring/v3/uptime_service_pb.rb +0 -63
  101. data/lib/google/monitoring/v3/uptime_service_services_pb.rb +0 -67
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: bcfd03392d8799f7a71bb655875632abbce2bc4a283c637373084349dc86d5cf
4
- data.tar.gz: d7bdd47af9c00b35d36fdd1d1008431bb687575a3bd155d438d5e10e88dad4d5
3
+ metadata.gz: 365c5d6d1b0867ed7484a2136836ae225484b6927740022217b7e2575484a2d6
4
+ data.tar.gz: ed4521d0b55375adc950504e51e32e34939a3252cf5adba642fbd1efcd279668
5
5
  SHA512:
6
- metadata.gz: 262ab3ce3d0e384233d9b437d6de34b8d1717badaee2b86e5b5eeaf082b52f11111465a1588efbeeaf4d6d1518b8a35b9669a9bc3644657f089e14225e13c973
7
- data.tar.gz: 3a91453e0e642e9eb337ba9a3348467772aab6acf13f8f7f9a1b98f0787b5002981bff5b899c56cd33f7eb77d6699af002e0ad32fa2fec3c03d8f0c3c88acad4
6
+ metadata.gz: f27b3497cd4f7b566a6256a7b2551047d59bdaf5005ab13e33347c87b71ec5615997506b83752e67dc03d8cbbf5a2b35556131d6d851226c824563e5faa6aa74
7
+ data.tar.gz: b9e726e852589596b82e12713645a6312a1188a48eac73f7663ef32687fdbabd9dd51d3f45f159fc9f3cf30cc0a8c97dc67ada17e85c3ec24fa4edd7349b9c9b
data/.yardopts CHANGED
@@ -8,4 +8,5 @@
8
8
  -
9
9
  README.md
10
10
  AUTHENTICATION.md
11
- LICENSE
11
+ MIGRATING.md
12
+ LICENSE.md
@@ -1,16 +1,17 @@
1
1
  # Authentication
2
2
 
3
- In general, the google-cloud-monitoring library uses [Service
4
- Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
5
- credentials to connect to Google Cloud services. When running within [Google
6
- Cloud Platform environments](#google-cloud-platform-environments)
7
- the credentials will be discovered automatically. When running on other
3
+ In general, the google-cloud-monitoring library uses
4
+ [Service Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
5
+ credentials to connect to Google Cloud services. When running within
6
+ [Google Cloud Platform environments](#google-cloud-platform-environments) the
7
+ credentials will be discovered automatically. When running on other
8
8
  environments, the Service Account credentials can be specified by providing the
9
- path to the [JSON
10
- keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys) for
11
- the account (or the JSON itself) in [environment
12
- variables](#environment-variables). Additionally, Cloud SDK credentials can also
13
- be discovered automatically, but this is only recommended during development.
9
+ path to the
10
+ [JSON keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys)
11
+ for the account (or the JSON itself) in
12
+ [environment variables](#environment-variables). Additionally, Cloud SDK
13
+ credentials can also be discovered automatically, but this is only recommended
14
+ during development.
14
15
 
15
16
  ## Quickstart
16
17
 
@@ -18,7 +19,7 @@ be discovered automatically, but this is only recommended during development.
18
19
  2. Set the [environment variable](#environment-variables).
19
20
 
20
21
  ```sh
21
- export MONITORING_CREDENTIALS=/path/to/json`
22
+ export MONITORING_CREDENTIALS=path/to/keyfile.json
22
23
  ```
23
24
 
24
25
  3. Initialize the client.
@@ -26,23 +27,14 @@ export MONITORING_CREDENTIALS=/path/to/json`
26
27
  ```ruby
27
28
  require "google/cloud/monitoring"
28
29
 
29
- client = Google::Cloud::Monitoring::AlertPolicy.new
30
+ client = Google::Cloud::Monitoring.alert_policy_service
30
31
  ```
31
32
 
32
- ## Project and Credential Lookup
33
+ ## Credential Lookup
33
34
 
34
35
  The google-cloud-monitoring library aims to make authentication
35
36
  as simple as possible, and provides several mechanisms to configure your system
36
- without providing **Project ID** and **Service Account Credentials** directly in
37
- code.
38
-
39
- **Project ID** is discovered in the following order:
40
-
41
- 1. Specify project ID in method arguments
42
- 2. Specify project ID in configuration
43
- 3. Discover project ID in environment variables
44
- 4. Discover GCP project ID
45
- 5. Discover project ID in credentials JSON
37
+ without requiring **Service Account Credentials** directly in code.
46
38
 
47
39
  **Credentials** are discovered in the following order:
48
40
 
@@ -55,28 +47,24 @@ code.
55
47
 
56
48
  ### Google Cloud Platform environments
57
49
 
58
- When running on Google Cloud Platform (GCP), including Google Compute Engine (GCE),
59
- Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud Functions
60
- (GCF) and Cloud Run, the **Project ID** and **Credentials** and are discovered
61
- automatically. Code should be written as if already authenticated.
50
+ When running on Google Cloud Platform (GCP), including Google Compute Engine
51
+ (GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
52
+ Functions (GCF) and Cloud Run, **Credentials** are discovered automatically.
53
+ Code should be written as if already authenticated.
62
54
 
63
55
  ### Environment Variables
64
56
 
65
- The **Project ID** and **Credentials JSON** can be placed in environment
66
- variables instead of declaring them directly in code. Each service has its own
67
- environment variable, allowing for different service accounts to be used for
68
- different services. (See the READMEs for the individual service gems for
69
- details.) The path to the **Credentials JSON** file can be stored in the
70
- environment variable, or the **Credentials JSON** itself can be stored for
71
- environments such as Docker containers where writing files is difficult or not
72
- encouraged.
73
-
74
- The environment variables that google-cloud-monitoring checks for project ID are:
57
+ The **Credentials JSON** can be placed in environment variables instead of
58
+ declaring them directly in code. Each service has its own environment variable,
59
+ allowing for different service accounts to be used for different services. (See
60
+ the READMEs for the individual service gems for details.) The path to the
61
+ **Credentials JSON** file can be stored in the environment variable, or the
62
+ **Credentials JSON** itself can be stored for environments such as Docker
63
+ containers where writing files is difficult or not encouraged.
75
64
 
76
- 1. `MONITORING_PROJECT`
77
- 2. `GOOGLE_CLOUD_PROJECT`
78
-
79
- The environment variables that google-cloud-monitoring checks for credentials are configured on {Google::Cloud::Monitoring::V3::Credentials}:
65
+ The environment variables that google-cloud-monitoring
66
+ checks for credentials are configured on the service Credentials class (such as
67
+ `::Google::Cloud::Monitoring::V3::AlertPolicyService::Credentials`):
80
68
 
81
69
  1. `MONITORING_CREDENTIALS` - Path to JSON file, or JSON contents
82
70
  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
87
75
  ```ruby
88
76
  require "google/cloud/monitoring"
89
77
 
90
- ENV["MONITORING_PROJECT"] = "my-project-id"
91
78
  ENV["MONITORING_CREDENTIALS"] = "path/to/keyfile.json"
92
79
 
93
- client = Google::Cloud::Monitoring::AlertPolicy.new
80
+ client = Google::Cloud::Monitoring.alert_policy_service
94
81
  ```
95
82
 
96
83
  ### Configuration
97
84
 
98
- The **Project ID** and **Credentials JSON** can be configured instead of placing them in environment variables or providing them as arguments.
85
+ The **Credentials JSON** can be configured instead of placing them in
86
+ environment variables. Either on an individual client initialization:
87
+
88
+ ```ruby
89
+ require "google/cloud/monitoring"
90
+
91
+ client = Google::Cloud::Monitoring.alert_policy_service do |config|
92
+ config.credentials = "path/to/keyfile.json"
93
+ end
94
+ ```
95
+
96
+ Or configured globally for all clients:
99
97
 
100
98
  ```ruby
101
99
  require "google/cloud/monitoring"
102
100
 
103
101
  Google::Cloud::Monitoring.configure do |config|
104
- config.project_id = "my-project-id"
105
102
  config.credentials = "path/to/keyfile.json"
106
103
  end
107
104
 
108
- client = Google::Cloud::Monitoring::AlertPolicy.new
105
+ client = Google::Cloud::Monitoring.alert_policy_service
109
106
  ```
110
107
 
111
108
  ### Cloud SDK
@@ -134,24 +131,24 @@ To configure your system for this, simply:
134
131
 
135
132
  ## Creating a Service Account
136
133
 
137
- Google Cloud requires a **Project ID** and **Service Account Credentials** to
138
- connect to the APIs. You will use the **Project ID** and **JSON key file** to
134
+ Google Cloud requires **Service Account Credentials** to
135
+ connect to the APIs. You will use the **JSON key file** to
139
136
  connect to most services with google-cloud-monitoring.
140
137
 
141
- If you are not running this client within [Google Cloud Platform
142
- environments](#google-cloud-platform-environments), you need a Google
143
- Developers service account.
138
+ If you are not running this client within
139
+ [Google Cloud Platform environments](#google-cloud-platform-environments), you
140
+ need a Google Developers service account.
144
141
 
145
142
  1. Visit the [Google Developers Console][dev-console].
146
- 1. Create a new project or click on an existing project.
147
- 1. Activate the slide-out navigation tray and select **API Manager**. From
143
+ 2. Create a new project or click on an existing project.
144
+ 3. Activate the slide-out navigation tray and select **API Manager**. From
148
145
  here, you will enable the APIs that your application requires.
149
146
 
150
147
  ![Enable the APIs that your application requires][enable-apis]
151
148
 
152
149
  *Note: You may need to enable billing in order to use these services.*
153
150
 
154
- 1. Select **Credentials** from the side navigation.
151
+ 4. Select **Credentials** from the side navigation.
155
152
 
156
153
  You should see a screen like one of the following.
157
154
 
@@ -0,0 +1,203 @@
1
+ Apache License
2
+ ==============
3
+
4
+ * Version 2.0, January 2004
5
+ * https://www.apache.org/licenses/
6
+
7
+ ### TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
8
+
9
+ 1. **Definitions.**
10
+
11
+ "License" shall mean the terms and conditions for use, reproduction,
12
+ and distribution as defined by Sections 1 through 9 of this document.
13
+
14
+ "Licensor" shall mean the copyright owner or entity authorized by
15
+ the copyright owner that is granting the License.
16
+
17
+ "Legal Entity" shall mean the union of the acting entity and all
18
+ other entities that control, are controlled by, or are under common
19
+ control with that entity. For the purposes of this definition,
20
+ "control" means (i) the power, direct or indirect, to cause the
21
+ direction or management of such entity, whether by contract or
22
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
23
+ outstanding shares, or (iii) beneficial ownership of such entity.
24
+
25
+ "You" (or "Your") shall mean an individual or Legal Entity
26
+ exercising permissions granted by this License.
27
+
28
+ "Source" form shall mean the preferred form for making modifications,
29
+ including but not limited to software source code, documentation
30
+ source, and configuration files.
31
+
32
+ "Object" form shall mean any form resulting from mechanical
33
+ transformation or translation of a Source form, including but
34
+ not limited to compiled object code, generated documentation,
35
+ and conversions to other media types.
36
+
37
+ "Work" shall mean the work of authorship, whether in Source or
38
+ Object form, made available under the License, as indicated by a
39
+ copyright notice that is included in or attached to the work
40
+ (an example is provided in the Appendix below).
41
+
42
+ "Derivative Works" shall mean any work, whether in Source or Object
43
+ form, that is based on (or derived from) the Work and for which the
44
+ editorial revisions, annotations, elaborations, or other modifications
45
+ represent, as a whole, an original work of authorship. For the purposes
46
+ of this License, Derivative Works shall not include works that remain
47
+ separable from, or merely link (or bind by name) to the interfaces of,
48
+ the Work and Derivative Works thereof.
49
+
50
+ "Contribution" shall mean any work of authorship, including
51
+ the original version of the Work and any modifications or additions
52
+ to that Work or Derivative Works thereof, that is intentionally
53
+ submitted to Licensor for inclusion in the Work by the copyright owner
54
+ or by an individual or Legal Entity authorized to submit on behalf of
55
+ the copyright owner. For the purposes of this definition, "submitted"
56
+ means any form of electronic, verbal, or written communication sent
57
+ to the Licensor or its representatives, including but not limited to
58
+ communication on electronic mailing lists, source code control systems,
59
+ and issue tracking systems that are managed by, or on behalf of, the
60
+ Licensor for the purpose of discussing and improving the Work, but
61
+ excluding communication that is conspicuously marked or otherwise
62
+ designated in writing by the copyright owner as "Not a Contribution."
63
+
64
+ "Contributor" shall mean Licensor and any individual or Legal Entity
65
+ on behalf of whom a Contribution has been received by Licensor and
66
+ subsequently incorporated within the Work.
67
+
68
+ 2. **Grant of Copyright License.** Subject to the terms and conditions of
69
+ this License, each Contributor hereby grants to You a perpetual,
70
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
71
+ copyright license to reproduce, prepare Derivative Works of,
72
+ publicly display, publicly perform, sublicense, and distribute the
73
+ Work and such Derivative Works in Source or Object form.
74
+
75
+ 3. **Grant of Patent License.** Subject to the terms and conditions of
76
+ this License, each Contributor hereby grants to You a perpetual,
77
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
78
+ (except as stated in this section) patent license to make, have made,
79
+ use, offer to sell, sell, import, and otherwise transfer the Work,
80
+ where such license applies only to those patent claims licensable
81
+ by such Contributor that are necessarily infringed by their
82
+ Contribution(s) alone or by combination of their Contribution(s)
83
+ with the Work to which such Contribution(s) was submitted. If You
84
+ institute patent litigation against any entity (including a
85
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
86
+ or a Contribution incorporated within the Work constitutes direct
87
+ or contributory patent infringement, then any patent licenses
88
+ granted to You under this License for that Work shall terminate
89
+ as of the date such litigation is filed.
90
+
91
+ 4. **Redistribution.** You may reproduce and distribute copies of the
92
+ Work or Derivative Works thereof in any medium, with or without
93
+ modifications, and in Source or Object form, provided that You
94
+ meet the following conditions:
95
+
96
+ * **(a)** You must give any other recipients of the Work or
97
+ Derivative Works a copy of this License; and
98
+
99
+ * **(b)** You must cause any modified files to carry prominent notices
100
+ stating that You changed the files; and
101
+
102
+ * **(c)** You must retain, in the Source form of any Derivative Works
103
+ that You distribute, all copyright, patent, trademark, and
104
+ attribution notices from the Source form of the Work,
105
+ excluding those notices that do not pertain to any part of
106
+ the Derivative Works; and
107
+
108
+ * **(d)** If the Work includes a "NOTICE" text file as part of its
109
+ distribution, then any Derivative Works that You distribute must
110
+ include a readable copy of the attribution notices contained
111
+ within such NOTICE file, excluding those notices that do not
112
+ pertain to any part of the Derivative Works, in at least one
113
+ of the following places: within a NOTICE text file distributed
114
+ as part of the Derivative Works; within the Source form or
115
+ documentation, if provided along with the Derivative Works; or,
116
+ within a display generated by the Derivative Works, if and
117
+ wherever such third-party notices normally appear. The contents
118
+ of the NOTICE file are for informational purposes only and
119
+ do not modify the License. You may add Your own attribution
120
+ notices within Derivative Works that You distribute, alongside
121
+ or as an addendum to the NOTICE text from the Work, provided
122
+ that such additional attribution notices cannot be construed
123
+ as modifying the License.
124
+
125
+ You may add Your own copyright statement to Your modifications and
126
+ may provide additional or different license terms and conditions
127
+ for use, reproduction, or distribution of Your modifications, or
128
+ for any such Derivative Works as a whole, provided Your use,
129
+ reproduction, and distribution of the Work otherwise complies with
130
+ the conditions stated in this License.
131
+
132
+ 5. **Submission of Contributions.** Unless You explicitly state otherwise,
133
+ any Contribution intentionally submitted for inclusion in the Work
134
+ by You to the Licensor shall be under the terms and conditions of
135
+ this License, without any additional terms or conditions.
136
+ Notwithstanding the above, nothing herein shall supersede or modify
137
+ the terms of any separate license agreement you may have executed
138
+ with Licensor regarding such Contributions.
139
+
140
+ 6. **Trademarks.** This License does not grant permission to use the trade
141
+ names, trademarks, service marks, or product names of the Licensor,
142
+ except as required for reasonable and customary use in describing the
143
+ origin of the Work and reproducing the content of the NOTICE file.
144
+
145
+ 7. **Disclaimer of Warranty.** Unless required by applicable law or
146
+ agreed to in writing, Licensor provides the Work (and each
147
+ Contributor provides its Contributions) on an "AS IS" BASIS,
148
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
149
+ implied, including, without limitation, any warranties or conditions
150
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
151
+ PARTICULAR PURPOSE. You are solely responsible for determining the
152
+ appropriateness of using or redistributing the Work and assume any
153
+ risks associated with Your exercise of permissions under this License.
154
+
155
+ 8. **Limitation of Liability.** In no event and under no legal theory,
156
+ whether in tort (including negligence), contract, or otherwise,
157
+ unless required by applicable law (such as deliberate and grossly
158
+ negligent acts) or agreed to in writing, shall any Contributor be
159
+ liable to You for damages, including any direct, indirect, special,
160
+ incidental, or consequential damages of any character arising as a
161
+ result of this License or out of the use or inability to use the
162
+ Work (including but not limited to damages for loss of goodwill,
163
+ work stoppage, computer failure or malfunction, or any and all
164
+ other commercial damages or losses), even if such Contributor
165
+ has been advised of the possibility of such damages.
166
+
167
+ 9. **Accepting Warranty or Additional Liability.** While redistributing
168
+ the Work or Derivative Works thereof, You may choose to offer,
169
+ and charge a fee for, acceptance of support, warranty, indemnity,
170
+ or other liability obligations and/or rights consistent with this
171
+ License. However, in accepting such obligations, You may act only
172
+ on Your own behalf and on Your sole responsibility, not on behalf
173
+ of any other Contributor, and only if You agree to indemnify,
174
+ defend, and hold each Contributor harmless for any liability
175
+ incurred by, or claims asserted against, such Contributor by reason
176
+ of your accepting any such warranty or additional liability.
177
+
178
+ _END OF TERMS AND CONDITIONS_
179
+
180
+ ### APPENDIX: How to apply the Apache License to your work.
181
+
182
+ To apply the Apache License to your work, attach the following
183
+ boilerplate notice, with the fields enclosed by brackets "`[]`"
184
+ replaced with your own identifying information. (Don't include
185
+ the brackets!) The text should be enclosed in the appropriate
186
+ comment syntax for the file format. We also recommend that a
187
+ file or class name and description of purpose be included on the
188
+ same "printed page" as the copyright notice for easier
189
+ identification within third-party archives.
190
+
191
+ Copyright [yyyy] [name of copyright owner]
192
+
193
+ Licensed under the Apache License, Version 2.0 (the "License");
194
+ you may not use this file except in compliance with the License.
195
+ You may obtain a copy of the License at
196
+
197
+ https://www.apache.org/licenses/LICENSE-2.0
198
+
199
+ Unless required by applicable law or agreed to in writing, software
200
+ distributed under the License is distributed on an "AS IS" BASIS,
201
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
202
+ See the License for the specific language governing permissions and
203
+ limitations under the License.
@@ -0,0 +1,361 @@
1
+ ## Migrating to google-cloud-monitoring 1.0
2
+
3
+ The 1.0 release of the google-cloud-monitoring client is a significant upgrade
4
+ based on a [next-gen code generator](https://github.com/googleapis/gapic-generator-ruby),
5
+ and includes substantial interface changes. Existing code written for earlier
6
+ versions of this library will likely require updates to use this version.
7
+ This document describes the changes that have been made, and what you need to
8
+ do to update your usage.
9
+
10
+ To summarize:
11
+
12
+ * The library has been broken out into multiple libraries. The new gems
13
+ `google-cloud-monitoring-v3` and `google-cloud-monitoring-dashboard-v1`
14
+ contain the actual client classes for version V3 of the monitoring service
15
+ and version V1 of the monitoring-dashboard service, respectively, and the
16
+ gem `google-cloud-monitoring` now simply provides a convenience wrapper.
17
+ See [Library Structure](#library-structure) for more info.
18
+ * The library uses a new configuration mechanism giving you closer control
19
+ over endpoint address, network timeouts, and retry. See
20
+ [Client Configuration](#client-configuration) for more info. Furthermore,
21
+ when creating a client object, you can customize its configuration in a
22
+ block rather than passing arguments to the constructor. See
23
+ [Creating Clients](#creating-clients) for more info.
24
+ * Previously, positional arguments were used to indicate required arguments.
25
+ Now, all method arguments are keyword arguments, with documentation that
26
+ specifies whether they are required or optional. Additionally, you can pass
27
+ a proto request object instead of separate arguments. See
28
+ [Passing Arguments](#passing-arguments) for more info.
29
+ * Previously, some client classes included class methods for constructing
30
+ resource paths. These paths are now instance methods on the client objects,
31
+ and are also available in a separate paths module. See
32
+ [Resource Path Helpers](#resource-path-helpers) for more info.
33
+ * Previously, clients reported RPC errors by raising instances of
34
+ `Google::Gax::GaxError` and its subclasses. Now, RPC exceptions are of type
35
+ `Google::Cloud::Error` and its subclasses. See
36
+ [Handling Errors](#handling-errors) for more info.
37
+ * Some classes have moved into different namespaces. See
38
+ [Class Namespaces](#class-namespaces) for more info.
39
+
40
+ ### Library Structure
41
+
42
+ Older 0.x releases of the `google-cloud-monitoring` gem were all-in-one gems
43
+ that included multiple clients for potentially multiple versions of the various
44
+ monitoring-related services. Factory methods such as `Google::Cloud::Monitoring::Metric.new`
45
+ would return you instances of the actual client classes such as
46
+ `Google::Cloud::Monitoring::V3::MetricServiceClient`. These classes were all
47
+ defined in the same gem.
48
+
49
+ With the 1.0 release, the `google-cloud-monitoring` gem still provides factory
50
+ methods for obtaining clients. (The method signatures will have changed. See
51
+ [Creating Clients](#creating-clients) for details.) However, the actual client
52
+ classes have been moved into separate gems, one per service and version. The
53
+ `Google::Cloud::Monitoring::V3::MetricService::Client` class, along with its
54
+ helpers and data types, is now part of the `google-cloud-monitoring-v3` gem.
55
+ Similarly, the `Google::Cloud::Monitoring::Dashboard::V1::DashboardsService::Client`
56
+ class is part of the `google-cloud-monitoring-dashboard-v1` gem.
57
+
58
+ For normal usage, you can continue to install the `google-cloud-monitoring` gem
59
+ (which will bring in the various client gems as dependencies) and continue to
60
+ use factory methods to create clients. However, you may alternatively choose to
61
+ install only one of the versioned gems. For example, if you know you will only
62
+ use `V3` of the base monitoring service, you can install `google-cloud-monitoring-v3` by
63
+ itself, and construct instances of the `Google::Cloud::Monitoring::V3::*` client
64
+ classes directly.
65
+
66
+ ### Client Configuration
67
+
68
+ In older releases, if you wanted to customize performance parameters or
69
+ low-level behavior of the client (such as credentials, timeouts, or
70
+ instrumentation), you would pass a variety of keyword arguments to the client
71
+ constructor. It was also extremely difficult to customize the default settings.
72
+
73
+ With the 1.0 release, a configuration interface provides control over these
74
+ parameters, including defaults for all instances of a client, and settings for
75
+ each specific client instance. For example, to set default credentials and
76
+ timeout for all Monitoring V3 MetricService clients:
77
+
78
+ ```
79
+ Google::Cloud::Monitoring::V3::MetricService::Client.configure do |config|
80
+ config.credentials = "/path/to/credentials.json"
81
+ config.timeout = 10.0
82
+ end
83
+ ```
84
+
85
+ Individual RPCs can also be configured independently. For example, to set the
86
+ timeout for the `create_metric_descriptor` call:
87
+
88
+ ```
89
+ Google::Cloud::Monitoring::V3::MetricService::Client.configure do |config|
90
+ config.rpcs.create_metric_descriptor.timeout = 20.0
91
+ end
92
+ ```
93
+
94
+ Defaults for certain configurations can be set for all Monitoring versions and
95
+ services globally:
96
+
97
+ ```
98
+ Google::Cloud::Monitoring.configure do |config|
99
+ config.credentials = "/path/to/credentials.json"
100
+ config.timeout = 10.0
101
+ end
102
+ ```
103
+
104
+ Finally, you can override the configuration for each client instance. See the
105
+ next section on [Creating Clients](#creating-clients) for details.
106
+
107
+ ### Creating Clients
108
+
109
+ In older releases, to create a client object, you would use the `new` method
110
+ of modules under `Google::Cloud::Monitoring`. For example, you might call
111
+ `Google::Cloud::Monitoring::Metric.new`. Keyword arguments were available to
112
+ select a service version and to configure parameters such as credentials and
113
+ timeouts.
114
+
115
+ With the 1.0 release, use named class methods of `Google::Cloud::Monitoring` to
116
+ create a client object. For example, `Google::Cloud::Monitoring.metric_service`.
117
+ You may select a service version using the `:version` keyword argument.
118
+ However, other configuration parameters should be set in a configuration block
119
+ when you create the client.
120
+
121
+ Old:
122
+ ```
123
+ client = Google::Cloud::Monitoring::Metric.new credentials: "/path/to/credentials.json"
124
+ ```
125
+
126
+ New:
127
+ ```
128
+ client = Google::Cloud::Monitoring.metric_service do |config|
129
+ config.credentials = "/path/to/credentials.json"
130
+ end
131
+ ```
132
+
133
+ The configuration block is optional. If you do not provide it, or you do not
134
+ set some configuration parameters, then the default configuration is used. See
135
+ [Client Configuration](#client-configuration).
136
+
137
+ A similar change was made for the monitoring dashboards service:
138
+
139
+ Old:
140
+ ```
141
+ client = Google::Cloud::Monitoring::Dashboard.new credentials: "/path/to/credentials.json"
142
+ ```
143
+
144
+ New:
145
+ ```
146
+ client = Google::Cloud::Monitoring::Dashboard.dashboards_service do |config|
147
+ config.credentials = "/path/to/credentials.json"
148
+ end
149
+ ```
150
+
151
+ ### Passing Arguments
152
+
153
+ In older releases, required arguments would be passed as positional method
154
+ arguments, while most optional arguments would be passed as keyword arguments.
155
+
156
+ With the 1.0 release, all RPC arguments are passed as keyword arguments,
157
+ regardless of whether they are required or optional. For example:
158
+
159
+ Old:
160
+ ```
161
+ client = Google::Cloud::Monitoring::Metric.new
162
+
163
+ name = "projects/my-project"
164
+
165
+ # The required name argument is positional, while the optional page_size
166
+ # argument is a keyword argument
167
+ response = client.list_metric_descriptors name, page_size: 10
168
+ ```
169
+
170
+ New:
171
+ ```
172
+ client = Google::Cloud::Monitoring.metric_service
173
+
174
+ name = "projects/my-project"
175
+
176
+ # All arguments are keyword arguments
177
+ response = client.list_metric_descriptors name: name, page_size: 10
178
+ ```
179
+
180
+ In the 1.0 release, it is also possible to pass a request object, either
181
+ as a hash or as a protocol buffer.
182
+
183
+ New:
184
+ ```
185
+ client = Google::Cloud::Monitoring.metric_service
186
+
187
+ request = Google::Cloud::Monitoring::V3::ListMetricDescriptorsRequest.new(
188
+ name: "projects/my-project",
189
+ page_size: 10
190
+ )
191
+
192
+ # Pass a request object as a positional argument:
193
+ response = client.list_metric_descriptors request
194
+ ```
195
+
196
+ Finally, in older releases, to provide call options, you would pass a
197
+ `Google::Gax::CallOptions` object with the `:options` keyword argument. In the
198
+ 1.0 release, pass call options using a _second set_ of keyword arguments.
199
+
200
+ Old:
201
+ ```
202
+ client = Google::Cloud::Monitoring::Metric.new
203
+
204
+ name = "projects/my-project"
205
+
206
+ options = Google::Gax::CallOptions.new timeout: 10.0
207
+
208
+ response = client.list_metric_descriptors name, page_size: 10, options: options
209
+ ```
210
+
211
+ New:
212
+ ```
213
+ client = Google::Cloud::Monitoring.metric_service
214
+
215
+ name = "projects/my-project"
216
+
217
+ # Use a hash to wrap the normal call arguments (or pass a request object), and
218
+ # then add further keyword arguments for the call options.
219
+ response = client.list_metric_descriptors(
220
+ { name: name, page_size: 10 },
221
+ timeout: 10.0)
222
+ ```
223
+
224
+ ### Resource Path Helpers
225
+
226
+ The client library includes helper methods for generating the resource path
227
+ strings passed to many calls. These helpers have changed in two ways:
228
+
229
+ * In older releases, they are _class_ methods on the client class. In the 1.0
230
+ release, they are _instance_ methods on the client. They are also available
231
+ on a separate paths module that you can include elsewhere for convenience.
232
+ * In older releases, arguments to a resource path helper are passed as
233
+ _positional_ arguments. In the 1.0 release, they are passed as named _keyword_
234
+ arguments. Some helpers also support different sets of arguments, each set
235
+ corresponding to a different type of path.
236
+
237
+ Following is an example involving using a resource path helper.
238
+
239
+ Old:
240
+ ```
241
+ client = Google::Cloud::Monitoring::UptimeCheck.new
242
+
243
+ # Call the helper on the client class
244
+ name = Google::Cloud::Monitoring::V3::UptimeCheckServiceClient.
245
+ uptime_check_config_path("my-project", "my-uptime-check")
246
+
247
+ response = client.get_uptime_check_config name
248
+ ```
249
+
250
+ New:
251
+ ```
252
+ client = Google::Cloud::Monitoring.uptime_check_service
253
+
254
+ # Call the helper on the client instance, and use keyword arguments
255
+ name = client.uptime_check_config_path project: "my-project",
256
+ uptime_check_config: "my-uptime-check"
257
+
258
+ response = client.get_uptime_check_config name: name
259
+ ```
260
+
261
+ Because helpers take keyword arguments, some can now generate several different
262
+ variations on the path that were not available under earlier versions of the
263
+ library. For example, `get_uptime_check_config` can generate paths with either
264
+ a project, an organization, or a folder as the parent resource.
265
+
266
+ New:
267
+ ```
268
+ client = Google::Cloud::Monitoring.uptime_check_service
269
+
270
+ # Create paths with different parent resource types
271
+ name = client.uptime_check_config_path project: "my-project",
272
+ uptime_check_config: "my-uptime-check"
273
+ # => "projects/my-project/uptimeCheckConfigs/my-uptime-check"
274
+ name = client.uptime_check_config_path folder: "my-folder",
275
+ uptime_check_config: "my-uptime-check"
276
+ # => "folders/my-folder/uptimeCheckConfigs/my-uptime-check"
277
+ ```
278
+
279
+ Finally, in the 1.0 client, you can also use the paths module as a convenience module.
280
+
281
+ New:
282
+ ```
283
+ # Bring the path helper methods into the current class
284
+ include Google::Cloud::Monitoring::V3::UptimeCheckService::Paths
285
+
286
+ def foo
287
+ client = Google::Cloud::Monitoring.uptime_check_service
288
+
289
+ # Call the included helper method
290
+ name = uptime_check_config_path project: "my-project",
291
+ uptime_check_config: "my-uptime-check"
292
+
293
+ response = client.get_uptime_check_config name: name
294
+
295
+ # Do something with response...
296
+ end
297
+ ```
298
+
299
+ ### Handling Errors
300
+
301
+ The client reports standard
302
+ [gRPC error codes](https://github.com/grpc/grpc/blob/master/doc/statuscodes.md)
303
+ by raising exceptions. In older releases, these exceptions were located in the
304
+ `Google::Gax` namespace and were subclasses of the `Google::Gax::GaxError` base
305
+ exception class, defined in the `google-gax` gem. However, these classes were
306
+ different from the standard exceptions (subclasses of `Google::Cloud::Error`)
307
+ thrown by other client libraries such as `google-cloud-storage`.
308
+
309
+ The 1.0 client library now uses the `Google::Cloud::Error` exception hierarchy
310
+ for consistency across all the Google Cloud client libraries. In general, these
311
+ exceptions have the same name as their counterparts from older releases, but
312
+ are located in the `Google::Cloud` namespace rather than the `Google::Gax`
313
+ namespace.
314
+
315
+ Old:
316
+ ```
317
+ client = Google::Cloud::Monitoring::Metric.new
318
+
319
+ name = "projects/my-project"
320
+
321
+ begin
322
+ response = client.list_metric_descriptors name, page_size: 10
323
+ rescue Google::Gax::Error => e
324
+ # Handle exceptions that subclass Google::Gax::Error
325
+ end
326
+ ```
327
+
328
+ New:
329
+ ```
330
+ client = Google::Cloud::Monitoring.metric_service
331
+
332
+ name = "projects/my-project"
333
+
334
+ begin
335
+ response = client.list_metric_descriptors name: name, page_size: 10
336
+ rescue Google::Cloud::Error => e
337
+ # Handle exceptions that subclass Google::Cloud::Error
338
+ end
339
+ ```
340
+
341
+ ### Class Namespaces
342
+
343
+ In older releases, some data type (protobuf) classes were located under the module
344
+ `Google::Monitoring`. In the 1.0 release, these classes have been moved into the
345
+ same `Google::Cloud::Monitoring` module by the client object, for consistency.
346
+
347
+ In older releases, the client object was of classes with names like:
348
+ `Google::Cloud::Monitoring::V3::MetricServiceClient`.
349
+ In the 1.0 release, the client object is of a different class:
350
+ `Google::Cloud::Monitoring::V3::MetricService::Client`.
351
+ Note that most users will use the factory methods such as
352
+ `Google::Cloud::Monitoring.metric_service` to create instances of the client object,
353
+ so you may not need to reference the actual class directly.
354
+ See [Creating Clients](#creating-clients).
355
+
356
+ In older releases, the credentials object was of class
357
+ `Google::Cloud::Monitoring::V3::Credentials`.
358
+ In the 1.0 release, each service has its own credentials class, e.g.
359
+ `Google::Cloud::Monitoring::V3::MetricService::Credentials`.
360
+ Again, most users will not need to reference this class directly.
361
+ See [Client Configuration](#client-configuration).