How to extend victoriametrics-promscrape.yaml

Percona Monitoring and Management (PMM) PMM 2.x
1

I remember when PMM use prometheus, I could customize some configuration by creating the file /srv/prometheus/prometheus.base.yml

FAQ - Percona Monitoring and Management

Now that we are using victoriametics, is it still possible to do this?
Because I want to add some monitoring, such as orchestrator. like

I merged this PR in my own branch

- job_name: 'orchestrator'
  metrics_path: /prometheus/metrics
  static_configs:
  - targets: ['orc1:3000', 'orc3:3000', 'orc3:3000']
1 Like
2

Hi @Fan,
Yes it should keep working the same way it was working with Prometheus.

Nurlan.

1 Like
3

Hi @nurlan.

image
image835×426 31.6 KB

Has this problem been fixed?

1 Like
4

Hi, @nurlan
Can you explain in detail how to use it?
The file was created in the following path, but it does not work.
/srv/victoriametrics/victoriametrics_promscape.base.yml
/srv/prometheus/prometheus.base.yml
/srv/victoriametrics/prometheus.base.yml

1 Like
5

so if this file prometheus.base.yml is not available should I create it? or is there a specific file that should be configured to add other targets to my PMM dashboard I tried looking for /etc/victoriametrics.yml but its says not to edit anything in it.

1 Like
6

Hi @Ali, @osysee ,
Yes, you should create a file /srv/prometheus/prometheus.base.yml and then restart PMM.
Then you can check generated file in /etc/victoriametrics.yml to make sure that base file is included.

1 Like
7

Hi @nurlan.
In this topic Victoriametrics cpu usage looks much higher than prometheus - #9 by Fan
image
Has this problem been fixed?

1 Like
8

Hi! We are still have problems with sending metrics to another prometheus from PMM (