Skip to content

Commit 4dd7638

Browse files
chore: regenerate README (#582)
This PR was generated using Autosynth. 🌈 <details><summary>Log from Synthtool</summary> ``` 2020-12-17 18:27:00,044 synthtool [DEBUG] > Executing /root/.cache/synthtool/java-bigtable/.github/readme/synth.py. On branch autosynth-readme nothing to commit, working tree clean 2020-12-17 18:27:00,999 synthtool [DEBUG] > Wrote metadata to .github/readme/synth.metadata/synth.metadata. ``` </details> Full log will be available here: https://source.cloud.google.com/results/invocations/a685e710-846a-4969-a779-fee6f22b33bf/targets - [ ] To automatically regenerate this PR, check this box.
1 parent 93353cf commit 4dd7638

File tree

2 files changed

+6
-8
lines changed

2 files changed

+6
-8
lines changed

.github/readme/synth.metadata/synth.metadata

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,14 @@
44
"git": {
55
"name": ".",
66
"remote": "https://github.com/googleapis/java-bigtable.git",
7-
"sha": "fa8f5ef216fcbcd9f57343475f03a7353b0e9ddd"
7+
"sha": "93353cfa3cb4bc30146f592bb1d6cdaac1fefebc"
88
}
99
},
1010
{
1111
"git": {
1212
"name": "synthtool",
1313
"remote": "https://github.com/googleapis/synthtool.git",
14-
"sha": "d73e8dea90af1b463a7f9d4a33244cf4612ada7c"
14+
"sha": "41e998d5afdc2c2143a23c9b044b9931936f7318"
1515
}
1616
}
1717
]

README.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -303,15 +303,13 @@ metrics will be tagged with:
303303
Under normal circumstances, this will be 1.
304304

305305
### GFE metric views:
306-
307306
* `cloud.google.com/java/bigtable/gfe_latency`: A distribution of the latency
308-
between Google's network receives an RPC and reads back the first byte of
309-
the response.
307+
between Google's network receives an RPC and reads back the first byte of
308+
the response.
310309

311310
* `cloud.google.com/java/bigtable/gfe_header_missing_count`: A counter of the
312-
number of RPC responses received without the server-timing header, which
313-
indicates that the request probably never reached Google's network.
314-
311+
number of RPC responses received without the server-timing header, which
312+
indicates that the request probably never reached Google's network.
315313

316314
By default, the functionality is disabled. For example to enable metrics using
317315
[Google Stackdriver](https://cloud.google.com/monitoring/docs/):

0 commit comments

Comments
 (0)