nano SIEM
Releases

nano v2.0.22

Supported in:Self-hosted

nano v2.0.22 hotfix: large parsers such as Sysmon no longer roll back on small hosts, and Helm installs keep ClickHouse reachable with allowedNetworks.

v2.0.22 includes everything in v2.0.20.

To upgrade, follow Upgrade a self-hosted deployment. On Docker Compose, scripts/nano upgrade upgrades v2.0.20 to v2.0.22 directly. Earlier v2.x releases also upgrade directly; there are no required stops.

Fixes

  • Deploying large parsers rolled back on smaller hosts. On a host with little CPU to spare for Vector, a large parser such as Microsoft Sysmon, CrowdStrike Falcon or Microsoft Defender could take longer to compile than nano waited for Vector to confirm the reload. nano then reported "Vector did not acknowledge" and rolled the deploy back, even though the config was valid.
    • The wait now grows with the size of the config: 45 seconds at minimum, up to 180 seconds.
    • It ends early when Vector rejects the config, or when Vector stops responding for 60 seconds.
    • Multi-server installs use the same wait on every ingest server.
    • A deploy that is still running after 270 seconds returns its job id instead of timing out. The deploy screen shows the progress.
  • Helm: ClickHouse could lock nano out after you set clickhouse.allowedNetworks. The chart now always keeps loopback in the list. On helm upgrade, a hook repairs a ClickHouse network config that doesn't admit the nano users and waits until every replica accepts them.
  • Helm: API probes. The API's startup, readiness and liveness probes use /livez. A ClickHouse blip no longer restarts or unroutes the API. /health still returns 200 with the state in the body. /health?strict=1 returns 503 when a dependency is down, and helm test uses it.
  • SIEM Health reports ClickHouse login refusals. When ClickHouse keeps refusing logins for a nano user, for example because of the network allow-list, SIEM Health names the user and how many refusals it saw.

Parser content

  • Large parsers compile faster again. The parser update that made parsing faster in v2.0.20 also made some parsers slower to compile. A new parser update groups the extra rules. Compile times are back near what they were before, and the faster parsing stays. Re-sync your parser repository, run Apply upstream update on each log source, then deploy.

Upgrade notes

  • Upgrade with the release, not by editing image tags. On Docker Compose, use scripts/nano upgrade or re-run install.sh from the new bundle. On Kubernetes, use helm upgrade with the new chart. These deliver the new reload settings and the Helm hook.

On this page