The remote_write configuration does not take effect

Percona Monitoring and Management (PMM)
,
1

I want to configure remote_write in pmm to collect pmm data to influxdb. I followed this document for relevant configuration.but unfortunately no data was collected.
please let me know how to make the remote_write configuration effective.
thanks.
The following is my trial process：

[root@c5c0248d14a4 prometheus]# pwd
/srv/prometheus
[root@c5c0248d14a4 prometheus]# 
[root@c5c0248d14a4 prometheus]# cat prometheus.base.yml 
---
remote_write:
  - url: http://10.10.236.101:32224/api/v1/prom/write?db=pmm
[root@c5c0248d14a4 prometheus]# 
[root@c5c0248d14a4 prometheus]# curl -X POST http://admin:admin@172.16.99.144/v1/Settings/Change
{
  "settings": {
    "telemetry_enabled": true,
    "metrics_resolutions": {
      "hr": "5s",
      "mr": "10s",
      "lr": "60s"
    },
    "data_retention": "2592000s",
    "aws_partitions": [
      "aws"
    ],
    "stt_check_intervals": {
      "standard_interval": "86400s",
      "rare_interval": "280800s",
      "frequent_interval": "14400s"
    }
  }
}[root@c5c0248d14a4 prometheus]#cat  /etc/victoriametrics-promscrape.yml 
# Managed by pmm-managed. DO NOT EDIT.
---
global:
    scrape_interval: 1m
    scrape_timeout: 54s
.......
.......
remote_write:
    - url: http://10.10.236.101:32224/api/v1/prom/write?db=pmm
[root@c5c0248d14a4 prometheus]#

Access to the database found that no data has been collected (ps:can ensure that the url is legal):

[root@c5c0248d14a4 prometheus]# curl -G 'http://10.10.236.101:32224/query?pretty=true' --data-urlencode "db=pmm" --data-urlencode "q=show measurements limit 10"
{
    "results": [
        {
            "statement_id": 0
        }
    ]
}
[root@c5c0248d14a4 prometheus]#
2

Hi @1115

What PMM2 version do you use?
Starting with PMM 2.12, VictoriaMetrics is used instead of Prometheus as a metrics store.

1 Like
3

Thanks for your reply, I use the latest version 2.23.0：image
When I switched to version 2.10.1, all the problems were solved:

[root@1ec6ab1c2a8d prometheus]# 
[root@1ec6ab1c2a8d prometheus]# curl -G 'http://10.10.236.101:32224/query?pretty=true' --data-urlencode "db=pmm" --data-urlencode "q=show measurements limit 10"
{
    "results": [
        {
            "statement_id": 0,
            "series": [
                {
                    "name": "measurements",
                    "columns": [
                        "name"
                    ],
                    "values": [
                        [
                            "alertmanager_alerts"
                        ],
                        [
                            "alertmanager_alerts_invalid_total"
                        ],
                        [
                            "alertmanager_alerts_received_total"
                        ],
                        [
                            "alertmanager_build_info"
                        ],
                        [
                            "alertmanager_cluster_enabled"
                        ],
                        [
                            "alertmanager_config_hash"
                        ],
                        [
                            "alertmanager_config_last_reload_success_timestamp_seconds"
                        ],
                        [
                            "alertmanager_config_last_reload_successful"
                        ],
                        [
                            "alertmanager_dispatcher_aggregation_groups"
                        ],
                        [
                            "alertmanager_dispatcher_alert_processing_duration_seconds_count"
                        ]
                    ]
                }
            ]
        }
    ]
}
[root@1ec6ab1c2a8d prometheus]#

The docker image I used is perconalab/pmm-client:2.10.1 and percona/pmm-server:2.10.1
thanks.

1 Like