elastalert2
vector
elastalert2 | vector | |
---|---|---|
5 | 96 | |
813 | 16,512 | |
- | 1.5% | |
9.4 | 9.9 | |
3 days ago | 6 days ago | |
Python | Rust | |
Apache License 2.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
elastalert2
-
Ask HN: Do you use Elasticsearch/elastalert and/or praeco for alerting?
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.
-
Is ELK overkill for this?
We use https://github.com/jertel/elastalert2 to drive our main alerting pipelines of elasticsearch logs. We also use OpsGenie.
-
Log alerting: trigger alert when specific log string has not been logged on specific time
Try using Elastalert
- New DevOps Engineer looking for advice for monitoring and alerting
-
Does Elasticalert monitorize everything you want?
You can use something like Elastalert2 as an alternative.
vector
-
Docker Log Observability: Analyzing Container Logs in HashiCorp Nomad with Vector, Loki, and Grafana
job "vector" { datacenters = ["dc1"] # system job, runs on all nodes type = "system" group "vector" { count = 1 network { port "api" { to = 8686 } } ephemeral_disk { size = 500 sticky = true } task "vector" { driver = "docker" config { image = "timberio/vector:0.30.0-debian" ports = ["api"] volumes = ["/var/run/docker.sock:/var/run/docker.sock"] } env { VECTOR_CONFIG = "local/vector.toml" VECTOR_REQUIRE_HEALTHY = "false" } resources { cpu = 100 # 100 MHz memory = 100 # 100MB } # template with Vector's configuration template { destination = "local/vector.toml" change_mode = "signal" change_signal = "SIGHUP" # overriding the delimiters to [[ ]] to avoid conflicts with Vector's native templating, which also uses {{ }} left_delimiter = "[[" right_delimiter = "]]" data=<
- FLaNK AI Weekly 18 March 2024
- Vector: A high-performance observability data pipeline
-
Hacks to reduce cloud spend
we are doing something similar with OTEL but we are looking at using https://vector.dev/
-
About reading logs
We don't pull logs, we forward logs to a centralized logging service.
-
Self hosted log paraer
opensearch - amazon fork of Elasticsearch https://opensearch.org/docs/latestif you do this an have distributed log sources you'd use logstash for, bin off logstash and use vector (https://vector.dev/) its better out of the box for SaaS stuff.
-
creating a centralize syslog server with elastic search
I have done something similar in the past: you can send the logs through a centralized syslog servers (I suggest syslog-ng) and from there ingest into ELK. For parsing I am advice to use something like Vector, is a lot more faster than logstash. When you have your logs ingested correctly, you can create your own dashboard in Kibana. If this fit your requirements, no need to install nginx (unless you want to use as reverse proxy for Kibana), php and mysql.
-
Show HN: Homelab Monitoring Setup with Grafana
I think there's nothing currently that combines both logging and metrics into one easy package and visualizes it, but it's also something I would love to have.
Vector[1] would work as the agent, being able to collect both logs and metrics. But the issue would then be storing it. I'm assuming the Elastic Stack might now be able to do both, but it's just to heavy to deal with in a small setup.
A couple of months ago I took a brief look at that when setting up logging for my own homelab (https://pv.wtf/posts/logging-and-the-homelab). Mostly looking at the memory usage to fit it on my synology. Quickwit[2] and Log-Store[3] both come with built in web interfaces that reduce the need for grafana, but neither of them do metrics.
- [1] https://vector.dev
-
Retaining Logs generated by service running in pod.
Log to stdout/stderr and collect your logs with a tool like vector (vector.dev) and send it to something like Grafana Loki.
-
Lightweight logging on RPi?
I would recommend that you run vector as a systems service so you don't have to worry about managing it. Here is a basic config to do that - https://github.com/vectordotdev/vector/blob/master/distribution/systemd/vector.service .
What are some alternatives?
elastalert - Easy & Flexible Alerting With ElasticSearch
graylog - Free and open log management
helm-charts - Prometheus community Helm charts
Fluentd - Fluentd: Unified Logging Layer (project under CNCF)
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
agent - Vendor-neutral programmable observability pipelines.
otomi-core - Self-hosted DevOps PaaS for Kubernetes
syslog-ng - syslog-ng is an enhanced log daemon, supporting a wide range of input and output methods: syslog, unstructured text, queueing, SQL & NoSQL.
keep - The open-source alert management and AIOps platform
OpenSearch - 🔎 Open source distributed and RESTful search engine.
prometheus-es-exporter - Prometheus Elasticsearch Exporter
tracing - Application level tracing for Rust.