<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Targino Castelo Branco</title>
    <description>The latest articles on DEV Community by Targino Castelo Branco (@targinocastelobranco).</description>
    <link>https://dev.to/targinocastelobranco</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1737187%2Fa738906f-43ab-4b5c-bbff-5d20959ce436.jpg</url>
      <title>DEV Community: Targino Castelo Branco</title>
      <link>https://dev.to/targinocastelobranco</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/targinocastelobranco"/>
    <language>en</language>
    <item>
      <title>Argus DBA Availability</title>
      <dc:creator>Targino Castelo Branco</dc:creator>
      <pubDate>Wed, 29 Apr 2026 03:35:00 +0000</pubDate>
      <link>https://dev.to/targinocastelobranco/argus-dba-availability-1aji</link>
      <guid>https://dev.to/targinocastelobranco/argus-dba-availability-1aji</guid>
      <description>&lt;p&gt;Hey everyone! &lt;/p&gt;

&lt;p&gt;Over the past few weeks I've been working on Argus DBA, initially a PostgreSQL database monitoring system, but in the future new databases will be added, along with automation features for the day-to-day routines we perform with the support of AI — though you will still be the DBA; Argus DBA will simply be a quality-of-life tool.&lt;/p&gt;

&lt;p&gt;We know that our databases grow in size and number every day, making it increasingly difficult to manage so many instances at once. That's why a reliable, affordable, and intuitive tool is needed to help us — and that's the purpose behind my work on Argus DBA.&lt;/p&gt;

&lt;p&gt;If you have any suggestions or comments, please feel free to share them, as they will be a great source of improvement.&lt;/p&gt;

&lt;p&gt;Discover Argus DBA at: argusdba.com and/or app.argusdba.com&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F77v67fzmk1oozaubzlu0.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F77v67fzmk1oozaubzlu0.jpg" alt=" " width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>postgres</category>
      <category>monitoring</category>
      <category>postgressql</category>
      <category>dba</category>
    </item>
    <item>
      <title>Quanto tempo leva pra sua equipe descobrir que o PostgreSQL caiu?</title>
      <dc:creator>Targino Castelo Branco</dc:creator>
      <pubDate>Fri, 20 Mar 2026 11:56:20 +0000</pubDate>
      <link>https://dev.to/targinocastelobranco/quanto-tempo-leva-pra-sua-equipe-descobrir-que-o-postgresql-caiu-fk4</link>
      <guid>https://dev.to/targinocastelobranco/quanto-tempo-leva-pra-sua-equipe-descobrir-que-o-postgresql-caiu-fk4</guid>
      <description>&lt;p&gt;Sexta-feira, 18h. O banco de dados caiu.&lt;/p&gt;

&lt;p&gt;Ninguém percebeu até o suporte receber uma enxurrada de tickets. Foram 23 minutos de downtime. O custo? Difícil calcular, mas fácil sentir.&lt;/p&gt;

&lt;p&gt;Isso acontece mais do que deveria — e quase sempre pelo mesmo motivo: ninguém estava checando se o PostgreSQL ainda estava no ar.&lt;/p&gt;

&lt;p&gt;Monitorar disponibilidade não precisa ser complexo. Um check ativo a cada poucos segundos, um alerta instantâneo quando algo cai, e um histórico pra entender o que aconteceu.&lt;/p&gt;

&lt;p&gt;Escrevemos um post explicando o que monitorar e como automatizar isso:&lt;br&gt;
&lt;a href="https://argusdba.com/pt/blog/por-que-monitorar-disponibilidade-postgresql/" rel="noopener noreferrer"&gt;https://argusdba.com/pt/blog/por-que-monitorar-disponibilidade-postgresql/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>postgres</category>
      <category>postgressql</category>
      <category>dba</category>
      <category>sre</category>
    </item>
  </channel>
</rss>
