Update README with working m3db.vultrlabs.dev endpoint

README.md

@@ -77,7 +77,7 @@ kubectl -n m3db get svc m3coordinator-lb
 ```bash
 ./test-metrics.sh <BASE_URL>
 # Example:
-./test-metrics.sh https://m3db.vultrlabs.dev:7201
+./test-metrics.sh http://m3db.vultrlabs.dev:7201
 ```
 
 This script verifies:
@@ -91,7 +91,7 @@ This script verifies:
 pip install requests python-snappy
 python3 test-metrics.py <BASE_URL>
 # Example:
-python3 test-metrics.py https://m3db.vultrlabs.dev:7201
+python3 test-metrics.py http://m3db.vultrlabs.dev:7201
 ```
 
 Writes a test metric via Prometheus remote_write and reads it back.
@@ -120,7 +120,7 @@ remote_read:
 ```yaml
 # prometheus.yml
 remote_write:
-  - url: "http://<LB-IP>:7201/api/v1/prom/remote/write"
+  - url: "http://m3db.vultrlabs.dev:7201/api/v1/prom/remote/write"
     queue_config:
       capacity: 10000
       max_shards: 30
@@ -128,7 +128,7 @@ remote_write:
       batch_send_deadline: 5s
 
 remote_read:
-  - url: "http://<LB-IP>:7201/api/v1/prom/remote/read"
+  - url: "http://m3db.vultrlabs.dev:7201/api/v1/prom/remote/read"
     read_recent: true
 ```
 
@@ -142,7 +142,7 @@ kubectl -n m3db get svc m3coordinator-lb
 Add a **Prometheus** datasource in Grafana pointing to:
 
 - **In-cluster:** `http://m3coordinator.m3db.svc.cluster.local:7201`
-- **External:** `http://<LB-IP>:7201`
+- **External:** `http://m3db.vultrlabs.dev:7201`
 
 All existing PromQL dashboards will work without modification.