Hi,
I have been using Cloudprober - deployed in Dev, Test Environments. Have configured Cloudprober to export probing (http & other external probe) metrics to Prometheus.
If i configure Postgresql surfacer in cloudprober config, unable to see these metrics exported from cloudprober UI. Is this expected behaviour or something wrong?
Ex: my cloudprober config. --- Sample
apiVersion: v1
data:
cloudprober.cfg: |
probe {
name: "golang-profiler"
type: HTTP
targets {
host_names: "localhost" #"golang-profiler.default.svc.cluster.local"
}
http_probe {
protocol: HTTP
port: 9313
relative_url: "/"
}
interval_msec: 15000 # 15s
timeout_msec: 1000 # 1s
}
probe {
name: "nodejs-profiler"
type: HTTP
targets {
host_names: "localhost" #"nodejs-profiler.default.svc.cluster.local"
}
http_probe {
protocol: HTTP
port: 9313
relative_url: "/"
}
interval_msec: 15000 # 15s
timeout_msec: 1000 # 1s
}
surfacer {
type: POSTGRES
postgres_surfacer {
connection_string: "postgresql://postgres:pgusergen@123@<postgresql host>/cloudprober?sslmode=disable"
metrics_table_name: "metrics"
}
}
grpc_port : 9314
kind: ConfigMap
Note: postgresql host is a container - I'm using its Load Balancer Endpoint.