Apache CloudStack
CloudStack's feed shows two LTS branches maintained in parallel and little else
Comparison · Infra & APIs
Icinga vs Luminescence
A side-by-side editorial comparison of Icinga and Luminescence — release velocity, themes, recent moves, and the top alternatives to consider.
Icinga vs Luminescence: at a glance
What is Icinga?
Icinga 2 is fixing the same API permission holes across every supported branch.
Icinga 2 ships security fixes as simultaneous releases across its 2.14, 2.15, and 2.16 branches, and has now done so twice in five weeks. The 18 August pair - v2.16.5 and v2.15.6, tagged 25 seconds apart - closes an events/* permission bypass on /v1/events and a memory-exhaustion path where a node could crash another using the 1 GB message limit, now capped at 16 MiB for messages from lower in the hierarchy. v2.16.5 additionally repairs an IcingaDB regression introduced in v2.16.0.
What is Luminescence?
Luminescence is revisiting the statistical assumptions baked into its dose-response fits.
The package provides luminescence dating analysis for the geochronology community — signal import from several instrument formats, dose-response curve fitting, and a large library of analysis routines. The current release changes how fitting weights are handled by default, on the reasoning that individual relative uncertainties do not in fact scale with dose as the previous approach assumed. Several releases in this window are historical versions backfilled into the feed, so their timestamps sit within minutes of each other and do not reflect when the work shipped.
Icinga vs Luminescence: editorial side-by-side
Icinga
5.0INFRA · APIS
Icinga 2 is fixing the same API permission holes across every supported branch.
◆ Current state
Icinga 2 ships security fixes as simultaneous releases across its 2.14, 2.15, and 2.16 branches, and has now done so twice in five weeks. The 18 August pair - v2.16.5 and v2.15.6, tagged 25 seconds apart - closes an events/* permission bypass on /v1/events and a memory-exhaustion path where a node could crash another using the 1 GB message limit, now capped at 16 MiB for messages from lower in the hierarchy. v2.16.5 additionally repairs an IcingaDB regression introduced in v2.16.0.
◆ Where it's heading
The recurring theme is that the API's filter and permission model was more permissive than intended. July's critical release introduced a filter-expression permission so DSL filters in API queries can be restricted per user, with enforcement deliberately deferred to v2.17; August's pair fixes filter expressions on /v1/events not being permission-checked at all. Cluster message handling is being tightened in parallel. The project is clearly working through an audit of the API surface, and it is backporting every finding rather than pushing users onto the newest branch.
◆ Prediction
Enforcement of the filter-expression permission is already scheduled for v2.17, so that release should be the one where the opt-in restrictions become mandatory - expect more backported API permission fixes across all three branches before it lands.
Luminescence
2.5INFRA · APIS
Luminescence is revisiting the statistical assumptions baked into its dose-response fits.
◆ Current state
The package provides luminescence dating analysis for the geochronology community — signal import from several instrument formats, dose-response curve fitting, and a large library of analysis routines. The current release changes how fitting weights are handled by default, on the reasoning that individual relative uncertainties do not in fact scale with dose as the previous approach assumed. Several releases in this window are historical versions backfilled into the feed, so their timestamps sit within minutes of each other and do not reflect when the work shipped.
◆ Where it's heading
Two kinds of change dominate. The first is deliberate breaking changes made for correctness or consistency: the weighting rework, and import functions now uniformly appending the detector to record types so all formats behave as one always did. The second is a steady stream of new analysis functions contributed by the wider research community, covering crosstalk correction, spatial autocorrelation on grain discs, and incomplete bleaching models. Deprecated functions are being removed on a clear schedule rather than left indefinitely.
◆ Prediction
Expect further consolidation of defaults that were inherited rather than chosen, since the weighting change is framed as correcting earlier reasoning rather than adding an option.
Alternatives to Icinga and Luminescence
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 Icinga or Luminescence.
ManageEngine Applications Manager
Applications Manager pushes monitoring past the server and out to the end user's network path
ToolJet
ToolJet's LTS and beta trains both narrow to component polish and CVE patching
missSBM
missSBM returns after four dormant years with a stricter API and a new refinement step.
sps
sps keeps sanding down sequential Poisson sampling rather than adding to it.
simDAG
simDAG grew a second simulation engine, then spent two releases surviving upstream breakage.
See all Icinga alternatives → · See all Luminescence alternatives →
Recent activity from Icinga and Luminescence
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5h agoIcingav2.16.5: /v1/events permission bypass and node memory exhaustion fixed
- 5h agoIcingav2.15.6: the 2.15-branch twin of the August security fixes
- 25d agoLuminescenceReworks dose-response fitting weights, changing prior defaults
- 1mo agoIcingaFixes API auth regression and hanging endpoint connections
- 1mo agoIcingaSecurity release for the 2.14 branch, adds filter-expression permission
- 1mo agoIcingaSecurity release for the 2.15 branch
- 1mo agoIcingaSecurity release for the current 2.16 branch
- 4mo agoLuminescenceFixes an uninitialised array and background overcounting
- 5mo agoLuminescenceImport functions now append detector type to record names
- 7mo agoLuminescenceAdds crosstalk correction, Moran's I, and dose-response fitting
- 7mo agoLuminescenceFixes baSAR reporting, fading input checks, and plot regressions
- 7mo agoLuminescenceAdds automatic background subtraction and record removal helpers
Frequently asked questions
What is the difference between Icinga and Luminescence?
They serve adjacent needs but don't currently overlap on shipped themes. Icinga is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Icinga better than Luminescence?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Icinga is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Icinga?
Top Icinga alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Icinga alternatives" section above for the current picks, or visit /alternatives/icinga for the full list with editorial commentary on each.
What are the best alternatives to Luminescence?
Top Luminescence alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Luminescence alternatives" section above for the current picks, or visit /alternatives/luminescence for the full list with editorial commentary on each.