This feature is in beta. Please contact the Support team or your account manager to request early access.

To send your Prometheus application metrics to a Infrastructure Monitoring account, use remote write to connect to as the endpoint. Your data is formatted as JSON documents by the listener.

Plan ahead

  • Multiple server environments: If you have multiple Prometheus server instances, you’ll have to add as an endpoint for each instance.

  • Reduce tagging: By default, all the metrics from your Prometheus server(s) are sent to To drop or send specific metrics, add Prometheus labeling before enabling the remote write, or as part of the remote write configuration. Learn more about Prometheus relabeling tricks here .

  • Paralleism levels: Set the parallelism level for sending data in the configuration file. This parameter determines the number of connections to open to the remote write listener. The default parallelism level is 1000. We recommend configuring much fewer connections. Of course, if you’re sending more data you’ll need to open more channels. (currently in development)

    We’re currently refining our best practice recommendations for configuring connection channels when sending data.

  • Metrics metadata dashboards: If you have both Prometheus & Grafana, you can activate a dashboard as part of the remote write configuration that will show you the queue size and how many metrics you’re sending. If your queue size increases, it might be necessary to open an additional channel. (currently in development)

Learn more about Prometheus remote write tuning here .

Once your metrics are flowing, export your existing Prometheus and Grafana dashboards to Infrastructure Monitoring as JSON files.

Configuring Remote Write to

Get your Infrastructure Monitoring account information

Within, look up the Listener host for your region (URL) and the Metrics Account token.

Add a remote_write url

Add the following parameters to your Prometheus yaml file:

Environment variable Description
external_labels Parameter to tag the metrics from this specific Prometheus server. Do not change the label p8s_logzio_name: This variable is required to identify from which Prometheus environment the metrics are arriving to
remote_write The remote write section configuration sets as the endpoint for your Prometheus metrics data. Place this section at the same indentation level as the global section.
url Listener url for for your region, configured to use port 8052 for http traffic or port 8053 for https traffic. For more details, see the Prometheus configuration file remote write reference
bearer_token Metrics account token
        p8s_logzio_name: <labelvalue>
      - url: https://<the Listener URL for your region>:8053
        bearer_token: <your Metrics account token> 
        remote_timeout: 30s
          batch_send_deadline: 5s  #default = 5s
          max_shards: 10  #default = 1000
          min_shards: 1
          max_samples_per_send: 500 #default = 100
          capacity: 10000  #default = 500

Verify the remote_write configuration

To check that the remote_write configuration is working properly, run a query on your local Prometheus for the metric prometheus_remote_storage_succeeded_sample_total and verify that the result is greater than zero (n > 0) for the url.