Skip to content

News from the Stroom team

New features as they ship, fixes worth knowing about, how we use Stroom ourselves, and what is coming next.


  1. How I use Stroom

    How we built the security dashboard on this website

    The Security Operations dashboard in our screenshots is a real Stroom instance fed synthetic events. Here is how it is put together, and the four things that caught us out.


  2. Upcoming

    What is coming in Stroom 7.14

    S3 storage, a rebuilt processor task system, traces as documents and JSON logging are all landing in the 7.14 betas. Here is what is ready, and what is still experimental.


  3. AI

    Ask Stroom AI: from a chat panel to a function you can call

    Ask Stroom AI started as a table-summary preview in 7.11. In 7.14-beta.1 you can call a model from XSLT and StroomQL, and add AI summaries to reports.


  4. Bug fix

    Two fixes in 7.14-beta.1 worth knowing about

    Processor filters could leave a stream permanently unprocessed, and bitmap-lookup ran its values together. Both are fixed in 7.14-beta.1.


  5. Bug fix

    Plan B fixes in the 7.13 betas

    Histograms and metrics no longer double count after an interrupted merge, queued data survives a restart, and sends retry through a network blip.


  6. Feature

    Signing in through an authenticating edge proxy

    From 7.13-beta.10, Stroom can sit behind an AWS ALB with Cognito or NGINX with oauth2-proxy, and let the proxy handle sign-in.


  7. Feature

    Content that lives in Git

    Stroom 7.11 adds Git-controlled folders, a Content Store for standard packs, and a Credentials feature to hold the secrets both of them need.

Follow new posts in a feed reader: RSS.