Release Notes — 2.70
Covers the 2.70 release series. Most recent patch: 2.70.3.
Unless a subsection notes otherwise, changes apply to both Monad SaaS and self-hosted.
New features & improvements
SaaS & self-hosted
-
Collapsible grouped side navigation — the left-hand navigation is now grouped into sections you can collapse, so it stays tidy as your workspace grows. Live for everyone. (2.70.2)
-
Longer batching windows for Kafka outputs — a Kafka output's maximum flush interval can now be set up to 20 minutes (up from 60 seconds), so a low-traffic pipeline can wait longer to accumulate a fuller batch instead of flushing many tiny ones — avoiding a small-file problem in downstream systems. Each record is still delivered as its own Kafka message; this setting only controls how long Monad waits before flushing a batch. (2.70.3)
- Access: set it on the Kafka output under the
Maximum Flush Intervalfield.
- Access: set it on the Kafka output under the
-
Clearer batch-output field name — the batch
Publish Ratesetting is now labeledMaximum Flush Intervalacross outputs, matching what it actually controls. (2.70.3) -
Self-describing HTTP ingest back-off — while the HTTP ingest endpoint is still starting up it now returns a clear
503with aRetry-Afterheader, so clients can retry gracefully instead of failing hard. (2.70.1) -
New guide: handling schema-drift alerts — a new guide on responding to Schema Drift Detection alerts. Docs → (2.70.2)
-
HTTP input accepts JSON arrays — the HTTP input now ingests a JSON array in a single request body and expands it into individual records, so batched senders no longer need one request per event. (2.70.1)
-
Unified organization users view — the organization's own users and users inherited from a parent organization are now shown in a single table, making it easier to see everyone with access at a glance. (2.70.1)
-
Filter alerts by pipeline and resource — the alerts API now supports filtering by pipeline and by resource, so you can scope alert queries to the pipeline or component you care about. (2.70.1)
-
Fresher enrichment lookups — the
kv-lookupenrichment's lookup cache now refreshes within about one second, so enrichment results reflect updates to your lookup data almost immediately. (2.70.1) -
Shared resources show their parent organization — resources shared into your organization now resolve and display the sharing (parent) organization's name, so it's clear where a shared component originates. (2.70.1)
-
Smoother pipeline continuity during restarts — pipelines now ride out routine node restarts and pod rescheduling without interruption, improving reliability during platform maintenance. (2.70.1)
Self-hosted only
- Configurable pipeline autoscaling ceiling — operators can now set the maximum replica count for pipeline autoscaling, giving tighter control over how far a busy pipeline scales out on your cluster. (2.70.2)
- Access: set the
MONAD_HPA_MAX_REPLICASoperator environment variable in your Helm values (default 10). See the Platform Architecture guide.
- Access: set the
- New self-managed deployment guides — new Platform Architecture and Troubleshooting guides for running Monad in your own cluster. Platform Architecture → · Troubleshooting → (2.70.1)
New connectors
- Microsoft Sentinel v2 (output) — a rebuilt Sentinel output connector for forwarding records into Microsoft Sentinel. Docs → (2.70.1)
Fixes
- Multicursor input backfill start time — inputs that use multicursor now return the correct backfill start time (the configured backfill time, or the current time when none is set) instead of an incorrect value. (2.70.3)
- Connections scoped to your organization — getting, updating, and deleting a connection is now correctly scoped to your organization, preventing cross-organization access. (2.70.1)
- Role updates respect the privilege floor — updating a role now enforces the same minimum-privilege rules as creating one, so a role can't be edited to exceed its allowed privileges. (2.70.1)
- Correct landing page after login — post-login redirect now only remembers real navigation destinations, so you're returned to the page you intended rather than an intermediate one. (2.70.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.70.x release with
helm upgrade. Review the Breaking changes section above before upgrading;
when it says "None," the upgrade is drop-in.