mehdig10

6 ms·

1.
Show HN: Pull, Replay or Inspect any webhook event(github.com)
2 points by mehdig10 8mo ago|0 comments
2.
Show HN: Basehook – consume, inspect or replay any webhook event(github.com)
2 points by mehdig10 9mo ago|0 comments
3.
by mehdig10 9mo ago
Thanks ! Since we're storing events in an intermediate collection and you consume them at your own rate, there is actually no need for this. They will just pile up until you can consume them
4.
by mehdig10 9mo ago
Well yeah for a simple queue where messages live in memory and disappear once consumed there are plenty of technologies that work (rabbitmq, redis...). Here is the goal is not to just build a queue but rather have something persisted where
5.
Show HN: Basehook – Webhook management system built on Postgres(github.com)
1 points by mehdig10 9mo ago|4 comments
6.
Show HN: LLM-powered data extraction from messy spreadsheets(github.com)
1 points by mehdig10 9mo ago|0 comments
7.
Show HN: A Grafana you can share with anyone(github.com)
1 points by mehdig10 9mo ago|0 comments
8.
Show HN: I built a Grafana your support team can use(github.com)
1 points by mehdig10 9mo ago|0 comments
9.
Show HN: Dashfrog – Customer-scoped observability for B2B SaaS(github.com)
1 points by mehdig10 9mo ago|0 comments
10.
by mehdig10 1y ago
yeah promql is a nightmare... don't know if datadog's better at that
11.
by mehdig10 1y ago
yeah but in my experience it's either the information is very shallow (like status page) or too technical (like traces). i feel like non engineering parts of the org still want to have a view of what's slow, what's fast, how
12.
Ask HN: How do you expose telemetry data to non-tech?
10 points by mehdig10 1y ago|6 comments
13.
Show HN: George, a Slack-native assistant for teams that hate ticketing(towerapp.ai)
2 points by mehdig10 1y ago|0 comments