| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Telemetry pipelines | IT operations and endpoint | 0% | 124 of 124 | 89% | 9 | under 10 labels · led by OpenTelemetry Collector at 37% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 1 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 3 | 3 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.20 | 0 | 0 | 0 | 0 | 0 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 1 | 1 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 2 | 2 |
| Kimi K2 | 0 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 1 | 1 |
Verbatim evidence the judge attached to positive labels.
“For Elastic ecosystems: Logstash or Filebeat” MiniMax M2.5 · Telemetry pipelines · comparative prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“It carries a massive memory footprint and slow startup times. Caution: Avoid deploying Logstash directly on application nodes as a local shipper.” Gemini 3.5 Flash · Telemetry pipelines · negative prompt · soft negative
“Heavy resource consumption (often cited as a high-memory Java app); primarily log-centric; being increasingly displaced by lighter alternatives” DeepSeek V4 Flash · Telemetry pipelines · comparative prompt · soft negative
“Caution: Relying entirely on Logstash or heavy Elasticsearch clusters for simple filtering before storage.” Qwen 3.7 Flash · Telemetry pipelines · negative prompt · soft negative
“Choose Logstash only if you're already deep in the Elastic ecosystem” GPT-5.4 mini · Telemetry pipelines · paraphrase prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 17 of the 22 answers that named Logstash and are not a share of its labels.
No domain is on file for Logstash, so its own site is not marked.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Logstash's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Logstash, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Logstash by email, built from the raw record of the edition. It shows: