graylog2-server
open-sourceThe section your link pointed to isn't on graylog2-server's page any more, so we've brought you to the top.
Free and open log management
Summary
graylog2-server is an open-source log management platform that collects, indexes, and analyzes log data, released under the Server Side Public License rather than a permissive open-source license, so it is free to use but with SSPL's restrictions on offering it as a hosted service. It runs as a self-hosted service, deployed on your own infrastructure, and is administered partly through a command-line interface that handles bulk data dumps in ndjson format and supports mTLSmTLSMutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. for secure connections to collectors, including Windows event log sources. It fits SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts and infrastructure teams who need centralized log aggregation and search rather than a packaged detection product. It sits in the SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. and log management space alongside tools like the ELK stack, though nothing in its own documentation names a direct competitor. The project has an active community, a public issue tracker, and a contributor base that suggests it is under continued maintenance.
Free and open log management
How graylog2-server helps
Which hosts and applications are actually logging something bad right now?
correlates incoming log events against configured event definitions and surfaces matches as alerts, so a spike or a specific pattern turns into a notification instead of sitting unread in a stream
Where did this event come from and what else happened around the same time?
lets you search across all indexed log data with a query language, filter by stream or time window, and pivot into the surrounding messages to reconstruct a sequence
Which raw log sources are feeding into a given investigation?
routes messages from configured inputs and collectors, including Windows event log sources, into streams and pipelines so you can trace which agent or receiver type a message originated from
Does this incident match a known attack pattern rather than a one-off anomaly?
evaluates incoming events against Sigma rules and returns which rule fired, tying the raw log line to a named detection technique
How much risk does a given asset or user actually carry over time?
aggregates matched events and enrichment data into a risk score per entity, so you can rank what to look at first instead of triaging every alert equally
Can I move a large batch of historical logs out of the platform for offline review or migration?
the command-line interface dumps stored messages to ndjson files, letting you hand off a self-contained export rather than querying the live cluster for each record
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for graylog2-server, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail graylog2-server puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
11 entries
No entries match these filters.
- July 20262
- June 20262
- June 20251
- May 20251
- April 20251
- November 20241
- February 20242
- July 20231
Project health
Issue, contributor and maintainer activity in Graylog2/graylog2-server, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 39 −2 vs prior 12 months
- Maintainers 15 +5 joined · −5 left, last 12 months
- Bus factor 6 committers behind half the commits
- Community-filed 70% of issues opened, last 12 months
- Median time to close 32 days first maintainer reply 9.8 days
- Open backlog 1,865 of 8,516 issues ever filed
- Issues opened / month 16 · 9 communitymaintainers
- Open backlog 1,865
- Contributors / month 21
- Commits / month 87
- Stars 8,133
- bugs 53%
- features 21%
- docs 0%
- other 26%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →