#patroni — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #patroni, aggregated by home.social.
-
pgwatch v6 ships a Patroni overview dashboard. It could not have existed before - and working out why explains the whole feature.
The dashboard asks for twenty-two readings: patroni_primary, patroni_xlog_location, patroni_dcs_last_seen and nineteen more. None of them come from a SQL query. #PostgresQL does not know any of this. #Patroni does, on its own metrics endpoint - and until v6, #pgwatch had no way to read it.
-
pgwatch v6 ships a Patroni overview dashboard. It could not have existed before - and working out why explains the whole feature.
The dashboard asks for twenty-two readings: patroni_primary, patroni_xlog_location, patroni_dcs_last_seen and nineteen more. None of them come from a SQL query. #PostgresQL does not know any of this. #Patroni does, on its own metrics endpoint - and until v6, #pgwatch had no way to read it.
-
pgwatch v6 ships a Patroni overview dashboard. It could not have existed before - and working out why explains the whole feature.
The dashboard asks for twenty-two readings: patroni_primary, patroni_xlog_location, patroni_dcs_last_seen and nineteen more. None of them come from a SQL query. #PostgresQL does not know any of this. #Patroni does, on its own metrics endpoint - and until v6, #pgwatch had no way to read it.
-
pgwatch v6 ships a Patroni overview dashboard. It could not have existed before - and working out why explains the whole feature.
The dashboard asks for twenty-two readings: patroni_primary, patroni_xlog_location, patroni_dcs_last_seen and nineteen more. None of them come from a SQL query. #PostgresQL does not know any of this. #Patroni does, on its own metrics endpoint - and until v6, #pgwatch had no way to read it.