syslog-ng
| splunk-otel-collector | syslog-ng | |
|---|---|---|
| 3 | 8 | |
| 172 | 2,048 | |
| 4.1% | 1.6% | |
| 9.9 | 9.9 | |
| 1 day ago | 4 days ago | |
| Go | C | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
splunk-otel-collector
-
Fluent-Bit for Splunk
Check out the Otel collector. https://github.com/signalfx/splunk-otel-collector. We use Splunk Connect for Kubernetes to grab logs. This project is the newer version of the same project.
-
Help with Docker Splunk and UF
I would utilize our Otel collector you will be using our HEC collector to send over logs to splunk https://github.com/signalfx/splunk-otel-collector
-
Auto generated data for Observability training
To collect data: https://github.com/signalfx/splunk-otel-collector
syslog-ng
-
Fluent-Bit for Splunk
Syslog-ng can feed splunk directly via HEC without having to use heavy forwarders. Earlier you had to hand configure it via the http () destination, v4.2 added this via a separate destination driver. https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-4.2.0
-
23.1.7 is up
ports: syslog-ng 4.1.1[6]
- syslog-ng 4 has been released
- Issue with syslog-ng messages
-
Let's talk logs
Syslog-ng seems a bit weird about open/close source. They have a github but it seems like all the documentation is seemingly all over the place & it's not obvious to find what the limitations of open source version are.
-
I Don't Think Elasticsearch Is a Good Logging System
What we do internally is use [syslog-ng](https://github.com/syslog-ng/syslog-ng) to read the journald socket and push to a remote and into Kafka. I think journald works well as a structured logging tool, but it's certainly deficient in other ways
-
Log management solution
We're using syslog-ng in my apprenticeship, it works just fine, interfacing with a in-prem Prometheus/Elasticsearch
-
OPNsense 21.1.3 released
[12] https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-3.31.1
What are some alternatives?
observability-content-contrib - Contribution repository for Splunk Observability Content (e.g. Dashboards, Detectors, Examples, etc)
rsyslog - a Rocket-fast SYStem for LOG processing
fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows
graylog - Free and open log management
vector - A high-performance observability data pipeline.
zeek-clickhouse
helm-charts
ClickHouse - ClickHouse® is a real-time analytics DBMS
qryn - qryn is a polyglot, high-performance observability framework for ClickHouse. Ingest, store and analyze logs, metrics and telemetry traces from any agent supporting Loki, Prometheus, OTLP, Tempo, Elastic, InfluxDB and many more formats and query transparently using Grafana or any other compatible client.
core - OPNsense GUI, API and systems backend
systemd - The systemd System and Service Manager
elasticsearch-py - Official Python client for Elasticsearch