Skip to content
This repository was archived by the owner on Sep 16, 2023. It is now read-only.

Commit 15093b4

Browse files
chore: fix brand name (#837)
* chore: fix brand name Remove "Cloud" from "Cloud Error Reporting". Leave "Google Cloud Error Reporting" as is. * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
1 parent 39f1187 commit 15093b4

File tree

3 files changed

+14
-14
lines changed

3 files changed

+14
-14
lines changed

.repo-metadata.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"api_shortname": "clouderrorreporting",
3-
"name_pretty": "Cloud Error Reporting",
3+
"name_pretty": "Error Reporting",
44
"product_documentation": "https://cloud.google.com/error-reporting",
55
"client_documentation": "https://cloud.google.com/java/docs/reference/google-cloud-errorreporting/latest/history",
66
"issue_tracker": "https://issuetracker.google.com/savedsearches/559780",

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# Google Cloud Error Reporting Client for Java
1+
# Google Error Reporting Client for Java
22

3-
Java idiomatic client for [Cloud Error Reporting][product-docs].
3+
Java idiomatic client for [Error Reporting][product-docs].
44

55
[![Maven][maven-version-image]][maven-version-link]
66
![Stability][stability-image]
@@ -93,13 +93,13 @@ See the [Authentication][authentication] section in the base directory's README.
9393

9494
## Authorization
9595

96-
The client application making API calls must be granted [authorization scopes][auth-scopes] required for the desired Cloud Error Reporting APIs, and the authenticated principal must have the [IAM role(s)][predefined-iam-roles] required to access GCP resources using the Cloud Error Reporting API calls.
96+
The client application making API calls must be granted [authorization scopes][auth-scopes] required for the desired Error Reporting APIs, and the authenticated principal must have the [IAM role(s)][predefined-iam-roles] required to access GCP resources using the Error Reporting API calls.
9797

9898
## Getting Started
9999

100100
### Prerequisites
101101

102-
You will need a [Google Cloud Platform Console][developer-console] project with the Cloud Error Reporting [API enabled][enable-api].
102+
You will need a [Google Cloud Platform Console][developer-console] project with the Error Reporting [API enabled][enable-api].
103103

104104
[Follow these instructions][create-project] to get your project set up. You will also need to set up the local development environment by
105105
[installing the Google Cloud SDK][cloud-sdk] and running the following commands in command line:
@@ -110,13 +110,13 @@ You will need a [Google Cloud Platform Console][developer-console] project with
110110
You'll need to obtain the `google-cloud-errorreporting` library. See the [Quickstart](#quickstart) section
111111
to add `google-cloud-errorreporting` as a dependency in your code.
112112

113-
## About Cloud Error Reporting
113+
## About Error Reporting
114114

115115

116-
[Cloud Error Reporting][product-docs] counts, analyzes, and aggregates the crashes 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.
116+
[Error Reporting][product-docs] counts, analyzes, and aggregates the crashes 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.
117117

118-
See the [Cloud Error Reporting client library docs][javadocs] to learn how to
119-
use this Cloud Error Reporting Client Library.
118+
See the [Error Reporting client library docs][javadocs] to learn how to
119+
use this Error Reporting Client Library.
120120

121121

122122

@@ -138,7 +138,7 @@ To get help, follow the instructions in the [shared Troubleshooting document][tr
138138

139139
## Transport
140140

141-
Cloud Error Reporting uses gRPC for the transport layer.
141+
Error Reporting uses gRPC for the transport layer.
142142

143143
## Supported Java Versions
144144

samples/snippets/src/main/java/com/example/errorreporting/QuickStart.java

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,12 +28,12 @@
2828
import com.google.devtools.clouderrorreporting.v1beta1.SourceLocation;
2929

3030
/**
31-
* Snippet demonstrates using the Cloud Error Reporting API to report a custom error event.
31+
* Snippet demonstrates using the Error Reporting API to report a custom error event.
3232
*
3333
* <p>This library is not required on App Engine, errors written to stderr are automatically written
34-
* to Cloud Error Reporting. It is also not required if you are writing logs to Cloud Logging.
35-
* Errors written to Cloud Logging that contain an exception or stack trace are automatically
36-
* written out to Cloud Error Reporting.
34+
* to Error Reporting. It is also not required if you are writing logs to Cloud Logging. Errors
35+
* written to Cloud Logging that contain an exception or stack trace are automatically written out
36+
* to Error Reporting.
3737
*/
3838
public class QuickStart {
3939
public static void main(String[] args) throws Exception {

0 commit comments

Comments
 (0)