google-cloud-monitoring 0.34.0 → 0.34.1
Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 2989412a8e8a0e50f2f00ba103b9a7d70b9d2b56c3f09fceb88896aacfbf2808
|
|
4
|
+
data.tar.gz: d739809f49b8bfe4b30d18170d19ce37459014f8d3d2250d09a1154cdd36bdf7
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 5ac878bd917ab65b222ae986dffb1e198109886e4ad5cc5444f79620786c331e2706a658b1d9fac2cd509a7ee77ff2b00279029746521b4f6a6e05d713fbd03c
|
|
7
|
+
data.tar.gz: 6a7d8a60a79dbe2c7606449072584bb8cb3aaec21d4fde8881c9a89b3db5e1ffade887c1777b3224046173ba9d763396c20b977a2d2ea850b1bff5e15a89fb90
|
|
@@ -49,6 +49,58 @@ module Google
|
|
|
49
49
|
# Some combinations of `metric_kind` and `value_type` might not be supported.
|
|
50
50
|
# @!attribute [rw] unit
|
|
51
51
|
# @return [String]
|
|
52
|
+
# The units in which the metric value is reported. It is only applicable
|
|
53
|
+
# if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
|
|
54
|
+
# defines the representation of the stored metric values.
|
|
55
|
+
#
|
|
56
|
+
# Different systems may scale the values to be more easily displayed (so a
|
|
57
|
+
# value of `0.02KBy` _might_ be displayed as `20By`, and a value of
|
|
58
|
+
# `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
|
|
59
|
+
# `KBy`, then the value of the metric is always in thousands of bytes, no
|
|
60
|
+
# matter how it may be displayed..
|
|
61
|
+
#
|
|
62
|
+
# If you want a custom metric to record the exact number of CPU-seconds used
|
|
63
|
+
# by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
|
|
64
|
+
# `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
|
|
65
|
+
# CPU-seconds, then the value is written as `12005`.
|
|
66
|
+
#
|
|
67
|
+
# Alternatively, if you want a custome metric to record data in a more
|
|
68
|
+
# granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
|
|
69
|
+
# `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
|
|
70
|
+
# or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
|
|
71
|
+
#
|
|
72
|
+
# The supported units are a subset of [The Unified Code for Units of
|
|
73
|
+
# Measure](http://unitsofmeasure.org/ucum.html) standard:
|
|
74
|
+
#
|
|
75
|
+
# **Basic units (UNIT)**
|
|
76
|
+
#
|
|
77
|
+
# * `bit` bit
|
|
78
|
+
# * `By` byte
|
|
79
|
+
# * `s` second
|
|
80
|
+
# * `min` minute
|
|
81
|
+
# * `h` hour
|
|
82
|
+
# * `d` day
|
|
83
|
+
#
|
|
84
|
+
# **Prefixes (PREFIX)**
|
|
85
|
+
#
|
|
86
|
+
# * `k` kilo (10^3)
|
|
87
|
+
# * `M` mega (10^6)
|
|
88
|
+
# * `G` giga (10^9)
|
|
89
|
+
# * `T` tera (10^12)
|
|
90
|
+
# * `P` peta (10^15)
|
|
91
|
+
# * `E` exa (10^18)
|
|
92
|
+
# * `Z` zetta (10^21)
|
|
93
|
+
# * `Y` yotta (10^24)
|
|
94
|
+
#
|
|
95
|
+
# * `m` milli (10^-3)
|
|
96
|
+
# * `u` micro (10^-6)
|
|
97
|
+
# * `n` nano (10^-9)
|
|
98
|
+
# * `p` pico (10^-12)
|
|
99
|
+
# * `f` femto (10^-15)
|
|
100
|
+
# * `a` atto (10^-18)
|
|
101
|
+
# * `z` zepto (10^-21)
|
|
102
|
+
# * `y` yocto (10^-24)
|
|
103
|
+
#
|
|
52
104
|
# * `Ki` kibi (2^10)
|
|
53
105
|
# * `Mi` mebi (2^20)
|
|
54
106
|
# * `Gi` gibi (2^30)
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: google-cloud-monitoring
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.34.
|
|
4
|
+
version: 0.34.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Google LLC
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2019-12-
|
|
11
|
+
date: 2019-12-20 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: google-gax
|