Release Notes — 2.69

Covers the 2.69 release series. Most recent patch: 2.69.2.

Unless a subsection notes otherwise, changes apply to both Monad SaaS and self-hosted.

New features & improvements

• jq transforms: prevent data dropping — a new opt-in toggle on jq transform nodes keeps records that would otherwise be silently discarded when a jq program returns empty or errors on a record, so a single malformed event no longer drops data from your pipeline. Docs →
  • Access: opt-in — turn on Prevent data dropping in the transform (jq) node's settings.
• 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.
• 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.
• 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.
• Fresher enrichment lookups — the kv-lookup enrichment's lookup cache now refreshes within about one second, so enrichment results reflect updates to your lookup data almost immediately.
• 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.
• Smoother pipeline continuity during restarts — pipelines now ride out routine node restarts and pod rescheduling without interruption, improving reliability during platform maintenance.

New connectors

• Microsoft Sentinel v2 (output) — a rebuilt Sentinel output connector for forwarding records into Microsoft Sentinel. Docs →

Fixes

• Connections scoped to your organization — getting, updating, and deleting a connection is now correctly scoped to your organization, preventing cross-organization access.
• 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.
• Edit stays reachable for shared resources — the Edit action remains available on a resource that has only a share policy, fixing a case where it disappeared.
• 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.

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.