nano SIEM
Releases

nano v2.0.19

Supported in:Self-hosted

nano v2.0.19 fixes distinct counts that counted a missing field, keeps every key of HEC object events and improves the Kubernetes guide for GKE and EKS.

v2.0.19 includes everything in v2.0.18. It is not flagged as a security release.

To upgrade, follow Upgrade a self-hosted deployment. On Docker Compose, scripts/nano upgrade upgrades v2.0.18 to v2.0.19 directly. Earlier v2.x releases also upgrade directly; there are no required stops. Read Upgrade notes if you have detection rules that use dc().

Fixes and improvements

  • dc() no longer counts a missing field. A field an event doesn't have reads as an empty value, and dc() and estdc() counted that empty value as one more distinct value. dc() of a field no event has returned 1; it now returns 0. A distinct count over events where some lack the field is now one lower, which is the correct count. This applies to stats, timechart, eventstats and streamstats. A numeric 0 still counts as a value.

Ingest

  • HEC object events keep every key. An HEC event sent as an object with a string message, such as {"event": {"message": "login failed", "user": "bob"}}, passed only the message text to the parser. A JSON parser couldn't parse that text, so the event was stored as a parse error and the other keys were lost. Now:
    • JSON parsers receive the whole object, the same as over HTTP /ingest. For the generic JSON parser, message maps to status_detail and every other key to unmapped.*.
    • Text parsers (syslog, CEF, key-value, regex) still receive the log line in message and parse it as before. The other keys are added to unmapped.* (or ext.* on UDM installs), only where the parser left that field empty.
    • nano decides which applies from the bound parser's code. To set it yourself, add a # nano:input=json or # nano:input=text comment to a custom parser.

Install and upgrade

  • Clearer migration log. A fresh install logged warnings for permission grants that the ClickHouse user configuration already provides, and for statements that apply to tables the install creates later. Those are now logged as information, with one summary per migration. Any other failed grant is still a warning.
  • Kubernetes guide. The Kubernetes guide now covers more of a first install on GKE and EKS:
    • GKE: every gcloud command passes --project; VPC, subnet and API setup; labeling; Cloud SQL zones; quota needs; and the measured Cloud SQL failover behavior.
    • EKS: the load balancer controller's IAM setup, importing a private-CA certificate into ACM, RDS creation and the security group to open.
    • OTLP over HTTP accepts protobuf only; JSON is refused with 415.

Upgrade notes

  • Distinct counts can drop by one. After upgrading, a dc() or estdc() over events where some lack the field returns one less than before. A detection rule with a threshold such as | where dc(user) > 5 can fire one value later. Review rules and dashboards that rely on dc() thresholds.
  • HEC object events change shape. Searches that relied on the old parse-error records from HEC object events, such as filtering on unmapped.parse_error, no longer match those events. Their keys are now searchable fields.

On this page