We're excited to launch <a target="_blank" href="https://github.com/PeerDB-io/pgslot-notify-bot">pgslot-notify-bot</a>, our latest open-source tool designed to surface the well-known issue of replication slot growth in PostgreSQL, as highlighted in <a target="_blank" href="https://blog.peerdb.io/five-tips-on-postgres-logical-decoding">this earlier article</a>. This tool is useful for database administrators to preemptively tackle problems associated with replication slot size increases, ensuring smooth database operations.
<h2 id="heading-features">Features</h2>
<ul>
<li>Monitoring: Checks the size of PostgreSQL replication slots at specified intervals.
</li>
<li>Slack Alerts: Instant notifications to a designated Slack channel for quick action. Tags <code>@channel</code> for slots that exceed the threshold otherwise just posts a message.
</li>
<li>Easy Setup: Simple configuration with an <code>.env</code> file, allowing quick deployment. There is also a <code>docker-compose.yaml</code> for those who prefer that.
</li>
<li>Adjustable Thresholds: Users can set size limits to suit their database needs.
</li>
</ul>
<img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1702563581515/3f280b6e-d5d9-46d5-8e06-0c23040f962e.png" alt="screenshot" class="image--center mx-auto" />
<h2 id="heading-future">Future</h2>
We see this bot to evolve to monitor other common issues that arise when replicating data in PostgreSQL, be it number of open connections or contentions by looking at <code>wait_event</code> and<code>wait_event_types</code>.
<h2 id="heading-get-involved">Get Involved</h2>
Try out the <a target="_blank" href="https://github.com/PeerDB-io/pgslot-notify-bot">pgslot-notify-bot</a>, and file issues or contribute if you'd want to see more features. Leave a star ⭐ if you like it!

We're excited to launch [pgslot-notify-bot](https://github.com/PeerDB-io/pgslot-notify-bot), our latest open-source tool designed to surface the well-known issue of replication slot growth in PostgreSQL, as highlighted in [this earlier article](https://blog.peerdb.io/five-tips-on-postgres-logical-decoding). This tool is useful for database administrators to preemptively tackle problems associated with replication slot size increases, ensuring smooth database operations.

## **Features**

* **Monitoring**: Checks the size of PostgreSQL replication slots at specified intervals.
    
* **Slack Alerts**: Instant notifications to a designated Slack channel for quick action. Tags `@channel` for slots that exceed the threshold otherwise just posts a message.
    
* **Easy Setup**: Simple configuration with an `.env` file, allowing quick deployment. There is also a `docker-compose.yaml` for those who prefer that.
    
* **Adjustable Thresholds**: Users can set size limits to suit their database needs.
    

![screenshot](https://cdn.hashnode.com/res/hashnode/image/upload/v1702563581515/3f280b6e-d5d9-46d5-8e06-0c23040f962e.png align="center")

## **Future**

We see this bot to evolve to monitor other common issues that arise when replicating data in PostgreSQL, be it number of open connections or contentions by looking at `wait_event` and`wait_event_types`.

## **Get Involved**

Try out the [pgslot-notify-bot](https://github.com/PeerDB-io/pgslot-notify-bot), and file issues or contribute if you'd want to see more features. Leave a star ⭐ if you like it!

PG Slot Notify: Monitor Postgres Slot Growth in Slack

At PeerDB, we are building a fast, simple and the most cost effective way to stream data from Postgres to Data Warehouses, Queues and Storage engines.
