GrafanaLabs Mimir supports Prometheus remote read API
.
vmctl in
remote-read mode
can be used
for historical data migration from Mimir.
By default, Mimir uses the prometheus path prefix so specifying the source
should be as simple as --remote-read-src-addr=http://<mimir>:9009/prometheus.
But if prefix was overridden via prometheus_http_prefix, then source address should be updated
to --remote-read-src-addr=http://<mimir>:9009/{prometheus_http_prefix}.
When you run Mimir, it exposes a port to serve HTTP on 8080 by default.
Next example of the local installation was in multi-tenant mode (3 instances of Mimir) with nginx as load balancer.
Load balancer expose single port :9090. As you can see in the example we call :9009 instead of :8080 because of proxy.
The importing process example for the local installation of Mimir and single-node VictoriaMetrics(http://localhost:8428):
./vmctl remote-read
--remote-read-src-addr=http://<mimir>:9009/prometheus \
--remote-read-filter-time-start=2021-10-18T00:00:00Z \
--remote-read-step-interval=hour \
--remote-read-headers=X-Scope-OrgID:demo \
--remote-read-use-stream=true \
--vm-addr=http://<victoria-metrics>:8428 \
Mimir supports streamed remote read API
,
so it is recommended setting --remote-read-use-stream=true flag for better performance and resource usage.
You may observe more samples being written to VictoriaMetrics with --remote-read-use-stream=true, particularly when using a small --remote-read-step-interval, such as minute.
This is caused by the underlying chunk storage structure in Mimir, and enabling
deduplication
will eventually remove these duplicates for both querying and storage.
See how to configure –vm-addr .
And when the process finishes, you will see the following:
Split defined times into 8847 ranges to import. Continue? [Y/n]
VM worker 0:→ 12176 samples/s
VM worker 1:→ 11918 samples/s
VM worker 2:→ 11261 samples/s
VM worker 3:→ 12861 samples/s
VM worker 4:→ 11096 samples/s
VM worker 5:→ 11575 samples/s
Processing ranges: 8847 / 8847 [█████████████████████████████████████████████████████████████████████████████] 100.00%
2022/10/21 17:22:23 Import finished!
2022/10/21 17:22:23 VictoriaMetrics importer stats:
idle duration: 0s;
time spent while importing: 15.379614356s;
total samples: 81243;
samples/s: 5282.51;
total bytes: 6.1 MB;
bytes/s: 397.8 kB;
import requests: 6;
import requests retries: 0;
2022/10/21 17:22:23 Total time: 16.287405248s
Configuration #
If you run Mimir installation in multi-tenant mode, remote read protocol requires an Authentication header like X-Scope-OrgID. Y
ou can define it via the flag --remote-read-headers=X-Scope-OrgID:demo.
See remote-read mode for more details.
See also general vmctl migration tips .
Read data from the remote storage like S3, GCS, Azure etc. #
If you have data stored in remote storage like S3, GCS, Azure etc. you can use vmctl in mimir mode to read data from
the remote storage and import it into VictoriaMetrics. In this mode vmctl reads data from the remote storage or file system
and checks index file, define needed blocks to be processed. After it downloads blocks by defined filters and
use Prometheus converter to read and sent data to VictoriaMetrics.
The following example shows how to read data from the file system and import it into VictoriaMetrics:
./vmctl mimir --mimir-path="fs:///mimir/test_data/mimir-tsdb" \ ? ? orbstack
--mimir-tenant-id=anonymous \
--mimir-filter-time-start=2024-12-01T00:00:00 \
--mimir-filter-time-end=2024-12-18T23:59:59 \
--mimir-creds-file-path=creads \
--vm-concurrency=6 \
--mimir-concurrency=6 \
--vm-addr=http://localhost:8428/
This approach is useful when you have data stored on the local file system or you have a mounted volume, download the data from the remote storage etc.
The following example shows how to read data from the remote storage and import it into VictoriaMetrics:
./vmctl mimir --mimir-path="s3:///mimir-tsdb/anonymous" \
--mimir-filter-time-start=2024-12-01T00:00:00 \
--mimir-filter-time-end=2024-12-17T23:59:59 \
--mimir-creds-file-path=creads \
--mimir-custom-s3-endpoint='http://localhost:9000' \
--vm-concurrency=6 \
--mimir-concurrency=6 \
--vm-addr=http://localhost:8428/
In the example above we are used --mimir-custom-s3-endpoint flag to specify the custom S3 endpoint if it is needed.
When the process finishes, you will see the following:
2025/01/18 13:01:59 Fetching blocks from remote storage
Found 204 blocks to import. Continue? [Y/n] y
VM worker 0:? 1589405 samples/s
VM worker 1:? 1911834 samples/s
VM worker 2:? 1849187 samples/s
VM worker 3:? 1648820 samples/s
VM worker 4:? 1539212 samples/s
VM worker 5:? 1411485 samples/s
Processing blocks: 204 / 204 [?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????] 100.00%
2025/01/18 13:02:18 Import finished!
2025/01/18 13:02:18 VictoriaMetrics importer stats:
idle duration: 18.485875611s;
time spent while importing: 16.40543875s;
total samples: 177961995;
samples/s: 10847743.71;
total bytes: 4.1 GB;
bytes/s: 248.2 MB;
import requests: 893;
import requests retries: 0;
2025/01/18 13:02:18 Total time: 18.867547083s