PgWatch v3. Collecting metrics from replicas

[UtkinMichael]

Hi, guys!
Please help me.
PgWatch v3.
I have near 200 servers PostgreSQL, all is inserted in pgwatch DB.
~30% is masters and everything is fine with them. Metrics are collected and displayed in Grafana.
And ~70% is replicas, but metrics are not collected from them, althouth they are in the DB pgwatch.

In this form they are entered into the DB:

pgwatch=# select * from pgwatch.source where name = 'fagote-07';
-[ RECORD 1 ]---------+------------------------------------------------------------
name | fagote-07
connstr | postgresql://myuser:mypasswd@fagote-07:5432/postgres
is_superuser | f
preset_config | superuser_no_python
config |
is_enabled | t
last_modified_on | 2025-04-14 07:14:48.913097+03
dbtype | postgres-continuous-discovery
include_pattern |
exclude_pattern | (postgres|template1|template0|repmgr|mamonsu|dbmon|dbadmin)
custom_tags |
group | default
host_config |
only_if_master | f
preset_config_standby |
config_standby |

The metrics collector is successfully connecting to these servers (and replicas and masters).
What do I need to do to collect metrics from them (from replicas)?

[pashagolub]

Would you please set preset_config_standby as a workaround

[UtkinMichael]

May be I don`t correctly understood, but if I set command
"update pgwatch.source set preset_config_standby='workaround' where name = 'fagote-07';"
I have error:
"ERROR: insert or update on table "source" violates foreign key constraint "source_preset_config_standby_fkey"
DETAIL: Key (preset_config_standby)=(workaround) is not present in table "preset"."

[pashagolub]

I didn't say set value to workaround but use any value as a workaround

update pgwatch.source set preset_config_standby='superuser_no_python' where name = 'fagote-07';

[UtkinMichael]

O, thanks, Pasha!
Sorry, but It's not obvious to me)