@google-cloud/logging - npm Package Compare versions

Comparing version 6.0.0 to 7.0.0

build/src/index.d.ts

@@ -30,3 +30,3 @@ /*!
 import { google } from '../protos/protos';
-export interface LoggingOptions extends gax.GoogleAuthOptions {
+export interface LoggingOptions extends gax.GrpcClientOptions {
     autoRetry?: boolean;
@@ -33,0 +33,0 @@ maxRetries?: number;

build/src/metadata.d.ts

@@ -64,3 +64,3 @@ /*!
         cluster_name: any;
-        namespace_id: string;
+        namespace_name: string;
     };
@@ -67,0 +67,0 @@ }>;

build/src/metadata.js

@@ -114,6 +114,6 @@ "use strict";
     return {
-        type: 'container',
+        type: 'k8s_container',
         labels: {
             cluster_name: resp,
-            namespace_id: namespace,
+            namespace_name: namespace,
         },
@@ -120,0 +120,0 @@ };

build/src/v2/doc/google/api/doc_metric.js

@@ -59,2 +59,54 @@ // Copyright 2019 Google LLC
  * @property {string} unit
+ *   The units in which the metric value is reported. It is only applicable
+ *   if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
+ *   defines the representation of the stored metric values.
+ *
+ *   Different systems may scale the values to be more easily displayed (so a
+ *   value of `0.02KBy` _might_ be displayed as `20By`, and a value of
+ *   `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
+ *   `KBy`, then the value of the metric is always in thousands of bytes, no
+ *   matter how it may be displayed..
+ *
+ *   If you want a custom metric to record the exact number of CPU-seconds used
+ *   by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
+ *   `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
+ *   CPU-seconds, then the value is written as `12005`.
+ *
+ *   Alternatively, if you want a custome metric to record data in a more
+ *   granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
+ *   `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
+ *   or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
+ *
+ *   The supported units are a subset of [The Unified Code for Units of
+ *   Measure](http://unitsofmeasure.org/ucum.html) standard:
+ *
+ *   **Basic units (UNIT)**
+ *
+ *   * `bit`   bit
+ *   * `By`    byte
+ *   * `s`     second
+ *   * `min`   minute
+ *   * `h`     hour
+ *   * `d`     day
+ *
+ *   **Prefixes (PREFIX)**
+ *
+ *   * `k`     kilo    (10^3)
+ *   * `M`     mega    (10^6)
+ *   * `G`     giga    (10^9)
+ *   * `T`     tera    (10^12)
+ *   * `P`     peta    (10^15)
+ *   * `E`     exa     (10^18)
+ *   * `Z`     zetta   (10^21)
+ *   * `Y`     yotta   (10^24)
+ *
+ *   * `m`     milli   (10^-3)
+ *   * `u`     micro   (10^-6)
+ *   * `n`     nano    (10^-9)
+ *   * `p`     pico    (10^-12)
+ *   * `f`     femto   (10^-15)
+ *   * `a`     atto    (10^-18)
+ *   * `z`     zepto   (10^-21)
+ *   * `y`     yocto   (10^-24)
+ *
  *   * `Ki`    kibi    (2^10)
@@ -61,0 +113,0 @@ *   * `Mi`    mebi    (2^20)

build/src/v2/v2/doc/google/api/doc_metric.js

@@ -59,2 +59,54 @@ // Copyright 2019 Google LLC
  * @property {string} unit
+ *   The units in which the metric value is reported. It is only applicable
+ *   if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
+ *   defines the representation of the stored metric values.
+ *
+ *   Different systems may scale the values to be more easily displayed (so a
+ *   value of `0.02KBy` _might_ be displayed as `20By`, and a value of
+ *   `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
+ *   `KBy`, then the value of the metric is always in thousands of bytes, no
+ *   matter how it may be displayed..
+ *
+ *   If you want a custom metric to record the exact number of CPU-seconds used
+ *   by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
+ *   `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
+ *   CPU-seconds, then the value is written as `12005`.
+ *
+ *   Alternatively, if you want a custome metric to record data in a more
+ *   granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
+ *   `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
+ *   or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
+ *
+ *   The supported units are a subset of [The Unified Code for Units of
+ *   Measure](http://unitsofmeasure.org/ucum.html) standard:
+ *
+ *   **Basic units (UNIT)**
+ *
+ *   * `bit`   bit
+ *   * `By`    byte
+ *   * `s`     second
+ *   * `min`   minute
+ *   * `h`     hour
+ *   * `d`     day
+ *
+ *   **Prefixes (PREFIX)**
+ *
+ *   * `k`     kilo    (10^3)
+ *   * `M`     mega    (10^6)
+ *   * `G`     giga    (10^9)
+ *   * `T`     tera    (10^12)
+ *   * `P`     peta    (10^15)
+ *   * `E`     exa     (10^18)
+ *   * `Z`     zetta   (10^21)
+ *   * `Y`     yotta   (10^24)
+ *
+ *   * `m`     milli   (10^-3)
+ *   * `u`     micro   (10^-6)
+ *   * `n`     nano    (10^-9)
+ *   * `p`     pico    (10^-12)
+ *   * `f`     femto   (10^-15)
+ *   * `a`     atto    (10^-18)
+ *   * `z`     zepto   (10^-21)
+ *   * `y`     yocto   (10^-24)
+ *
  *   * `Ki`    kibi    (2^10)
@@ -61,0 +113,0 @@ *   * `Mi`    mebi    (2^20)

CHANGELOG.md

@@ -7,2 +7,20 @@ # Changelog
 
+## [7.0.0](https://www.github.com/googleapis/nodejs-logging/compare/v6.0.0...v7.0.0) (2020-01-09)
+
+
+### ⚠ BREAKING CHANGES
+
+* if using GKE, "Kubernetes Container" type is now properly populated, and logs will be grouped accordingly.
+
+### Features
+
+* **samples:** increase logging client scope ([#670](https://www.github.com/googleapis/nodejs-logging/issues/670)) ([5f35601](https://www.github.com/googleapis/nodejs-logging/commit/5f356014d72a523fc7061caf7bd0143166af6c91))
+
+
+### Bug Fixes
+
+* populate k8s_container rather than container ([#674](https://www.github.com/googleapis/nodejs-logging/issues/674)) ([fa32048](https://www.github.com/googleapis/nodejs-logging/commit/fa3204877cf6f6b943950994d49c0f7d7def5096))
+* **docs:** point folks towards the appropriate client instantiation ([091d7dd](https://www.github.com/googleapis/nodejs-logging/commit/091d7dd28d5f50cb0cf274bb370b36cdf612d42a))
+* **types:** extend constructor options from gax ([#676](https://www.github.com/googleapis/nodejs-logging/issues/676)) ([5156538](https://www.github.com/googleapis/nodejs-logging/commit/51565388f25ef16d7ab9c20c1d96e2a4adb78149))
+
 ## [6.0.0](https://www.github.com/googleapis/nodejs-logging/compare/v5.5.5...v6.0.0) (2019-12-06)
@@ -9,0 +27,0 @@

package.json

 {
   "name": "@google-cloud/logging",
   "description": "Stackdriver Logging Client Library for Node.js",
-  "version": "6.0.0",
+  "version": "7.0.0",
   "license": "Apache-2.0",
@@ -87,9 +87,9 @@ "author": "Google Inc.",
     "bignumber.js": "^9.0.0",
-    "c8": "^6.0.1",
+    "c8": "^7.0.0",
     "codecov": "^3.0.4",
     "eslint": "^6.0.0",
     "eslint-config-prettier": "^6.0.0",
-    "eslint-plugin-node": "^10.0.0",
+    "eslint-plugin-node": "^11.0.0",
     "eslint-plugin-prettier": "^3.0.0",
-    "execa": "^3.2.0",
+    "execa": "^4.0.0",
     "gts": "^1.0.0",
@@ -102,3 +102,3 @@ "http2spy": "^1.1.0",
     "linkinator": "^1.5.0",
-    "mocha": "^6.1.4",
+    "mocha": "^7.0.0",
     "mv": "^2.1.1",
@@ -110,3 +110,3 @@ "ncp": "^2.0.0",
     "proxyquire": "^2.1.0",
-    "sinon": "^7.2.5",
+    "sinon": "^8.0.0",
     "typescript": "3.6.4",
@@ -113,0 +113,0 @@ "uuid": "^3.3.2"

README.md

@@ -58,2 +58,5 @@ [//]: # "This README.md file is auto-generated, all changes to this file will be lost."
 ```javascript
+// Imports the Google Cloud client library
+const {Logging} = require('@google-cloud/logging');
+
 async function quickstart(
@@ -63,5 +66,2 @@ projectId = 'YOUR_PROJECT_ID', // Your Google Cloud Platform project ID
 ) {
-  // Imports the Google Cloud client library
-  const {Logging} = require('@google-cloud/logging');
-
   // Creates a client
@@ -68,0 +68,0 @@ const logging = new Logging({projectId});

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

2797334

increased by0.18%

Lines of code

51804

increased by0.2%

No dependency changes