mudhorn/prometheus
1
0
Fork 0
mirror of https://github.com/prometheus/prometheus.git synced 2025-03-05 20:59:13 -08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

Tweak migration doc (#3430)

Browse source
This commit is contained in:
Brian Brazil 2017-11-08 08:38:28 +00:00
parent b3b6538348
commit 5dff97639f
1 changed files with 11 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
docs/migration.md
View file

@ -98,11 +98,11 @@ Would look like this:
groups: groups:
- name: example.rules - name: example.rules
rules: rules:
- record: job:request_duration_seconds:99percentile - record: job:request_duration_seconds:histogram_quantile99
expr: histogram_quantile(0.99, sum(rate(request_duration_seconds_bucket[1m])) expr: histogram_quantile(0.99, sum(rate(request_duration_seconds_bucket[1m]))
BY (le, job)) BY (le, job))
- alert: FrontendRequestLatency - alert: FrontendRequestLatency
expr: job:request_duration_seconds:99percentile{job="frontend"} > 0.1 expr: job:request_duration_seconds:histogram_quantile99{job="frontend"} > 0.1
for: 5m for: 5m
annotations: annotations:
summary: High frontend request latency summary: High frontend request latency
@ -115,30 +115,30 @@ new format. For example:
$ promtool update rules example.rules $ promtool update rules example.rules
``` ```
Note that you will need to use promtool from 2.0, not 1.8.
## Storage ## Storage
The data format in Prometheus 2.0 has completely changed and is not backwards The data format in Prometheus 2.0 has completely changed and is not backwards
compatible with 1.8. To retain access to your historic monitoring data we recommend compatible with 1.8. To retain access to your historic monitoring data we
you run a non-scraping Prometheus 1.8.1 instance in parallel with your Prometheus 2.0 recommend you run a non-scraping Prometheus instance running at least version
instance, and have the new server read existing data from the old one via the 1.8.1 in parallel with your Prometheus 2.0 instance, and have the new server
remote write protocol. read existing data from the old one via the remote write protocol.
Your Prometheus 1.8 instance should be started with the following flags and an Your Prometheus 1.8 instance should be started with the following flags and an
empty config file (`empty.yml`): config file containing only the `external_labels` setting (if any):
``` ```
$ ./prometheus-1.8.1.linux-amd64/prometheus -web.listen-address ":9094" -config.file empty.yml $ ./prometheus-1.8.1.linux-amd64/prometheus -web.listen-address ":9094" -config.file old.yml
``` ```
NOTE: **NOTE** If you used external labels in your Prometheus 2.0 config, they need to be
preserved in your Prometheus 1.8 config.
Prometheus 2.0 can then be started (on the same machine) with the following flags: Prometheus 2.0 can then be started (on the same machine) with the following flags:
``` ```
$ ./prometheus-2.0.0.linux-amd64/prometheus --config.file prometheus.yml $ ./prometheus-2.0.0.linux-amd64/prometheus --config.file prometheus.yml
``` ```
Where `prometheus.yml` contains the stanza: Where `prometheus.yml` contains in addition to your full existing configuration, the stanza:
``` ```
remote_read: remote_read: