<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>self-hosted on </title>
    <link>https://hawkvelt.id.au/tags/self-hosted/</link>
    <description>Recent content in self-hosted on </description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 06 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hawkvelt.id.au/tags/self-hosted/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Alerting with Alerta and ntfy</title>
      <link>https://hawkvelt.id.au/post/2026-04-06-alerta-ntfy-self-hosted-alerting/</link>
      <pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://hawkvelt.id.au/post/2026-04-06-alerta-ntfy-self-hosted-alerting/</guid>
      <description>
        
          
            Overview When you run infrastructure long enough, you end up with alerts coming from multiple sources: Prometheus, Grafana, custom scripts, hardware sensors, and more. Managing these across different channels (email, Slack, PagerDuty) becomes unwieldy and often expensive for self-hosted setups.
This post walks through building a self-hosted alerting solution using two powerful tools:
 Alerta — an alert aggregation and deduplication server ntfy — a simple push notification service with support for actions  The goal: consolidate all your alerts into one place, then route them to any device via ntfy&#39;s flexible notification system with clickable action buttons.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
