Healthchecks VS keep

Hey mate, I'm using https://healthchecks.io/ for heartbeat monitoring my crons. It's been working flawlessly for quite some time now. The UI is super clean and easy to navigate. It's also free up to 20 monitored jobs. Note - I'm not in any way related to that project.

In fact, your platform (https://healthchecks.io/) is a prime example of where running customer wasm would be really excellent.

Instead of sending webhooks out to customer configured URLs, you could run a Wasm environment to execute customer code. Off hand, a good use case here is to do further inspection of the event before it gets sent off to some other system - maybe there are cases where you send false-positives and needlessly trigger external system alerts. The customer Wasm could do more introspection on the healthcheck event and make a more informed decision about how to proceed.

i use healthchecks.io and have been very happy

Is there anything different from https://healthchecks.io/ --- a service I've been using for free for a couple years now?

Because of this block on the router, and the fact that IPv6 connections are by default preferred over IPv4, many things on the system now cannot access the internet. the only things that can access the internet are for accessing servers that ONLY support IPv4 like my mail.smpt2go or my uptime monitoring scripts for healthchecks.io.

i use https://healthchecks.io/ and highly recommend it.

We use a heartbeat system. Basically the monitoring continuously sends an alert to a healtcheck system. If that heartbeat fails, PagerDuty sends an alert to the oncall.

i like healthchecks.io

I enjoyed talking to Tal, CEO and co-founder at Keep. It started as a CLI tool and, over time, became an alert aggregation tool.

Keep

Missing any provider/feature? just open an issue at https://github.com/keephq/keep and we will add it ASAP (and of course contributions are welcome!)

st2 reminds me a lot of what we're building at https://github.com/keephq/keep (i maintain this oss), there are a few concepts that i really love but the video in the repo really gives me a 90s feelin'

i can't really seem to understand, there's an "enterprise" (with ldap, etc.) version but couldn't find any pricing info

Nope, fully open source - https://github.com/keephq/keep

hey there! we had the exact same problem so we built https://github.com/keephq/keep. it's cool to see that we have very similar syntax (you can see workflows examples here - https://github.com/keephq/keep/tree/main/examples/workflows)

Yo HN!

I've followed https://github.com/Yelp/elastalert which was archived and then forked by https://github.com/jertel/elastalert2 for quite a while, and I'm pretty ambiguous about it. On one hand, it looks like these projects got some good traction, but on the other hand, they feel pretty abandoned these days. I've also tried to reach out to the maintainers and am still waiting for an answer.

Anyway - if you use any of these projects, I'll be more than happy to talk (just drop a comment or send an email to [email protected])

The context is, I'm building Keep (https://github.com/keephq/keep), and I thought these projects could work pretty cool together. So, I'm trying to understand if they are still being used.

hey! would be cool to chat about what you've build. we are currently building Keep (https://github.com/keephq/keep) where you can define alerts as YAML's. would be cool to learn from you.