Consolidate alerts with Feeder

Search for a command to run...

No comments yet. Be the first to comment.
doc-home is a way to manage and monitor your Docker containers from a graphical user interface. To get started, simply run the following docker compose version: "3.4" services: doc-home: container_name: doc-home image: niradler/doc-home ...
Your team has 14 versions of the same code review skill across 5 repos, with no way to sync them. when one improves, the others don't. drop a folder in .claude/skills/ and pray nothing drifts. source

AI agents are unreasonably good at writing SQL. They get specific error messages, fix their own mistakes in one retry, and can introspect query performance with EXPLAIN ANALYZE before you even ask. No

n8n has over 400 integrations. Zapier claims 7,000+. Every single one was hand-built, tested against a moving API, and will eventually break when that API ships a v2. The entire workflow automation in

Part of the "Your Next Startup" series, where I break down startup ideas I think are worth building. Auth0 sold for \(6.5B. Okta is worth \)15B+. CyberArk, Delinea, BeyondTrust, all printing money fro

For as long as software has existed, we've been building two doors into our systems. Door one: the UI, a carefully designed surface where humans point, click, and occasionally rage-quit. Door two: the

Feeder is a self-hosted alert feed, you can use it to consolidate alerts from multiple sources, in my case I'm using it to get alerts on the status of my open source projects and self-hosted apps, any issues with one of these products will trigger a POST request to Feeder /webhook.
Feeder is built on SSR (Server Side Rendering) technologies.
My personal orientation is to the backend side, so I prefer to avoid client frameworks like React/Vue and such.
Instead, I'm using my own framework, Statikly, which is basically an opinionated Fastify template.
Feeder uses SSE (Server Sent Event), for real-time alert updates.

Feeder has one main page, the alerts page, you can search alerts by content, and tags, powered by Htmx, the alerts interaction feels like SPA (Single Page Application).

Another cool feature is the themes support, I'm using DaisyUI which comes with a pre-build set of themes, you can play with it and choose the theme you like.

Alerts fields
- `title` - The title of the alert
- `description` - The description of the alert
- `level` - The level of the alert, can be empty/error/warning/info
- `action` - The form action for the alert (trigger by the response button, see image above)
- `actionMethod` - The form method for the alert, default to `POST`
- `timestamp` - The timestamp for the alert
- `tags` - The tags for the alert (experimental)
- `groupId` - The groupId for the alert (experimental)
You can click an alert to see more details. If an action is present on the alert, a response button will be shown to trigger the action, this opens the way to cool interactions like confirming reading and action to deal with alerts. For example, an alert for a server that is not responding and an action response to restart the server.
Tech stack:
Checkout the Github repository for more https://github.com/niradler/feeder
Demo with n8n integration
