Release Notes
Release Notes — 2.100
Covers the 2.100.x Helm chart series. Most recent patch: 2.100.6.
Unless a subsection says otherwise, changes apply to both Monad SaaS and self-hosted.
New features & improvements
- Keep the previous API key token valid while you rotate — when you regenerate an API key, you can keep the previous token working for 1 to 90 days so your integrations have time to switch to the new one. The API Keys table shows when the previous token stops working. Docs → (2.100.2)
- Access: opt-in — use the Regenerate row action on the API Keys page and pick a Previous token period instead of Revoke immediately. Over the API, pass
previous_token_expiration_timeto the regenerate endpoint.
- Access: opt-in — use the Regenerate row action on the API Keys page and pick a Previous token period instead of Revoke immediately. Over the API, pass
- Route records by size — edge conditions have a new Record size larger than rule, so you can send records over a size threshold to a different output (for example, one that accepts larger records) instead of trimming them in a transform. (2.100.3)
- Access: opt-in — in the pipeline editor, edit an edge's conditions and choose Record size larger than, then enter the size in bytes.
- Embed SDK: prefill connector fields with your own defaults —
configMetaOverridesnow takes adefaultfor text, number, and true/false fields, so white-label forms can replace Monad's prefilled values (such as the PagerDuty alert source or the Slack message template) with your own. The value stays editable. (2.100.2)- Access: opt-in — set
defaulton a field inconfigMetaOverrides; needs@monad-inc/embed0.4.0 or later. Defaults apply when creating a component, not when editing one.
- Access: opt-in — set
New connectors
- Azure Kubernetes Service (AKS) Audit Logs (input) — ingests Kubernetes API server audit logs from AKS clusters, read from a Log Analytics workspace or an Azure event hub. Audit logs record every request to the Kubernetes control plane: who did what, to which object, and whether it was allowed. Docs → (2.100.2)
Fixes
SaaS & self-hosted
- Volume Anomaly alerts compare against the right baseline — the weekly history behind an anomaly baseline is now sampled at the time each evaluation runs, instead of always at the same hour of the week, which caused false positives. (2.100.2)
- Azure Blob Storage input no longer re-sends append blobs — append blobs in JSON Lines format without compression, such as Azure Monitor diagnostic logs, are now read from where the input left off instead of being downloaded and sent again in full after every append. (2.100.3)
- Salesforce Pub/Sub and CrowdStrike Event Stream inputs clear their Erroring status after recovering — once the stream reconnects, the input returns to Running even if no new records have arrived yet. (2.100.3)
Self-hosted only
- The UI no longer restarts on pages that load a lot at once — the ui's default memory limit is raised from 128Mi to 256Mi, so pages such as creating a transform no longer get the container OOM-killed. If you set
ui.resources, your values are kept. (2.100.1)
Breaking changes
None.
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.100.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