Postgres Exporter - custom_queries_config_path not working

[alebeta90]

Hi,

I'm configuring grafana agent to export postgresql metrics. the basic configuration works.
Now I need to set a separate file with queries to collect some stats from the SQL queries, and it is not working, am receiving error:

May 07 09:11:24 db01 grafana-agent[2585743]: 2025/05/07 09:11:24 error loading config file /etc/grafana-agent.yaml: failed to unmarshal integration "postgres_exporter": yaml: unmarshal errors:
May 07 09:11:24 db01 grafana-agent[2585743]: line 17: field custom_queries_config_path not found

By checking the code, I can see the configuration does not have the custom_queries_config_path option available https://github.com/grafana/agent/blob/main/static/integrations/postgres_exporter/postgres_exporter.go#L20

But when reading documentation and a old issue in this repo there are some references to the usage of this option.

My current configuration looks as follow

postgres_exporter:
    enabled: {{ grafana_agent_postgres_enabled | lower }}
    instance: "{{ inventory_hostname }}"
    data_source_names:
      - "postgresql://{{ grafana_agent_postgres_user }}:{{ grafana_agent_postgres_password }}@{{ grafana_agent_postgres_host }}:{{ grafana_agent_postgres_port }}/postgres?sslmode=disable"
    autodiscover_databases: true
    # Use custom_queries_config_path for external queries file
    custom_queries_config_path: "/etc/grafana-agent-pg-queries.json"
    relabel_configs:
      - replacement: "{{ inventory_hostname }}"
        target_label: instance

it has some jinja vars because of ansible deployment.

Thanks in advance for any hint.

[github-actions]

This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!