Release Notes
Release Notes — 2.99
Covers the 2.99.x Helm chart series. Most recent patch: 2.99.5.
Unless a subsection says otherwise, changes apply to both Monad SaaS and self-hosted.
New features & improvements
- Finxact inputs are generally available — the Finxact Error Log, Messages, Rule Log, Login, and Login Events inputs are out of Beta. Docs → (2.99.2)
- Edit a secret without leaving the component form — when a secret is selected in a component's secret field, a pencil button next to it opens the secret's edit dialog, so you can change its name, description, or value in place. Leave the value blank to keep the current one. (2.99.5)
- KV Lookup enrichment is faster and lighter on memory — lookups are encoded once per lookup instead of once per record, and the enrichment cache now stays within its memory budget. (2.99.5)
New connectors
- Google Cloud Storage via Pub/Sub (input) — ingests objects from a Cloud Storage bucket as they land, driven by the bucket's Pub/Sub notifications instead of listing the bucket. It's the Google Cloud counterpart to the SQS S3 and Azure Blob Storage Queue inputs and suits higher-volume buckets. Docs → (2.99.5)
- Idira Detailed Raw Events (input) — Beta — collects all detailed raw events from Idira (formerly CyberArk EPM) through the EPM detailed raw events API, not only the policy-triggered events the Idira Policy Audit Events input returns. Docs → (2.99.5)
Fixes
- CloudTrail and Backblaze B2 inputs no longer skip data after an interrupted run — when a run stops partway through a file, the input now resumes from its last saved point instead of skipping the rest of that file. (2.99.1)
- CrowdStrike Event Stream no longer repeats the last event — after a reconnect or restart, the input resumes with the next event instead of delivering the last one again. (2.99.1)
- Opening a dropdown no longer scrolls the page to the top — on long component forms, selectors such as the secret picker now open in place. (2.99.1)
- A KV output in use by a KV Lookup enrichment can't be deleted — Monad now refuses the delete and names the enrichments and pipeline nodes that still use the output, instead of letting those pipelines fail. (2.99.2)
- Datadog, Coralogix, and OpenTelemetry outputs handle bad event times consistently — with a Timestamp Field set, Datadog now sends records whose timestamp is missing or invalid instead of failing them; one bad timestamp no longer fails a whole Coralogix batch; and OpenTelemetry records with a bad timestamp arrive without an event time instead of with the time Monad sent them. (2.99.2)
- Panther output no longer gets stuck on large batches — a batch that encodes larger than Panther's request limit is now split across several requests, and a single record too large for Panther is counted as a failed record instead of being retried indefinitely and holding up the pipeline. (2.99.5)
- Schema detection's View tracked schema button follows the selected edge — selecting an edge without schema detection no longer leaves the button pointing at the previously selected edge. (2.99.5)
Breaking changes
- Google SecOps output rejects records with a missing or invalid event time — records whose Log Entry Time or Collection Time is missing, has no date, uses a time zone that can't be resolved (for example
CST), is before 1990, or is more than 24 hours in the future now fail individually instead of being sent with the current time. The rest of the batch is still delivered. If your records use those forms, normalize the time field in a transform before the output, and watch the output's failed-record count after upgrading. (2.99.2)
Need help?
See the Monad docs for setup guides and reference, or reach out to Monad Customer Support at support@monad.com or via your dedicated Slack customer channel.
Self-hosted deployments upgrade to a 2.99.x release with
helm upgrade. Review the Breaking changes section above before upgrading;
when it says "None," the upgrade is drop-in.
Last modified on