elastalert2 VS kube-prometheus

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.

We use https://github.com/jertel/elastalert2 to drive our main alerting pipelines of elasticsearch logs. We also use OpsGenie.

Try using Elastalert

You can use something like Elastalert2 as an alternative.

The last one is mostly an observability stack with Prometheus, Metric server, and Prometheus adapter to have excellent insights into what is happening on the cluster. You can reuse the same stack for autoscaling by repurposing all the data collected for monitoring.

kustomize Kube Prometheus

On the other hand, the Kube-prometheus project provides documentation and scripts to operate end-to-end Kubernetes cluster monitoring using the Prometheus Operator, making easier the process of monitoring the Kubernetes cluster.

For our load testing we’ve deployed Temporal on Kubernetes, and we’re using MySQL for the persistence backend. The MySQL instance has 4 CPU cores and 32GB RAM, and each Temporal service (Frontend, History, Matching, and Worker) has 2 pods, with requests for 1 CPU core and 1GB RAM as a starting point. We’re not setting CPU limits for our pods—see our upcoming Temporal on Kubernetes post for more details on why. For monitoring we’ll use Prometheus and Grafana, installed via the kube-prometheus stack, giving us some useful Kubernetes metrics.

The 2 most common approaches I have seen are kube-prometheus-stack and kube-prometheus..

- I'm missing a lot of the Grafana dashboards that are provisioned during the deployment, not sure why as it has worked before, and wanted to add them after install... I believe it's different ConfigMaps like the one in kube-prometheus but I was wondering if there's a way to force provisioning them all again at once (multiple k8s, node_exporter, vm, etc)?

Check out the kube Prometheus project -- https://github.com/prometheus-operator/kube-prometheus It's a bit heavy, but the included recording rules and dashboards give you a great start at understanding your cluster.

The actual link to the prometheus/grafana bundle: https://github.com/prometheus-operator/kube-prometheus

Here’s a list of what’s installed: https://github.com/prometheus-operator/kube-prometheus/tree/main/manifests