chore: regenerate README

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

@@ -4,14 +4,14 @@
       "git": {
         "name": ".",
         "remote": "https://github.com/googleapis/java-bigtable.git",
-        "sha": "fa8f5ef216fcbcd9f57343475f03a7353b0e9ddd"
+        "sha": "8240779434a602dc8b2bf90dbe539c5d7470d850"
       }
     },
     {
       "git": {
         "name": "synthtool",
         "remote": "https://github.com/googleapis/synthtool.git",
-        "sha": "d73e8dea90af1b463a7f9d4a33244cf4612ada7c"
+        "sha": "41e998d5afdc2c2143a23c9b044b9931936f7318"
       }
     }
   ]

README.md

@@ -296,22 +296,12 @@ metrics will be tagged with:
   each client RPC, tagged by operation name and the attempt status. Under normal
   circumstances, this will be identical to op_latency. However, when the client
   receives transient errors, op_latency will be the sum of all attempt_latencies
-  and the exponential delays.
+  and the exponential delays
 
 * `cloud.google.com/java/bigtable/attempts_per_op`: A distribution of attempts that
   each operation required, tagged by operation name and final operation status.
   Under normal circumstances, this will be 1.
 
-### GFE metric views:
-
-* `cloud.google.com/java/bigtable/gfe_latency`: A distribution of the latency
-  between Google's network receives an RPC and reads back the first byte of
-  the response.
-
-* `cloud.google.com/java/bigtable/gfe_header_missing_count`: A counter of the
-  number of RPC responses received without the server-timing header, which
-  indicates that the request probably never reached Google's network.
-
 
 By default, the functionality is disabled. For example to enable metrics using
 [Google Stackdriver](https://cloud.google.com/monitoring/docs/):
@@ -367,8 +357,6 @@ StackdriverStatsExporter.createAndRegister(
 );
 
 BigtableDataSettings.enableOpenCensusStats();
-// Enable GFE metric views
-BigtableDataSettings.enableGfeOpenCensusStats();
 ```
 
 ## Version Conflicts