Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPoG9-006PqJ-5e for pgsql-announce@arkaria.postgresql.org; Fri, 05 Jul 2024 19:06:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sPoG5-00DB6S-8G for pgsql-announce@arkaria.postgresql.org; Fri, 05 Jul 2024 19:06:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPoG4-00DB5M-Cl for pgsql-announce@lists.postgresql.org; Fri, 05 Jul 2024 19:06:13 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPoG0-000bFy-O0 for pgsql-announce@lists.postgresql.org; Fri, 05 Jul 2024 19:06:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=IKlSOU8mkC7pStGlmbPBLZtWp3psl648rEkqQG4/wUw=; b=y2grMuyCNaN1UAn2v+x2hd4p+j KeClqt1UrFWa0IPX4u5bJl9TRa6L1bh0UsiCc6zgrsJP+KeqjkBxq9cnJ9I1dPnnf1rMt1qrDIYQC qefsk547hi8kf87syvV3k66llmExMCYCKMoePFCL9GJ+VFNG9XY//5cFfPzGOai2yq1qADCdsYAtd qxYTxUKEjqd6RIfMsJKEEdSXoM2ftxVESfuGwKQDHSNTKfRu37rAAI4mzmW42iBblHGggvJ2Pg0MG qdCIiop+94L0JqDLvsqLudZNTVR05Ro9NuEquYPvdH0Q7gQsLVvCI95mn1LEVSCXVP/KAbFt2VdJn sWGGpSrg==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPoFx-001lcv-9n for pgsql-announce@lists.postgresql.org; Fri, 05 Jul 2024 19:06:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sPoFu-002arN-Ld for pgsql-announce@lists.postgresql.org; Fri, 05 Jul 2024 19:06:03 +0000 Content-Type: multipart/mixed; boundary="===============0619643181780715116==" MIME-Version: 1.0 Subject: check_pgbackrest 2.4 has been released To: PostgreSQL Announce From: Stefan Fercot via PostgreSQL Announce Reply-To: pgstef@fercot.be Date: Fri, 05 Jul 2024 19:05:58 +0000 Message-ID: <172020635894.714.6727191841030847525@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 61cbed8b08c72bad4205b1701f2b9eb5bf788542a649ef67effdfc72e10ad0b5 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============0619643181780715116== Content-Type: multipart/alternative; boundary="===============8539612031226763805==" MIME-Version: 1.0 --===============8539612031226763805== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable _Mons, Belgium, July 05, 2024_ `check_pgbackrest` is designed to monitor [pgBackRest](https://pgbackrest.o= rg) backups from Nagios, relying on the status information given by the [in= fo](https://pgbackrest.org/command.html#command-info) command. It allows to monitor the backups retention and the consistency of the archi= ved WAL segments. Changes in check_pgbackrest 2.4 ---------------------------------------------------------------------------= ----- * Only support pgBackRest **2.52** and above to fix issue with new pgBack= Rest versioning policy since `2.52.1`. (Reported by netphantm) * Add new `pgbackrest_version` service, in order to check for a specific = pgBackRest target version. Links & Credits ---------------------------------------------------------------------------= ----- This is an open project, licensed under the PostgreSQL license.=20 Any contribution to improve it is welcome. Links: * Download: https://github.com/pgstef/check_pgbackrest/releases * Support: https://github.com/pgstef/check_pgbackrest/issues --===============8539612031226763805== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable check_pgbackrest 2.4 has been released
 

check_pgbackrest 2.4 has been released

Mons, Belgium, July 05, 2024

check_pgbackrest is designed t= o monitor pgBackRest backups from Nagios, relying on the s= tatus information given by the info<= /a> command.

It allows to monitor the backups retention = and the consistency of the archived WAL segments.

Changes in check_pgbackrest 2.4=

  • Only support pg= BackRest 2.52 and above to fix issue with new pgBackRest v= ersioning policy since 2.52.1. (Reported by netphantm)
  • Add new p= gbackrest_version service, in order to check for a specific pgBackRe= st target version.

Links & Credits

This is an open project, licensed under the= PostgreSQL license.=20 Any contribution to improve it is welcome.

Links:

  • Download: https= ://github.com/pgstef/check_pgbackrest/releases
  • Support: https:= //github.com/pgstef/check_pgbackrest/issues
This email was sent to you from Stefan Fercot. It was delivered on their be= half by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Stefan Fercot.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============8539612031226763805==-- --===============0619643181780715116==--