-
Notifications
You must be signed in to change notification settings - Fork 99
feat(container): make dashboard portable and ready to use #483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Conversation
|
@andrewlecuyer |
|
I've tried this and it didn't work in our installer; also as has been pointed out both internally and externally, our container dashboards are a little out of date. I have some thoughts about how to advance at this moment, but need to check with the team and other maintainers. |
it's because all dashboards from postgres-operator-examples are out of date and not usable , that i came here .. and propose this fix .. maybe be use an https NB: on my side, all dashboard work as expected .. |
|
hey @DrummyFloyd, just wanted to let you know that we have a ticket in the backlog to update and I'm glad this isn't blocking you. Out of curiosity, are you using the postgres_exporter to get metrics from your clusters? |
|
@DrummyFloyd What version of Grafana are you using? |
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: monitoring.coreos.com/v1
kind: PodMonitor
metadata:
annotations:
argocd.argoproj.io/tracking-id: databases-home:monitoring.coreos.com/PodMonitor:databases/crunchy-postgres-exporter
creationTimestamp: "2025-08-24T21:16:35Z"
generation: 1
name: crunchy-postgres-exporter
namespace: databases
spec:
jobLabel: crunchy-postgres-exporter
podMetricsEndpoints:
- interval: 15s
port: exporter
relabelings:
- action: keep
regex: "9187"
sourceLabels:
- __meta_kubernetes_pod_container_port_number
- action: replace
sourceLabels:
- __meta_kubernetes_namespace
targetLabel: kubernetes_namespace
- action: replace
sourceLabels:
- __meta_kubernetes_pod_name
targetLabel: pod
- action: replace
replacement: $1$2
separator: ':'
sourceLabels:
- __meta_kubernetes_namespace
- __meta_kubernetes_pod_label_postgres_operator_crunchydata_com_cluster
targetLabel: pg_cluster
- action: replace
sourceLabels:
- __meta_kubernetes_pod_ip
targetLabel: ip
- action: replace
sourceLabels:
- __meta_kubernetes_pod_label_postgres_operator_crunchydata_com_instance
targetLabel: deployment
- action: replace
sourceLabels:
- __meta_kubernetes_pod_label_postgres_operator_crunchydata_com_role
targetLabel: role
- action: replace
sourceLabels:
- __meta_kubernetes_pod_label_postgres_operator_crunchydata_com_cluster
targetLabel: cluster_name
scrapeTimeout: 10s
selector:
matchLabels:
postgres-operator.crunchydata.com/crunchy-postgres-exporter: "true" |
grafana-operator v5.19.4 |
keithf4
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting on changes from CPK team to update dashboards for more recent versions of Grafana
|
any news ? |
|
@DrummyFloyd we recently updated our Dashboards in the Postgres Operator examples repo: https://github.com/CrunchyData/postgres-operator-examples/tree/main/kustomize/monitoring When you have a chance, can you verify that these changes work for you? |
this is still not okay for IaC configuration (or with manual import with grafana UI)
with same apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaDashboard
metadata:
annotations:
argocd.argoproj.io/tracking-id: databases-home:grafana.integreatly.org/GrafanaDashboard:databases/pgbackrest
name: pgbackrest
namespace: databases
spec:
allowCrossNamespaceImport: true
configMapRef:
key: pgbackrest.json
name: grafana-dashboards
datasources:
- datasourceName: prometheus
inputName: DS_PROMETHEUS
folder: Databases
instanceSelector:
matchLabels:
grafana: home
resyncPeriod: 10m
because uid |


Description
Please describe the changes made by your PR. This description should be at a high-level but detailed enough that a reviewer understands the scope of the fix or enhancement and can easily judge the PRs validity at addressing the stated issue/feature. Please fully describe any new or changed feature and whether said change is user-facing or not:
Benefits
Please indicate what kind of change your PR includes (multiple selections are acceptable):
PRs should be against existing issues, so please list each issue using a separate 'closes' line:
closes #482
If you have an external dependency (packages, portal updates, etc), add the 'BLOCKED' tag to your PR.
Testing
None of the testing listed below is optional.
Tested with IAC configurations and manually over my grafana instance (import + datasource selected after import)
IAC method
Code testing
Have you tested your changes against:
If your code touches sql_exporter, have you:
If your code touches node_exporter, have you:
If your code touches Prometheus, have you:
promtool check configpromtool check rulesIf your code touches Grafana, have you:
Checklist: