Promscale has been discontinued. We strongly recommend that you do not use Promscale in a production environment. Learn more.
Promscale can be used as a remote storage for Prometheus and has native support for the Prometheus remote write and read protocols as well as full PromQL support.
You can configure Prometheus to use Promscale as a remote storage. Open the Prometheus configuration file and add or edit these lines:
remote_write:- url: "http://<connector-address>:9201/write"remote_read:- url: "http://<connector-address>:9201/read"read_recent: true
We highly recommend that you set Prometheus
to query data from Promscale for all PromQL
queries. To do this, set the
read_recent parameter to
This section contains information about configuring the Prometheus remote-write settings to maximize performance from Promscale.
Remote-write performance is dependent on
queue_config. Changing values in
queue_config allows you to change the
remote-write component for different scenarios.
For most cases, these settings work well:
remote_write:remote_timeout: 100squeue_config:max_samples_per_send: 10000
This section contains further explanation of each parameter.
For more information about Prometheus remote-write configuration, see the Prometheus documentation.
Set with the
remote_timeout field in
This parameter corresponds to the timeout value
POST requests, which
carry the samples batch to the remote storage. If
Promscale is far from where
Prometheus is deployed, or you have a high
cardinality of data being ingested,
you can set this to
remote_timeout: 100s. However, higher
remote_timeout can be considered,
based on the requirements.
Set with the
This parameter is the maximum number of samples
that can fit in a single write
request to the remote storage system. Samples
batch less than
max_samples_per_send are sent only
Promscale performs better with larger batches, so
set the default to