[prometheus-to-sd] Error while sending request to Stackdriver googleapi: Error 400: One or more TimeSeries could not be written: Unrecognized region or location.: timeSeries[0-199], badRequest

When I add the flag `--monitored-resource-type-prefix=k8s_` to `prometheus-to-sd`, I get the following error in the logs and no longer can see metrics in Stackdriver:

```
Error while sending request to Stackdriver googleapi: Error 400: One or more TimeSeries could not be written: Unrecognized region or location.: timeSeries[0-199], badRequest
```

prometheus-to-sd config:
```
name = "prometheus-to-sd"
image = "gcr.io/google-containers/prometheus-to-sd:v0.9.2"
port {
name = "profiler"
container_port = 6060
}
command = [
"/monitor",
"--stackdriver-prefix=custom.googleapis.com",
"--source=kube-state-metrics:http://localhost:8080",
"--monitored-resource-type-prefix=k8s_",
"--pod-id=$(POD_NAME)",
"--namespace-id=$(POD_NAMESPACE)"
]
```

kube-state-metrics config:
```
name = "kube-state-metrics"
image = "k8s.gcr.io/kube-state-metrics/kube-state-metrics:v2.0.0"
image_pull_policy = "Always"
args = []
command = []

port {
name = "http-metrics"
container_port = 8080
host_port = 0
}
```

It works if I drop the image down to `v0.9.0` or remove the `monitored-resource-type-prefix` flag.

Beginne damit, den Fehler mit prometheus-to-sd v0.9.2, kube-state-metrics v2.0.0 und --monitored-resource-type-prefix=k8s_ zu reproduzieren, und vergleiche anschließend mit v0.9.0 oder ohne dieses Flag. Verfolge, wie sich das Flag auf die Regionen der Stackdriver-Zeitreihenressourcen auswirkt, und überprüfe den Fix, indem du bestätigst, dass Metriken ohne den Regionsfehler akzeptiert werden.

Vom Indexierungsmodell aus dem Issue-Text verfasst.