Can't add metric when adding PW_SOURCES as directory

[robinportigliatti]

Hello,

Describe the bug

I can't add any metric when I provide PW_SOURCES as a directory.

It may not be a bug, but it is not clear in the doc.

In my docker-compose.yaml file I have the following for my PW_SOURCES:

[...]
  pgwatch:
    image: cybertecpostgresql/pgwatch:latest
    container_name: pgwatch
    environment:
      PW_SOURCES: "/config/pgwatch/sources/"
#      PW_METRICS: "/config/pgwatch/metrics/"
    command:
    - "--sink=postgresql://pgwatch:pgwatch@pgwatch_db:5432/pgwatch_metrics?sslmode=disable"
    - "--sink=prometheus://pgwatch:9187/metrics"
    ports:
      - "8080:8080"   # interface Web UI
      - "9187:9187"   # Prometheus exporter
    volumes:
      - "./pgwatch/sources/:/config/pgwatch/sources/"
      - "./pgwatch/metrics/:/config/pgwatch/metrics/"
    depends_on:
      pgwatch_db:
        condition: service_healthy
[...]

And when I add any metric, I get an "unsupported operation" message.

I think we should add a litle note about it, that when we use file based configuration we are not allowed to add any custom metrics from the UI. It makes sense in my opinion but not to everyone who whishes to put their hand on pgwatch.

EDIT : Using a file works, using a folder does not.

Robin,

[pashagolub]

Hello Robin.

Yes, if you don't specify metrics then pgwatch uses built-in. Operations on built-in metrics are not supported.

This is no way connected to how you specify sources.

[robinportigliatti]

I am not sure but it seems that I did not make myself clear.

I was not doing anything on built-in metrics. I was trying to add a metric.