RArachbelaid·May 20, 2016
A quick update to say that few things got added since version 0.1 and you can find more details on the github release page. https://github.com/rach/pome/releases
In Pome: Postgres monitoring dashboardrach
pome
Go2016–2016
rach / pome
pome
A Postgres Metrics Dashboard
3Distinct people
6Mentions
0Explicit recommenders
1.1KGitHub stars
What to know before exploring
What it is
A Postgres Metrics Dashboard
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week6 dated mentions
Observed mentions: 2016-01-05 00:19:04 UTC to 2016-05-20 21:56:27 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 4 | 2016-01-04 00:00:00 UTC | 2016-01-11 00:00:00 UTC | 5 | 1 | 4 |
| Jan 11 | 2016-01-11 00:00:00 UTC | 2016-01-18 00:00:00 UTC | 0 | 0 | 0 |
| Jan 18 | 2016-01-18 00:00:00 UTC | 2016-01-25 00:00:00 UTC | 0 | 0 | 0 |
| Jan 25 | 2016-01-25 00:00:00 UTC | 2016-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 1 | 2016-02-01 00:00:00 UTC | 2016-02-08 00:00:00 UTC | 0 | 0 | 0 |
| Feb 8 | 2016-02-08 00:00:00 UTC | 2016-02-15 00:00:00 UTC | 0 | 0 | 0 |
| Feb 15 | 2016-02-15 00:00:00 UTC | 2016-02-22 00:00:00 UTC | 0 | 0 | 0 |
| Feb 22 | 2016-02-22 00:00:00 UTC | 2016-02-29 00:00:00 UTC | 0 | 0 | 0 |
| Feb 29 | 2016-02-29 00:00:00 UTC | 2016-03-07 00:00:00 UTC | 0 | 0 | 0 |
| Mar 7 | 2016-03-07 00:00:00 UTC | 2016-03-14 00:00:00 UTC | 0 | 0 | 0 |
| Mar 14 | 2016-03-14 00:00:00 UTC | 2016-03-21 00:00:00 UTC | 0 | 0 | 0 |
| Mar 21 | 2016-03-21 00:00:00 UTC | 2016-03-28 00:00:00 UTC | 0 | 0 | 0 |
| Mar 28 | 2016-03-28 00:00:00 UTC | 2016-04-04 00:00:00 UTC | 0 | 0 | 0 |
| Apr 4 | 2016-04-04 00:00:00 UTC | 2016-04-11 00:00:00 UTC | 0 | 0 | 0 |
| Apr 11 | 2016-04-11 00:00:00 UTC | 2016-04-18 00:00:00 UTC | 0 | 0 | 0 |
| Apr 18 | 2016-04-18 00:00:00 UTC | 2016-04-25 00:00:00 UTC | 0 | 0 | 0 |
| Apr 25 | 2016-04-25 00:00:00 UTC | 2016-05-02 00:00:00 UTC | 0 | 0 | 0 |
| May 2 | 2016-05-02 00:00:00 UTC | 2016-05-09 00:00:00 UTC | 0 | 0 | 0 |
| May 9 | 2016-05-09 00:00:00 UTC | 2016-05-16 00:00:00 UTC | 0 | 0 | 0 |
| May 16 | 2016-05-16 00:00:00 UTC | 2016-05-23 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
6 sourcesHere the author.
Glad and scare that this project reached the 1st page of HN.
This project is at a very early stage but I had to release it at some stage. I wrote some explanation in the Readme [1] and in a blog post [2].
TL;DR: Pome aim to be very simple to deploy, opinionated and battery included tool to have a look at the health of your PG db. It's maybe not the case of anybody here but in my career, I have seen many PG db for which no health status were track (or because people think that RDS is magic). I assumed that if a very simple tool existed then it gives less reason to not track their health status.
At this stage, I don't think that Pome offers enough to be very useful but I hope that you will like the direction taken and where it's going.
Pome isn't aiming to be a tool for humongous Postgres instances which are already in the
Read the rest
hands of a DBA who can have the time to setup more advanced monitoring tools. Pome won't be an alternative to a more configurable tool like collectd.
[1] https://github.com/rach/pome#why-building-pome
[2] http://rachbelaid.com/introducing-pome/
Here the author. If you dislike Go then that makes two of us :)
But more seriously, I wrote a bit about the why in https://github.com/rach/pome#why-building-pome
To keep with the simplicity that I was aiming, I wanted a binary. I considered Rust, Haskell or Go (Swift was not opensource yet at the time) but went with Go because the libs that I will need (cron like scheduler, embedding assets, etc).
I had never written something in Go before but if I've known go then maybe I would have pick an other language as I started this project with a learning motivation.
In Pome – Postgres Metrics Dashboard Written in GoHere the author. I understand your points, I wrote a bit about my personal motivation behind this project.
http://rachbelaid.com/introducing-pome/
I also wrote within the readme about why wrote the project (context+goals), https://github.com/rach/pome#why-building-pome
This project is not aimed to replace more advanced tool like collectd but to offer a basic all-in-one solution. I'm also not planning to support huge database for the scaling problem that you highlight.
Trying to offer something easy without RDD store constraint for people who right now doesn't monitor their db.
I hope this make the goals behind the project more clear.
In Pome – Postgres Metrics Dashboard Written in GoI made a PR:
https://github.com/rach/pome/pull/20
In Pome – Postgres Metrics Dashboard Written in GoPome – Postgres Metrics Dashboard Written in Go
77 points · Open discussion