zalando / zalando/postgres-operator

Feature: Integration with pmm

Open
#2,784 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

  • Where do you run it - cloud or metal? Kubernetes or OpenShift? EKS
  • Are you running Postgres Operator in production? yes
  • Type of issue? feature request

It would be really nice if operator was able to integrate with pmm, it is a monitoring tool and mainly what it lacks is auto clusters discoverability

Possible solutions:

  • Fork pmm and possibly upstream patches
  • Build out what pmm into Grafana dashboards with help of extra optional daemon for monitoring clusters
  • Create some sort of script that would exec into pmm and add clusters (probably the easiest solution)
    • Should be possible via API, but they have a binary for that which feels like the easiest solution

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files, tests, or entry points are named. Start by evaluating PMM's API or binary and how it could discover EKS-managed PostgreSQL clusters; done means selecting and implementing one integration approach with reliable automatic cluster registration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, postgresql
Domain
databases, infrastructure, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.