google-cloud-error_reporting 0.30.3 → 0.30.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d68cac833a46587b17d54be984dc1f7b95413db71b73df8dd5f9e00a17f81d1d
-  data.tar.gz: d1840a538b5770c01d8dd6535c88e6ef58346b479916dec7d0600bba60b3a1d9
+  metadata.gz: f6b3875ef96a2a0861e6398e925cdbfcc86b945c29274c28a08f0a480021c468
+  data.tar.gz: b0b8f6a7bb99ea7a99a9e9fbe5c2882007fa6e5142251daa22a45314096dccda
 SHA512:
-  metadata.gz: 657ecf8a0361102b796f41ac3a74b3b8aab2523999cb19c700bc9c2046b4351387a09973e6a14a8632399ed2416e3bf50701435c1124bbd2d354488b3996f478
-  data.tar.gz: '08ddd5fdfb87aaaa2086ddb5c5650a277382c93e128037587eb6521d05a63319222b50fd656323ce546cb9f1c53f0bf532e6507d0c92e44506da9df15707c38d'
+  metadata.gz: fac501a993ac6f6bc474b0fcb9210ada3386bfd6281b003a0e334276f15e2ee8d64a4ff73fedd866ed23022a97f8401278a69f3c927e7448647f8ba8fe223431
+  data.tar.gz: 1a5136a8d82ea9d1e3733cbfd180662d9d6b4d1bb82404da3bc46b5edcdccb28f760b0c3be9b70c16ba5c99931b31c427fafc3ef5d3938462c86f80e2ab68fc7

data/AUTHENTICATION.md

@@ -0,0 +1,180 @@
+Error Reporting# Authentication
+
+In general, the google-cloud-error_reporting library uses [Service
+Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
+credentials to connect to Google Cloud services. When running on Compute Engine
+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. Additionally, Cloud
+SDK credentials can also be discovered automatically, but this is only
+recommended during development.
+
+## Project and Credential Lookup
+
+The google-cloud-error_reporting 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 GCE project ID
+
+**Credentials** are discovered in the following order:
+
+1. Specify credentials in method arguments
+2. Specify credentials in configuration
+3. Discover credentials path in environment variables
+4. Discover credentials JSON in environment variables
+5. Discover credentials file in the Cloud SDK's path
+6. Discover GCE credentials
+
+### Google Cloud Platform environments
+
+While running on Google Cloud Platform environments such as Google Compute
+Engine, Google App Engine and Google Kubernetes Engine, no extra work is needed.
+The **Project ID** and **Credentials** and are discovered automatically. Code
+should be written as if already authenticated. Just be sure when you [set up the
+GCE instance][gce-how-to], you add the correct scopes for the APIs you want to
+access. For example:
+
+  * **All APIs**
+    * `https://www.googleapis.com/auth/cloud-platform`
+    * `https://www.googleapis.com/auth/cloud-platform.read-only`
+  * **BigQuery**
+    * `https://www.googleapis.com/auth/bigquery`
+    * `https://www.googleapis.com/auth/bigquery.insertdata`
+  * **Compute Engine**
+    * `https://www.googleapis.com/auth/compute`
+  * **Datastore**
+    * `https://www.googleapis.com/auth/datastore`
+    * `https://www.googleapis.com/auth/userinfo.email`
+  * **DNS**
+    * `https://www.googleapis.com/auth/ndev.clouddns.readwrite`
+  * **Pub/Sub**
+    * `https://www.googleapis.com/auth/pubsub`
+  * **Storage**
+    * `https://www.googleapis.com/auth/devstorage.full_control`
+    * `https://www.googleapis.com/auth/devstorage.read_only`
+    * `https://www.googleapis.com/auth/devstorage.read_write`
+
+### 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 Error Reporting checks for project ID are:
+
+1. `ERROR_REPORTING_PROJECT`
+2. `GOOGLE_CLOUD_PROJECT`
+
+The environment variables that Error Reporting checks for credentials are
+configured on {Google::Cloud::ErrorReporting::V1beta1::Credentials}:
+
+1. `ERROR_REPORTING_CREDENTIALS` - Path to JSON file, or JSON contents
+2. `ERROR_REPORTING_KEYFILE` - Path to JSON file, or JSON contents
+3. `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents
+4. `GOOGLE_CLOUD_KEYFILE` - Path to JSON file, or JSON contents
+5. `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file
+
+```ruby
+require "google/cloud/error_reporting"
+
+ENV["ERROR_REPORTING_PROJECT"]     = "my-project-id"
+ENV["ERROR_REPORTING_CREDENTIALS"] = "path/to/keyfile.json"
+
+error_reporting = Google::Cloud::ErrorReporting.new
+```
+
+### Configuration
+
+The **Project ID** and **Credentials JSON** can be configured instead of placing
+them in environment variables or providing them as arguments.
+
+```ruby
+require "google/cloud/error_reporting"
+
+Google::Cloud::ErrorReporting.configure do |config|
+  config.project_id  = "my-project-id"
+  config.credentials = "path/to/keyfile.json"
+end
+
+error_reporting = Google::Cloud::ErrorReporting.new
+```
+
+### Cloud SDK
+
+This option allows for an easy way to authenticate during development. If
+credentials are not provided in code or in environment variables, then Cloud SDK
+credentials are discovered.
+
+To configure your system for this, simply:
+
+1. [Download and install the Cloud SDK](https://cloud.google.com/sdk)
+2. Authenticate using OAuth 2.0 `$ gcloud auth login`
+3. Write code as if already authenticated.
+
+**NOTE:** This is _not_ recommended for running in production. The Cloud SDK
+*should* only be used during development.
+
+[gce-how-to]: https://cloud.google.com/compute/docs/authentication#using
+[dev-console]: https://console.cloud.google.com/project
+
+[enable-apis]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/enable-apis.png
+
+[create-new-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account.png
+[create-new-service-account-existing-keys]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account-existing-keys.png
+[reuse-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/reuse-service-account.png
+
+## 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
+connect to most services with google-cloud-error_reporting.
+
+If you are not running this client on Google Compute Engine, 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
+   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.
+
+   You should see a screen like one of the following.
+
+   ![Create a new service account][create-new-service-account]
+
+   ![Create a new service account With Existing Keys][create-new-service-account-existing-keys]
+
+   Find the "Add credentials" drop down and select "Service account" to be
+   guided through downloading a new JSON key file.
+
+   If you want to re-use an existing service account, you can easily generate a
+   new key file. Just select the account you wish to re-use, and click "Generate
+   new JSON key":
+
+   ![Re-use an existing service account][reuse-service-account]
+
+   The key file you download will be used by this library to authenticate API
+   requests and should be stored in a secure location.
+
+## Troubleshooting
+
+If you're having trouble authenticating you can ask for help by following the
+{file:TROUBLESHOOTING.md Troubleshooting Guide}.

data/CHANGELOG.md

@@ -0,0 +1,102 @@
+# Release History
+
+### 0.30.4 / 2018-09-12
+
+* Add missing documentation files to package.
+
+### 0.30.3 / 2018-09-10
+
+* Update documentation.
+
+### 0.30.2 / 2018-08-21
+
+* Update documentation.
+
+### 0.30.1 / 2018-07-05
+
+* Fix undefined method for nil error when error object has empty backtrace.
+* Fix issue when disabling Stackdriver components with Rails.env.production.
+* Capture env["rack.exception"] errors from Rack env.
+* Add documentation for enabling gRPC logging.
+
+### 0.30.0 / 2018-02-27
+
+* Use Google Cloud Shared Configuration.
+
+### 0.29.0 / 2017-12-19
+
+* Update google-gax dependency to 1.0.
+
+### 0.28.1 / 2017-11-15
+
+* Fix credentials verification bug in Railtie.
+
+### 0.28.0 / 2017-11-14
+
+* Add `Google::Cloud::ErrorReporting::Credentials` class.
+* Rename constructor arguments to `project_id` and `credentials`.
+  (The previous arguments `project` and `keyfile` are still supported.)
+* Document `Google::Auth::Credentials` as `credentials` value.
+* Updated `google-gax` (`grpc`, `google-protobuf`), `googleauth` dependencies.
+
+### 0.27.0 / 2017-09-08
+
+* Rename `module_name` and `module_version` parameters to `service_name` and `service_version` respectively.
+* Print captured exception from asynchronous worker thread.
+
+### 0.26.1 / 2017-07-11
+
+* stackdriver-core 1.2.0 release
+
+### 0.26.0 / 2017-07-11
+
+* Update `Google::Cloud::ErrorReporting::Middleware` and `Google::Cloud::ErrorReporting::Railtie` to submit error events asynchronously by default.
+* Update GAPIC configuration to exclude `UNAVAILABLE` errors from automatic retry.
+
+### 0.25.0 / 2017-05-25
+
+* New Error Reporting instrumentation client.
+* Introduce simple `Google::Cloud::ErrorReporting.report` interface to easily report Ruby exception.
+* New `Google::Cloud::ErrorReporting.configure` instrumentation configuration interface.
+* `Google::Cloud::ErrorReporting::Middleware` can now be used without required parameters.
+
+### 0.24.0 / 2017-03-31
+
+* Automatic retry on `UNAVAILABLE` errors
+
+### 0.23.3 / 2017-03-03
+
+* Update GRPC header value sent to the Error Reporting API.
+
+### 0.23.2 / 2017-03-01
+
+* Update GRPC header value sent to the Error Reporting API.
+
+### 0.23.1 / 2017-02-23
+
+* Add middleware require to rails module (premist)
+
+### 0.23.0 / 2017-02-21
+
+* Fix GRPC retry bug
+* The client_config data structure has replaced retry_codes/retry_codes_def with retry_codes
+* Update GRPC/Protobuf/GAX dependencies
+
+### 0.22.0 / 2017-01-27
+
+* Update Error Reporting requires. For Rack integration, users now need to use
+  `require "google/cloud/error_reporting/middleware"` rather than
+  `require "google/cloud/error_reporting/v1beta1"`.
+* Change class names in low-level API (GAPIC)
+
+### 0.21.2 / 2016-11-03
+
+* Fixed instrumentation integration with Ruby on Rails
+
+### 0.21.1 / 2016-11-01
+
+* Fixed instrumentation integration with non-Rails Rack frameworks
+
+### 0.21.0 / 2016-10-20
+
+* First release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,40 @@
+# Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of
+fostering an open and welcoming community, we pledge to respect all people who
+contribute through reporting issues, posting feature requests, updating
+documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free
+experience for everyone, regardless of level of experience, gender, gender
+identity and expression, sexual orientation, disability, personal appearance,
+body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic
+  addresses, without explicit permission
+* Other unethical or unprofessional conduct.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct. By adopting this Code of Conduct, project
+maintainers commit themselves to fairly and consistently applying these
+principles to every aspect of managing this project. Project maintainers who do
+not follow or enforce the Code of Conduct may be permanently removed from the
+project team.
+
+This code of conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by opening an issue or contacting one or more of the project
+maintainers.
+
+This Code of Conduct is adapted from the [Contributor
+Covenant](http://contributor-covenant.org), version 1.2.0, available at
+[http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/)

data/CONTRIBUTING.md

@@ -0,0 +1,189 @@
+# Contributing to Google Cloud Error Reporting
+
+1. **Sign one of the contributor license agreements below.**
+2. Fork the repo, develop and test your code changes.
+3. Send a pull request.
+
+## Contributor License Agreements
+
+Before we can accept your pull requests you'll need to sign a Contributor
+License Agreement (CLA):
+
+- **If you are an individual writing original source code** and **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).
+
+You can sign these electronically (just scroll to the bottom). After that, we'll
+be able to accept your pull requests.
+
+## Setup
+
+In order to use the google-cloud-error_reporting console and run the project's
+tests, there is a small amount of setup:
+
+1. Install Ruby. google-cloud-error_reporting requires Ruby 2.3+. You may choose
+   to manage your Ruby and gem installations with [RVM](https://rvm.io/),
+   [rbenv](https://github.com/rbenv/rbenv), or
+   [chruby](https://github.com/postmodern/chruby).
+
+2. Install [Bundler](http://bundler.io/).
+
+   ```sh
+   $ gem install bundler
+   ```
+
+3. Install the top-level project dependencies.
+
+   ```sh
+   $ bundle install
+   ```
+
+4. Install the Error Reporting dependencies.
+
+   ```sh
+   $ cd google-cloud-error_reporting/
+   $ bundle exec rake bundleupdate
+   ```
+
+## Console
+
+In order to run code interactively, you can automatically load
+google-cloud-error_reporting and its dependencies in IRB. This requires that
+your developer environment has already been configured by following the steps
+described in the {file:AUTHENTICATION.md Authentication Guide}. An IRB console
+can be created with:
+
+```sh
+$ cd google-cloud-error_reporting/
+$ bundle exec rake console
+```
+
+## Error Reporting Tests
+
+Tests are very important part of google-cloud-error_reporting. All contributions
+should include tests that ensure the contributed code behaves as expected.
+
+To run the unit tests, documentation tests, and code style checks together for a
+package:
+
+``` sh
+$ cd google-cloud-error_reporting/
+$ bundle exec rake ci
+```
+
+To run the command above, plus all acceptance tests, use `rake ci:acceptance` or
+its handy alias, `rake ci:a`.
+
+### Error Reporting Unit Tests
+
+
+The project uses the [minitest](https://github.com/seattlerb/minitest) library,
+including [specs](https://github.com/seattlerb/minitest#specs),
+[mocks](https://github.com/seattlerb/minitest#mocks) and
+[minitest-autotest](https://github.com/seattlerb/minitest-autotest).
+
+To run the Error Reporting unit tests:
+
+``` sh
+$ cd google-cloud-error_reporting/
+$ bundle exec rake test
+```
+
+### Error Reporting Documentation Tests
+
+The project tests the code examples in the gem's
+[YARD](https://github.com/lsegal/yard)-based documentation.
+
+The example testing functions in a way that is very similar to unit testing, and
+in fact the library providing it,
+[yard-doctest](https://github.com/p0deje/yard-doctest), is based on the
+project's unit test library, [minitest](https://github.com/seattlerb/minitest).
+
+To run the Error Reporting documentation tests:
+
+``` sh
+$ cd google-cloud-error_reporting/
+$ bundle exec rake doctest
+```
+
+If you add, remove or modify documentation examples when working on a pull
+request, you may need to update the setup for the tests. The stubs and mocks
+required to run the tests are located in `support/doctest_helper.rb`. Please
+note that much of the setup is matched by the title of the
+[`@example`](http://www.rubydoc.info/gems/yard/file/docs/Tags.md#example) tag.
+If you alter an example's title, you may encounter breaking tests.
+
+### Error Reporting Acceptance Tests
+
+The Error Reporting acceptance tests interact with the live service API. Follow
+the instructions in the {file:AUTHENTICATION.md Authentication guide} for
+enabling the Error Reporting API. Occasionally, some API features may not yet be
+generally available, making it difficult for some contributors to successfully
+run the entire acceptance test suite. However, please ensure that you do
+successfully run acceptance tests for any code areas covered by your pull
+request.
+
+To run the acceptance tests, first create and configure a project in the Google
+Developers Console, as described in the {file:AUTHENTICATION.md Authentication
+guide}. Be sure to download the JSON KEY file. Make note of the PROJECT_ID and
+the KEYFILE location on your system.
+
+Before you can run the Error Reporting acceptance tests, you must first create
+indexes used in the tests.
+
+#### Running the Error Reporting acceptance tests
+
+To run the Error Reporting acceptance tests:
+
+``` sh
+$ cd google-cloud-error_reporting/
+$ bundle exec rake acceptance[\\{my-project-id},\\{/path/to/keyfile.json}]
+```
+
+Or, if you prefer you can store the values in the `GCLOUD_TEST_PROJECT` and
+`GCLOUD_TEST_KEYFILE` environment variables:
+
+``` sh
+$ cd google-cloud-error_reporting/
+$ export GCLOUD_TEST_PROJECT=\\{my-project-id}
+$ export GCLOUD_TEST_KEYFILE=\\{/path/to/keyfile.json}
+$ bundle exec rake acceptance
+```
+
+If you want to use a different project and credentials for acceptance tests, you
+can use the more specific `ERROR_REPORTING_TEST_PROJECT`  and
+`ERROR_REPORTING_TEST_KEYFILE` environment variables:
+
+``` sh
+$ cd google-cloud-error_reporting/
+$ export ERROR_REPORTING_TEST_PROJECT=\\{my-project-id}
+$ export ERROR_REPORTING_TEST_KEYFILE=\\{/path/to/keyfile.json}
+$ bundle exec rake acceptance
+```
+
+## Coding Style
+
+Please follow the established coding style in the library. The style is is
+largely based on [The Ruby Style
+Guide](https://github.com/bbatsov/ruby-style-guide) with a few exceptions based
+on seattle-style:
+
+* Avoid parenthesis when possible, including in method definitions.
+* Always use double quotes strings. ([Option
+  B](https://github.com/bbatsov/ruby-style-guide#strings))
+
+You can check your code against these rules by running Rubocop like so:
+
+```sh
+$ cd google-cloud-error_reporting/
+$ bundle exec rake rubocop
+```
+
+## Code of Conduct
+
+Please note that this project is released with a Contributor Code of Conduct. By
+participating in this project you agree to abide by its terms. See
+{file:CODE_OF_CONDUCT.md Code of Conduct} for more information.

data/INSTRUMENTATION.md

@@ -0,0 +1,91 @@
+# Stackdriver Error Reporting Instrumentation
+
+The google-cloud-error_reporting gem provides framework instrumentation features
+to make it easy to report exceptions from your application.
+
+## Quick Start
+
+```ruby
+require "google/cloud/error_reporting"
+
+# Insert a Rack Middleware to report unhanded exceptions
+use Google::Cloud::ErrorReporting::Middleware
+
+# Or explicitly submit exceptions
+begin
+  fail "Boom!"
+rescue => exception
+  Google::Cloud::ErrorReporting.report exception
+end
+```
+
+## Configuration
+The default configuration enables Stackdriver instrumentation features to run on
+Google Cloud Platform. You can easily configure the instrumentation library  if
+you want to run on a non Google Cloud environment or you want to customize  the
+default behavior.
+
+See the [Configuration
+Guide](https://googlecloudplatform.github.io/google-cloud-ruby/docs/stackdriver/latest/file.INSTRUMENTATION_CONFIGURATION)
+for full configuration parameters.
+
+## Rack Middleware and Railtie
+
+The google-cloud-error_reporting gem provides a Rack Middleware class that can
+easily integrate with Rack based application frameworks, such as Rails and
+Sinatra. When enabled, it automatically gathers application exceptions from
+requests and submits the information to the Stackdriver Error Reporting service.
+On top of that, the google-cloud-error_reporting also implements a Railtie class
+that automatically enables the Rack Middleware in Rails applications when used.
+
+### Rails Integration
+
+To use the Stackdriver Error Reporting Railtie for Ruby on Rails applications,
+simply add this line to `config/application.rb`:
+
+```ruby
+require "google/cloud/error_reporting/rails"
+```
+
+Alternatively, check out the
+[stackdriver](https://googlecloudplatform.github.io/google-cloud-ruby/docs/stackdriver/latest)
+gem, which enables this Railtie by default.
+
+### Rack Integration
+
+Other Rack-based framework can also directly leverage the Middleware directly:
+
+```ruby
+require "google/cloud/error_reporting"
+
+use Google::Cloud::ErrorReporting::Middleware
+```
+
+## Report Captured Exceptions
+Captured Ruby exceptions can be reported directly to Stackdriver Error Reporting
+by using {Google::Cloud::ErrorReporting.report}:
+
+```ruby
+begin
+  fail "Boom!"
+rescue => exception
+  Google::Cloud::ErrorReporting.report exception
+end
+```
+
+The reported error event can also be customized:
+
+```ruby
+begin
+  fail "Boom!"
+rescue => exception
+  Google::Cloud::ErrorReporting.report exception do |error_event|
+    # Directly modify the Google::Cloud::ErrorReporting::ErrorEvent object before submission
+    error_event.message     = "Custom error message"
+    error_event.user        = "johndoh@example.com"
+    error_event.http_status = 502
+  end
+end
+```
+
+See {Google::Cloud::ErrorReporting::ErrorEvent} class for all options.

data/LOGGING.md

@@ -0,0 +1,32 @@
+# Enabling gRPC Logging
+
+To enable logging for this library, set the logger for the underlying
+[gRPC](https://github.com/grpc/grpc/tree/master/src/ruby) library. The logger
+that you set may be a Ruby stdlib
+[`Logger`](https://ruby-doc.org/stdlib-2.5.0/libdoc/logger/rdoc/Logger.html) as
+shown below, or a
+[`Google::Cloud::Logging::Logger`](https://googlecloudplatform.github.io/google-cloud-ruby/docs/google-cloud-logging/latest/Google/Cloud/Logging/Logger)
+that will write logs to [Stackdriver
+Logging](https://cloud.google.com/logging/). See
+[grpc/logconfig.rb](https://github.com/grpc/grpc/blob/master/src/ruby/lib/grpc/logconfig.rb)
+and the gRPC
+[spec_helper.rb](https://github.com/grpc/grpc/blob/master/src/ruby/spec/spec_helper.rb)
+for additional information.
+
+Configuring a Ruby stdlib logger:
+
+```ruby
+require "logger"
+
+module MyLogger
+  LOGGER = Logger.new $stderr, level: Logger::WARN
+  def logger
+    LOGGER
+  end
+end
+
+# Define a gRPC module-level logger method before grpc/logconfig.rb loads.
+module GRPC
+  extend MyLogger
+end
+```

data/OVERVIEW.md

@@ -0,0 +1,48 @@
+# Error Reporting
+
+Stackdriver Error Reporting counts, analyzes and aggregates the crashes in your
+running cloud services. The Stackdriver Error Reporting Instrumentation client
+provides a simple way to report errors from your application.
+
+For general information about Stackdriver Error Reporting, read [Stackdriver
+Error Reporting Documentation](https://cloud.google.com/error-reporting/docs/).
+
+The goal of google-cloud is to provide an API that is comfortable to Rubyists.
+Your authentication credentials are detected automatically in Google Cloud
+Platform environments such as Google Compute Engine, Google App Engine and
+Google Kubernetes Engine. In other environments you can configure authentication
+easily, either directly in your code or via environment variables. Read more
+about the options for connecting in the {file:AUTHENTICATION.md Authentication
+Guide}.
+
+## How to report errors
+
+You can easily report exceptions from your applications to Stackdriver Error
+Reporting service:
+
+```ruby
+require "google/cloud/error_reporting"
+
+# Configure Stackdriver ErrorReporting instrumentation
+Google::Cloud::ErrorReporting.configure do |config|
+  config.project_id = "my-project"
+  config.keyfile = "/path/to/keyfile.json"
+end
+
+# Insert a Rack Middleware to report unhanded exceptions
+use Google::Cloud::ErrorReporting::Middleware
+
+# Or explicitly submit exceptions
+begin
+  fail "Boom!"
+rescue => exception
+  Google::Cloud::ErrorReporting.report exception
+end
+```
+
+See the {file:INSTRUMENTATION.md Instrumentation Guide} for more examples.
+
+## Additional information
+
+Stackdriver Error Reporting can be configured to use gRPC's logging. To learn more, see the
+{file:LOGGING.md Logging guide}.

data/TROUBLESHOOTING.md

@@ -0,0 +1,37 @@
+# Troubleshooting
+
+## Where can I get more help?
+
+### Ask the Community
+
+If you have a question about how to use a Google Cloud client library in your
+project or are stuck in the Developer's console and don't know where to turn,
+it's possible your questions have already been addressed by the community.
+
+First, check out the appropriate tags on StackOverflow:
+  - [`google-cloud-platform+ruby+errorreporting`][so-ruby]
+
+Next, try searching through the issues on GitHub:
+
+  - [`api:error reporting` issues][gh-search-ruby]
+
+Still nothing?
+
+### Ask the Developers
+
+If you're experiencing a bug with the code, or have an idea for how it can be
+improved, *please* create a new issue on GitHub so we can talk about it.
+
+  - [New issue][gh-ruby]
+
+Or, you can ask questions on the [Google Cloud Platform Slack][slack-ruby]. You
+can use the "ruby" channel for general Ruby questions, or use the
+"google-cloud-ruby" channel if you have questions about this gem in particular.
+
+[so-ruby]: http://stackoverflow.com/questions/tagged/google-cloud-platform+ruby+errorreporting
+
+[gh-search-ruby]: https://github.com/googlecloudplatform/google-cloud-ruby/issues?q=label%3A%22api%3A+error+reporting%22
+
+[gh-ruby]: https://github.com/googlecloudplatform/google-cloud-ruby/issues/new
+
+[slack-ruby]: https://gcp-slack.appspot.com/

data/lib/google/cloud/error_reporting/version.rb

@@ -16,7 +16,7 @@
 module Google
   module Cloud
     module ErrorReporting
-      VERSION = "0.30.3".freeze
+      VERSION = "0.30.4".freeze
     end
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-cloud-error_reporting
 version: !ruby/object:Gem::Version
-  version: 0.30.3
+  version: 0.30.4
 platform: ruby
 authors:
 - Google Inc
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-09-10 00:00:00.000000000 Z
+date: 2018-09-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-cloud-core
@@ -215,8 +215,15 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".yardopts"
+- AUTHENTICATION.md
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
+- INSTRUMENTATION.md
 - LICENSE
-- README.md
+- LOGGING.md
+- OVERVIEW.md
+- TROUBLESHOOTING.md
 - lib/google-cloud-error_reporting.rb
 - lib/google/cloud/error_reporting.rb
 - lib/google/cloud/error_reporting/async_error_reporter.rb

data/README.md

@@ -1,257 +0,0 @@
-# google-cloud-error_reporting
-
-[Stackdriver Error Reporting](https://cloud.google.com/error-reporting/) counts,
-analyzes and aggregates errors raised in your running cloud services. A
-centralized error management interface displays the results with sorting and
-filtering capabilities. A dedicated view shows the error details: time chart,
-occurrences, affected user count, first and last seen dates and a cleaned
-exception stack trace. Opt-in to receive email and mobile alerts on new errors.
-
-- [google-cloud-error_reporting API documentation](http://googlecloudplatform.github.io/google-cloud-ruby/docs/google-cloud-error_reporting/latest)
-- [google-cloud-error_reporting instrumentation documentation](https://googlecloudplatform.github.io/google-cloud-ruby/docs/google-cloud-error_reporting/latest/file.INSTRUMENTATION)
-- [google-cloud-error_reporting on RubyGems](https://rubygems.org/gems/google-cloud-error_reporting)
-- [Stackdriver ErrorReporting documentation](https://cloud.google.com/error-reporting/docs/)
-
-## Quick Start
-
-Install the gem directly:
-
-```sh
-$ gem install google-cloud-error_reporting
-```
-
-Or install through Bundler:
-
-1. Add the `google-cloud-error_reporting` gem to your Gemfile:
-
-```ruby
-gem "google-cloud-error_reporting"
-```
-
-2. Use Bundler to install the gem:
-
-```sh
-$ bundle install
-```
-
-Alternatively, check out the
-[`stackdriver`](http://googlecloudplatform.github.io/google-cloud-ruby/docs/stackdriver/latest)
-gem that includes the `google-cloud-error_reporting` gem.
-
-## Enable Stackdriver Error Reporting API
-
-The Stackdriver Error Reporting library needs the [Stackdriver Error Reporting
-API](https://console.cloud.google.com/apis/library/clouderrorreporting.googleapis.com)
-to be enabled on your Google Cloud project. Make sure it's enabled if not
-already.
-
-## Reporting errors in Rack-based frameworks
-
-The Stackdriver Error Reporting library for Ruby makes it easy to integrate
-Stackdriver Error Reporting into popular Rack-based Ruby web frameworks such as
-Ruby on Rails and Sinatra. When the library integration is enabled, it
-automatically reports exceptions captured from the application's Rack stack.
-
-### With Ruby on Rails
-
-You can load the Railtie that comes with the library into your Ruby on Rails
-application by explicitly requiring it during the application startup:
-
-```ruby
-# In config/application.rb
-require "google/cloud/error_reporting/rails"
-```
-
-If you're using the `stackdriver` gem, it automatically loads the Railtie into
-your application when it starts.
-
-### With other Rack-based frameworks
-
-Other Rack-based frameworks, such as Sinatra, can use the Rack Middleware
-provided by the library:
-
-```ruby
-require "google/cloud/error_reporting"
-use Google::Cloud::ErrorReporting::Middleware
-```
-
-## Reporting errors manually
-
-Manually reporting an error is as easy as calling the report method:
-
-```ruby
-require "google/cloud/error_reporting"
-begin
-  fail "boom!"
-rescue => exception
-  Google::Cloud::ErrorReporting.report exception
-end
-```
-
-## Configuring the library
-
-You can customize the behavior of the Stackdriver Error Reporting library for
-Ruby. See the [configuration
-guide](http://googlecloudplatform.github.io/google-cloud-ruby/docs/stackdriver/latest/file.INSTRUMENTATION_CONFIGURATION)
-for a list of possible configuration options.
-
-## Running on Google Cloud Platform
-
-The Stackdriver Error Reporting library for Ruby should work without you
-manually providing authentication credentials for instances running on Google
-Cloud Platform, as long as the Stackdriver Error Reporting API access scope is
-enabled on that instance.
-
-### App Engine
-
-On Google App Engine, the Stackdriver Error Reporting API access scope is
-enabled by default, and the Stackdriver Error Reporting library for Ruby can be
-used without providing credentials or a project ID.
-
-### Container Engine
-
-On Google Container Engine, you must explicitly add the `cloud-platform` OAuth
-scope when creating the cluster:
-
-```sh
-$ gcloud container clusters create example-cluster-name --scopes https://www.googleapis.com/auth/cloud-platform
-```
-
-You may also do this through the Google Cloud Platform Console. Select
-**Enabled** in the **Cloud Platform** section of **Create a container cluster**.
-
-### Compute Engine
-
-For Google Compute Engine instances, you must explicitly enable the
-`cloud-platform` access scope for each instance. When you create a new instance
-through the Google Cloud Platform Console, you can do this under Identity and
-API access: Use the Compute Engine default service account and select "Allow
-full access to all Cloud APIs" under Access scopes.
-
-## Running locally and elsewhere
-
-To run the Stackdriver Error Reporting outside of Google Cloud Platform, you
-must supply your GCP project ID and appropriate service account credentials
-directly to the Stackdriver Error Reporting. This applies to running the library
-on your own workstation, on your datacenter's computers, or on the VM instances
-of another cloud provider. See the [Authentication section](#authentication) for
-instructions on how to do so.
-
-## Authentication
-
-The Instrumentation client and API use Service Account credentials to connect to
-Google Cloud services. When running on Google Cloud Platform environments, the
-credentials will be discovered automatically. When running on other environments
-the Service Account credentials can be specified by providing in several ways.
-
-The best way to provide authentication information if you're using Ruby on Rails
-is through the Rails configuration interface:
-
-```ruby
-# in config/environments/*.rb
-Rails.application.configure do |config|
-  # Shared parameters
-  config.google_cloud.project_id = "your-project-id"
-  config.google_cloud.keyfile = "/path/to/key.json"
-  # Or Stackdriver Error Reporting specific parameters
-  config.google_cloud.error_reporting.project_id = "your-project-id"
-  config.google_cloud.error_reporting.keyfile = "/path/to/key.json"
-end
-```
-
-Other Rack-based applications that are loading the Rack Middleware directly or
-using the manually reporting interface can leverage the configration interface:
-
-```ruby
-require "google/cloud/error_reporting"
-Google::Cloud.configure do |config|
-  # Shared parameters
-  config.project_id = "your-project-id"
-  config.keyfile = "/path/to/key.json"
-  # Or Stackdriver Error Reporting specific parameters
-  config.error_reporting.project_id = "your-project-id"
-  config.error_reporting.keyfile = "/path/to/key.json"
-end
-```
-
-This library also supports the other authentication methods provided by the
-`google-cloud-ruby` suite. Instructions and configuration options are covered in
-the [Authentication
-Guide](https://googlecloudplatform.github.io/google-cloud-ruby/docs/google-cloud-debugger/latest/file.AUTHENTCATION).
-
-## Enabling Logging
-
-To enable logging for this library, set the logger for the underlying
-[gRPC](https://github.com/grpc/grpc/tree/master/src/ruby) library. The logger
-that you set may be a Ruby stdlib
-[`Logger`](https://ruby-doc.org/stdlib-2.5.0/libdoc/logger/rdoc/Logger.html) as
-shown below, or a
-[`Google::Cloud::Logging::Logger`](https://googlecloudplatform.github.io/google-cloud-ruby/docs/google-cloud-logging/latest/Google/Cloud/Logging/Logger)
-that will write logs to [Stackdriver
-Logging](https://cloud.google.com/logging/). See
-[grpc/logconfig.rb](https://github.com/grpc/grpc/blob/master/src/ruby/lib/grpc/logconfig.rb)
-and the gRPC
-[spec_helper.rb](https://github.com/grpc/grpc/blob/master/src/ruby/spec/spec_helper.rb)
-for additional information.
-
-Configuring a Ruby stdlib logger:
-
-```ruby
-require "logger"
-
-module MyLogger
-  LOGGER = Logger.new $stderr, level: Logger::WARN
-  def logger
-    LOGGER
-  end
-end
-
-# Define a gRPC module-level logger method before grpc/logconfig.rb loads.
-module GRPC
-  extend MyLogger
-end
-```
-
-## Supported Ruby Versions
-
-This library is supported on Ruby 2.3+.
-
-Google provides official support for Ruby versions that are actively supported
-by Ruby Core—that is, Ruby versions that are either in normal maintenance or in
-security maintenance, and not end of life. Currently, this means Ruby 2.3 and
-later. Older versions of Ruby _may_ still work, but are unsupported and not
-recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details
-about the Ruby support schedule.
-
-## Versioning
-
-This library follows [Semantic Versioning](http://semver.org/).
-
-It is currently in major version zero (0.y.z), which means that anything may
-change at any time and the public API should not be considered stable.
-
-## Contributing
-
-Contributions to this library are always welcome and highly encouraged.
-
-See the [Contributing
-Guide](https://googlecloudplatform.github.io/google-cloud-ruby/docs/google-cloud-debugger/latest/file.CONTRIBUTING)
-for more information on how to get started.
-
-Please note that this project is released with a Contributor Code of Conduct. By
-participating in this project you agree to abide by its terms. See [Code of
-Conduct](https://googlecloudplatform.github.io/google-cloud-ruby/docs/google-cloud-debugger/latest/file.CODE_OF_CONDUCT)
-for more information.
-
-## License
-
-This library is licensed under Apache 2.0. Full license text is available in
-[LICENSE](https://googlecloudplatform.github.io/google-cloud-ruby/docs/google-cloud-debugger/latest/file.LICENSE).
-
-## Support
-
-Please [report bugs at the project on
-Github](https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues). Don't
-hesitate to [ask
-questions](http://stackoverflow.com/questions/tagged/google-cloud-platform+ruby)
-about the client or APIs on [StackOverflow](http://stackoverflow.com).