Ask HN: How do you handle internal event webhooks without spamming Slack?

I’ve been routing internal product events, backend signals, and 3rd-party notifications into Slack channels using webhooks, but it’s starting to feel wrong — hard to search/filter, and overloading channels.

How are you dealing with this?

Do you have a better system to collect and review these?

Any tools you like for this purpose?

I'm a solo dev working on a product and trying to figure out how others deal with this:

I have a bunch of non-critical internal events that I want visibility on:

Product updates: new signups, conversions, upgrades

Backend events: migrations finished, cron jobs completed, some errors (but not urgent ones)

Third-party integrations: like when my SEO tool posts a daily summary

Right now, I’m using Slack channels to receive webhook notifications from everywhere — it kinda works, but it’s starting to feel wrong:

Hard to filter or search

Feeds get noisy fast

I miss stuff because it blends with team chat

I know tools like Sentry, PagerDuty, or full observability stacks exist — but for a tiny team, they’re overkill. I just want a better way to organize and review these internal “status” events.

So I’m wondering: how do you handle this?

Do you send webhooks somewhere structured?

Are you using Airtable, Notion, email, or something else?

Have you built your own webhook dashboard or log viewer?

Curious how others in the same boat (indie hackers, small teams, solo devs) are solving this. Looking to learn how others manage this kind of internal “status” noise.