Thanos
Thanos is rebuilding Receive around multi-tenancy, and shipping it through a stuttering RC train.
Comparison · Infra & APIs
Jaeger vs MISP
A side-by-side editorial comparison of Jaeger and MISP — release velocity, themes, recent moves, and the top alternatives to consider.
Jaeger vs MISP: at a glance
What is Jaeger?
Jaeger folds its MCP server into the query service and drops Elasticsearch 6
Jaeger's 2.x line is releasing roughly monthly, and two threads dominate. The storage layer is being modernised and pruned — Elasticsearch 6 support removed, rotation and index-cleaner feature gates promoted to beta, ClickHouse gaining TLS and analyzer fixes, configurable max trace duration. The other thread is the query surface: a lightweight trace-summaries endpoint added in 2.19 then given a native Elasticsearch implementation in 2.20, and the MCP extension merged into the query extension.
What is MISP?
MISP extends instance-to-instance sync to collections while a security-hardening program runs underneath
MISP is shipping on a roughly two-week cadence, and three tracks run through every release. The first is federation: 2.5.43 added collection synchronisation between instances in both pull and push directions, with per-server toggles and feature negotiation. The second is a sustained security program — 2.5.40, 2.5.41 and 2.5.42 are all substantially security releases, with 2.5.42 alone closing two RCE vectors and a mass-assignment sweep across a 74-controller review. The third is the Overmind UI migration to Bootstrap 5, which lands a batch of converted views in nearly every release.
Jaeger vs MISP: editorial side-by-side
Jaeger
3.8INFRA · APIS
Jaeger folds its MCP server into the query service and drops Elasticsearch 6
◆ Current state
Jaeger's 2.x line is releasing roughly monthly, and two threads dominate. The storage layer is being modernised and pruned — Elasticsearch 6 support removed, rotation and index-cleaner feature gates promoted to beta, ClickHouse gaining TLS and analyzer fixes, configurable max trace duration. The other thread is the query surface: a lightweight trace-summaries endpoint added in 2.19 then given a native Elasticsearch implementation in 2.20, and the MCP extension merged into the query extension.
◆ Where it's heading
Jaeger is treating machine consumption of traces as a first-class query path rather than an add-on. Merging jaegermcp into jaegerquery means the MCP surface ships wherever query ships, and trace summaries give both the UI and any agent a cheap way to scan results before pulling full traces. On storage, the direction is fewer supported backends maintained better, with ClickHouse steadily gaining parity.
◆ Prediction
Expect the trace-summaries path to become the default for search across storage backends, and further ClickHouse feature work as the Elasticsearch surface is trimmed rather than extended.
MISP
6.3INFRA · APIS
MISP extends instance-to-instance sync to collections while a security-hardening program runs underneath
◆ Current state
MISP is shipping on a roughly two-week cadence, and three tracks run through every release. The first is federation: 2.5.43 added collection synchronisation between instances in both pull and push directions, with per-server toggles and feature negotiation. The second is a sustained security program — 2.5.40, 2.5.41 and 2.5.42 are all substantially security releases, with 2.5.42 alone closing two RCE vectors and a mass-assignment sweep across a 74-controller review. The third is the Overmind UI migration to Bootstrap 5, which lands a batch of converted views in nearly every release.
◆ Where it's heading
The security work reads as a deliberate audit rather than incident response — the fixes are systematic (mass-assignment and broken-access-control across the controller layer, OIDC hardening, ACL enforcement on cluster search) and credited to named external researchers across four consecutive releases. Alongside it, the interop surface keeps widening: TAXII 2 conformance and scheduled push, STIX moved onto the upstream misp-stix library, and now collection sync. The Overmind migration is the slow constant, converting the UI tab by tab rather than in one cutover.
◆ Prediction
The Overmind migration and the Pivotick pivot explorer are both mid-rollout, so the next releases should continue converting views and fill out Pivotick rather than open a new track. Given the pattern of the last four releases, expect further externally-reported security fixes to ship alongside them.
Alternatives to Jaeger and MISP
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Jaeger or MISP.
webpack
webpack is absorbing its own loader ecosystem — TypeScript, CSS and HTML now build natively.
Apereo CAS
CAS 8.0 is six release candidates deep with notes that describe nothing
LibreELEC
LibreELEC's changelog stops dead at the 12.0 release in May 2024
Node-RED
Node-RED 5.0 rebuilt the editor, and the patches since are settling it in
Biome
Biome's patch train is really a type-aware linting project in disguise
Recent activity from Jaeger and MISP
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 14d agoJaegerMCP merges into the query service; Elasticsearch 6 support removed ⚡
- 21d agoMISPCollections now sync between MISP instances, plus Pivotick pivot explorer ⚡
- 21d agoMISPHotfix for pull sync failing on untagged events
- 1mo agoMISPTwo RCE fixes and a 74-controller access-control sweep, plus TAXII scheduled push
- 1mo agoMISPGalaxy cluster mass-assignment, OIDC redirect loop and dashboard ACL fixes
- 1mo agoMISPSecurity release resolving externally disclosed vulnerabilities
- 1mo agoMISPMISP 2.5.39: New Dashboard Experience, Stronger STIX, Sharper Analyst Workflows
- 2mo agoJaegerLightweight trace-summaries endpoint arrives in the v3 API
- 2mo agoJaegerHeader forwarding to storage backends and UI base-path autodetection
- 4mo agoJaegerClock-skew and jitter fixes; metrics storage exposed to the UI
- 4mo agoJaegerLegacy remote-sampling response format removed; Go 1.25.7 required
- 5mo agoJaegerPatch: default span kind in operations endpoint
Frequently asked questions
What is the difference between Jaeger and MISP?
They serve adjacent needs but don't currently overlap on shipped themes. MISP is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Jaeger better than MISP?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. MISP is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Jaeger?
Top Jaeger alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Jaeger alternatives" section above for the current picks, or visit /alternatives/jaeger for the full list with editorial commentary on each.
What are the best alternatives to MISP?
Top MISP alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "MISP alternatives" section above for the current picks, or visit /alternatives/misp for the full list with editorial commentary on each.