Skip to content

Releases: tenzir/tenzir

Tenzir Node v4.22.2

28 Oct 13:51
v4.22.2
b43476a
Compare
Choose a tag to compare

This patch release contains the following bug fixes and improvements over Tenzir Node v4.22.1:

Tenzir Node v4.22.2

  • We fixed a bug that sometimes prevented incoming connections from load_tcp from closing properly.
  • The google-cloud-pubsub connector and TQL2 operators load_google_cloud_pubsub save_google_cloud_pubsub operators are now available in the Docker image.
  • We fixed a bug that caused the mode aggregation function to sometimes ignore some input values.
  • We fixed a bug in the buffer operator that caused it to break when restarting a pipeline or using multiple buffers in a "parallel" context, such as in load_tcp's pipeline argument.
  • The new value_counts aggregation function returns a list of values and their frequency.
  • The new sort method sorts fields in records by name and lists by values.

Tenzir Node v4.22.1

23 Oct 11:20
v4.22.1
324214e
Compare
Choose a tag to compare

This patch release contains the following bug fixes and improvements over Tenzir Node v4.22:

Tenzir Node v4.22.1

  • The /serve endpoint now returns instantly when its pipeline fails before the endpoint is used for the first time. In the Tenzir Platform this causes the load more button in the Explorer to correctly stop showing for pipelines that fail shortly after starting.
  • The boolean operators and/or now work correctly for the type null. Previously, null and false evaluated to null, and a warning was emitted. Now, it evaluates to false without a warning.
  • Using the tenzir process from multiple users on the same host sometimes failed because the cache directory was not writable for all users. This no longer happens.
  • We added three new, TQL2-exclusive aggregation functions: first, last, and mode. The functions return the first, last, and most common non-null value per group, respectively.

Tenzir Node v4.22.0

18 Oct 19:25
v4.22.0
90ac560
Compare
Choose a tag to compare

Tenzir Node v4.22 comes with documentation for the new version of the Tenzir Query Language, connectors for Google Cloud Pub/Sub and various bug fixes.

image

Discover Tenzir Node v4.22

📣 Dive into the details of Tenzir Node v4.22 from our announcement blog post.
🎯 Check out the new features on app.tenzir.com.
🚀 Follow the quickstart guide, get your fingers dirty and explore the demo node with just a few clicks and a guided tour. Security data has never been easier.
🎓 Learn the basics of pipelines and get familiar with the Tenzir Query Language (TQL). You'll master security data in no time.
💭 Understand why Tenzir was developed and how it measures up against the competition.
📝 Read all the details in our changelog.

Tenzir Node v4.21.1

11 Oct 08:23
v4.21.1
e606c7a
Compare
Choose a tag to compare

This patch release contains the following bug fixes and improvements over Tenzir Node v4.21:

Tenzir Node v4.21.1

  • We fixed a bug that sometimes caused the tenzir-node process to hang on shutdown. This was most likely to happen when the node shut down immediately after starting up, e.g., because of an invalid configuration file.
  • Fixed a bug in the python operator that could lead to random valid file descriptors in the parent process being closed prematurely.
  • The azure-blob-storage connector is now also available in the static linux binary distributions.
  • We fixed a bug that caused the context_updates field in metrics lookup to be reported once per field specified in the corresponding lookup operator instead of being reported once per operator in total.
  • A new sample operator now provides the ability to dynamically sample input data based on the frequency of the receiving events allowing relative sampling in situations of varying load.
  • The grok parser now allows better control over the schema inference.
  • The grok parser can now be directly used when reading input, allowing for read grok.

Tenzir Node v4.21.0

04 Oct 14:08
v4.21.0
e3d3797
Compare
Choose a tag to compare

Parsing is now easier, faster, and better than before with Tenzir Node v4.21. Also: introducing an all-new integration with Azure Blob Storage.

Tenzir Node v4.21

Discover Tenzir Node v4.21

📣 Dive into the details of Tenzir Node v4.21 from our announcement blog post.
🎯 Check out the new features on app.tenzir.com.
🚀 Follow the quickstart guide, get your fingers dirty and explore the demo node with just a few clicks and a guided tour. Security data has never been easier.
🎓 Learn the basics of pipelines and get familiar with the Tenzir Query Language (TQL). You'll master security data in no time.
💭 Understand why Tenzir was developed and how it measures up against the competition.
📝 Read all the details in our changelog.

Tenzir Node v4.20.3

09 Sep 13:19
v4.20.3
3974eff
Compare
Choose a tag to compare

This patch release contains the following bug fixes and improvements over Tenzir Node v4.20:

Tenzir Node v4.20.3

  • We fixed a bug where the export, metrics, and diagnostics operators were sometimes missing events from up to the last 30 seconds. In the Tenzir Platform, this showed itself as a gap in activity sparkbars upon loading the page.
  • The /serve endpoint now gracefully handles retried requests with the same continuation token, returning the same result for each request.

Tenzir Node v4.20.2

  • The empty record type is no longer rejected in schema definitions.
  • We fixed a bug that caused the Demo Node package not to be pre-installed correctly when using the tenzir/tenzir-demo Docker image.
  • We fixed a potential crash in the csv, ssv, and tsv parsers for slowly arriving inputs.
  • The azure-log-analytics operator sometimes errored on startup complaining about an unknown window option. This no longer occurs.
  • Restarting pipelines with the udp connector no longer fails to bind to the socket.
  • The systemd unit now allows binding to privileged ports by default via the ambient capability CAP_NET_BIND_SERVICE.

Tenzir Node v4.20.1

  • We fixed a regression introduced with Tenzir v4.20 that sometimes caused the Tenzir Platform to fail to fetch results from pipelines.

Tenzir Node v4.20.2

06 Sep 14:15
v4.20.2
3fb62a0
Compare
Choose a tag to compare

This patch release contains the following bug fixes and improvements over Tenzir Node v4.20:

Tenzir Node v4.20.2

  • The empty record type is no longer rejected in schema definitions.
  • We fixed a bug that caused the Demo Node package not to be pre-installed correctly when using the tenzir/tenzir-demo Docker image.
  • We fixed a potential crash in the csv, ssv, and tsv parsers for slowly arriving inputs.
  • The azure-log-analytics operator sometimes errored on startup complaining about an unknown window option. This no longer occurs.
  • Restarting pipelines with the udp connector no longer fails to bind to the socket.
  • The systemd unit now allows binding to privileged ports by default via the ambient capability CAP_NET_BIND_SERVICE.

Tenzir Node v4.20.1

  • We fixed a regression introduced with Tenzir v4.20 that sometimes caused the Tenzir Platform to fail to fetch results from pipelines.

Tenzir Node v4.20.1

02 Sep 09:41
v4.20.1
87a6d69
Compare
Choose a tag to compare

This patch release contains the following bug fixes and improvements over Tenzir Node v4.20:

Tenzir Node v4.20.1

  • We fixed a regression introduced with Tenzir v4.20 that sometimes caused the Tenzir Platform to fail to fetch results from pipelines.

Tenzir Node v4.20

30 Aug 13:35
v4.20.0
d347722
Compare
Choose a tag to compare

Tenzir Node v4.20 is here, bringing a host of under-the-hood improvements that pave the way for exciting upcoming changes to the Tenzir Platform.

Tenzir Node v4.20

Discover Tenzir Node v4.20

📣 Dive into the details of Tenzir Node v4.20 from our announcement blog post.
🎯 Check out the new features on app.tenzir.com.
🚀 Follow the quickstart guide, get your fingers dirty and explore the demo node with just a few clicks and a guided tour. Security data has never been easier.
🎓 Learn the basics of pipelines and get familiar with the Tenzir Query Language (TQL). You'll master security data in no time.
💭 Understand why Tenzir was developed and how it measures up against the competition.
📝 Read all the details in our changelog.

Tenzir v4.19.6

15 Aug 14:10
v4.19.6
a5b24ed
Compare
Choose a tag to compare

This patch release contains the following bug fixes and improvements over Tenzir v4.19:

Tenzir v4.19.6

  • Pipelines with the python operator now deploy more quickly, as their deployment no longer waits for the virtual environment to be set up successfully.
  • We fixed a bug in the shell operator that could cause the process to crash when breaking its pipe. Now, the operator shuts down with an error diagnostic instead.
  • The slice operator no longer crashes when used with a positive begin and negative end value when operating on less events than -end, e.g., when working on a single event and using slice 0:-1.
  • The tenzir command-line utility gained a new option --strict, causing it to exit with a non-zero exit code for pipelines that emit at least one warning.

Tenzir v4.19.5

  • The serve operator no longer uses an excessive amount of CPU.

Tenzir v4.19.4

  • The packages plugin is now available in the static binary release artifacts.

Tenzir v4.19.3

  • Pipelines from packages now correctly remember their last run number and last state when reinstalling the package.

Tenzir v4.19.2

  • The subscribe operator now delivers metrics more consistently.
  • The throttle operator allows for limiting the bandwidth of a pipeline.
  • We've made some changes that optimize Tenzir's memory usage. Pipeline operators that emit very small batches of events or bytes at a high frequency now use less memory. The serve operator's internal buffer is now soft-capped at 1Ki instead of 64Ki events, aligning the buffer size with the default upper limit for the number of events that can be fetched at once from /serve. The export, metrics, and diagnostics operators now handle back pressure better and utilize less memory in situations where the node has many small partitions. For expert users, the new tenzir.demand configuration section allows for controlling how eagerly operators demand input from their upstream operators. Lowering the demand reduces the peak memory usage of pipelines at some performance cost.

Tenzir v4.19.1

  • We fixed a problem where a stoppingpython operator could cause a crash.
  • The python operator is now compatible with Python 3.9 again.
  • The AMQP connector now handles connections with heartbeats correctly.
  • We restored the performance of the partitions operator to pre --experimental-include-ranges times, when the flag is not used.