#patroni — Public Fediverse posts

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.

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.

Построение отказоустойчивого кластера 1С Предприятие 8.3. Требования назначения функциональности. MythBusters

Одна из завершающих публикаций цикла «В облако на работу:… Рецепты от Капитана» в ходе которых был собран полнофункциональный рабочий контур 1С в сети на отечественной Ред ОС. С веб-серверами, доменной авторизацией, архивированием и прочая прочая… На закуску разбираемся с отказоустойчивостью. В этой публикации для серверов 1С, заодно попробуем подобно сериалу «Разрушители легенд» подтвердить или опровергнуть пару устойчивых мифов о требованиях назначения функциональности.

https://habr.com/ru/companies/serverspace/articles/851598/

#1С_Предприятие #vipmanager #patroni #etcd #HAProxy #Alt_Linux #Astra_Linux #Ред_ОС #Kylin #рабочее_место_пользователя_1С #active_directory #авторизация_ОС