Release Notes
Release Notes — 2.74
Covers the 2.74 release series. Most recent patch: 2.74.3.
Unless a subsection notes otherwise, changes apply to both Monad SaaS and self-hosted.
New features & improvements
SaaS & self-hosted
- Monad MCP — edit one pipeline edge without rebuilding the graph — the new
update_pipeline_edgetool changes a single edge's name, conditions, or schema-detection settings in place. Previously an assistant had to resubmit the whole pipeline to touch one edge, and any field it forgot to resend was silently dropped — an omitted condition widened a filtered edge to pass-all, and an omitted schema-detection setting discarded the edge's learned baseline. The tool reads the edge back after the change and reports what actually landed. Docs → (2.74.1) (For teams using the Monad MCP integration.) - Monad MCP — complete pipeline introspection —
get_pipelinenow renders each edge's full condition tree (every rule and its configuration, not just the top-level operator), the component each node points at, node names alongside their IDs, and whether a node overrides its component's configuration. An assistant can now audit, document, or faithfully duplicate a pipeline's routing from the MCP alone. (2.74.1) (For teams using the Monad MCP integration.) - Monad MCP — raw JSON on the pipeline read tools —
get_pipeline,get_pipeline_statusandget_node_statusaccept the samerawoption the type-lookup tools already had, returning the complete API document when the rendered summary omits a field you need. (2.74.1) (For teams using the Monad MCP integration.)- Access: opt-in — pass
raw: trueon the call; the rendered summary remains the default.
- Access: opt-in — pass
- Monad MCP — forgiving type lookups — the
get_input_type,get_output_type,get_transform_type,get_enrichment_typeandget_alert_rule_typetools now accepttype,idortype_idas well as their canonical parameter, and an unknown type ID returns the closest matches from the catalog instead of an unexplained server error. (2.74.1) (For teams using the Monad MCP integration.) - Elasticsearch output — date-based index names — the Index Name field now accepts date tokens, so records can be routed to a daily, monthly, or hourly index (for example
security-logs-{yyyy}-{mm}-{dd}) instead of one ever-growing index. Tokens resolve against the current UTC time when a batch is written. Docs → (2.74.1)- Access: opt-in — add tokens (
{yyyy},{yy},{mm},{dd},{hh},{mi},{ss}) to the output's Index Name; a plain name behaves as before.
- Access: opt-in — add tokens (
Self-hosted only
- Database migrations now run from the API pod — the separate
db-migrationsJob is gone; on upgrade theapipod applies migrations from an init container on the same image, so the schema and the code that needs it are always the same release.partition-manageris now its own component, and oneglobal.monad.natsUrlvalue sets the NATS URL for every component. If your values override anything underdb-migrations, remove it; if you run an external Postgres, make sure themonad-db-appSecret includes theurikey. (2.74.0)
Fixes
- Monad MCP status tools answer "is data flowing?" —
get_node_statusnow shows each node's name and type, records in and out, when it last processed a record, and any records shed unattempted;get_pipeline_status'smetricsfilter works (every value previously returned an error); andsample_node_datanow says plainly that it returns a retained sample rather than proof of live flow, pointing to the status tools for liveness. (2.74.1) - Monad MCP alert and secret guidance corrected — alert-rule severity is now offered as the exact set the platform accepts (the documented
warningwas never valid and always failed), and the tool descriptions and guidelines show the correct way to reference a secret, which previously led to an unexplained server error. (2.74.1) - API: partial updates no longer require re-sending the component type — a
PATCHto an input, output, or enrichment that omitted the unchangedtypefield failed with a 400; the stored type is now used, so a description-only or config-only update works as expected. (2.74.1) - Google Cloud Logs, GKE Audit Logs, and Looker audit logs inputs no longer lose late or backdated entries — the inputs now poll in windows keyed on when Google received each entry rather than its event time, so an entry ingested late is still collected; the Looker input, which had matched no log entries at all, returns logs again. Records arrive a couple of minutes after Google ingests them. Docs → (2.74.1)
- Cisco Meraki Organization Configuration Changes input stays within Meraki's lookback window — a checkpoint older than the 365 days Meraki retains is now clamped forward instead of producing an undefined query, and records without a timestamp no longer fail the run. (2.74.1)
- CrowdStrike Event Stream input resumes correctly after a restart — the stream's application ID is now persisted with the input's state, so a pipeline restart continues the existing feed instead of colliding with it. (2.74.3)
- Lansweeper Vulnerabilities input syncs the full inventory on a schedule — the incremental sync keyed on a global publication date could skip records and never delivered updates to an existing vulnerability; the input now re-lists the full inventory on a Cron schedule you set (required) and drops unchanged records. The former Backfill Start Date setting is removed. Docs → (2.74.1)
- Cloudflare DDoS Attack Analytics input no longer skips attacks — results are now requested in a fixed order and paged on a time-plus-attack-ID key, and each run covers the full lookback window Cloudflare allows rather than a one-hour slice. (2.74.1)
- Snowflake Authentication Logs input no longer misses late-materializing logins — queries now stop short of the latency Snowflake documents for its login-history view, so a login that appears after the checkpoint passed its timestamp is still collected on a later run. After upgrading, an existing input can return no records for up to about three hours while the window catches up; nothing is lost. (2.74.1)
- NetSuite SuiteBilling Audit Logs input pages reliably on long backfills — each run now queries a fixed window, checkpoints after every page, and stays under SuiteQL's 100,000-row result cap, so a long backfill or outage no longer truncates silently and a mid-run failure resumes where it left off. Docs → (2.74.1)
- CrowdStrike Spotlight Vulnerabilities inputs no longer skip same-second updates — the time filter is now inclusive and results are requested in ascending order, so a vulnerability updated in the checkpoint second, or returned out of order within a page, is no longer dropped. (2.74.1)
- Prowler Findings input captures updates and stops dropping findings — the input now keys on when a finding was last updated, so a mute, triage change, or new scan result is delivered rather than only the first sighting, and findings returned out of order within a page are no longer lost. It also polls hourly to keep load off the Prowler API. Docs → (2.74.1)
- Postman Audit Logs input collects every event — Postman returns newest-first by default, which left only one record per fetch; the input now requests ascending order with a date window that includes today. (2.74.1)
- Cloudflare URL Scanner input publishes scans again — the query could loop indefinitely on a full page, keep only one result per page, and exclude the current day; the input now walks scans one day at a time, oldest first. (2.74.1)
- runZero inputs can be created again, and Vulnerabilities is rewritten — configuration type mismatches that blocked creating any runZero input are fixed, and the Vulnerabilities input was rebuilt against live runZero data. (2.74.1)
- Azure Activity Logs input no longer loses late-published or high-volume events — queries now allow for Azure's publish delay and follow every results page, so busy subscriptions are no longer truncated to one page. Docs → (2.74.1)
- Nightfall Posture Events input no longer drops events — requests now specify ascending order and send timestamps as Unix seconds, as Nightfall expects. (2.74.1)
- Splunk Search Results input tracks each saved search separately — a single shared checkpoint let searches on different schedules skip past one another; each saved search now keeps its own. (2.74.1)
- Splunk Notable Events input no longer misses late-indexed notables — the search now bounds and checkpoints on index time rather than event time. Existing inputs see a one-time, bounded re-ingest as the checkpoint shifts. (2.74.1)
- OneLogin Events input no longer skips events while paging — the time filter stays fixed for the whole run and results are sorted by ID, so pages no longer shift underneath the cursor. (2.74.1)
- Idira Audit Events input checkpoints on arrival time — the cursor, filter, and sort now use the server's arrival time, the field Idira returns in chronological order, so late-arriving events are collected reliably. (2.74.1)
- Numeric settings fields can be cleared — emptying a number field in a connector or pipeline form no longer snaps it back to its default value. (2.74.1)
- Full-size jq editor handles very large documents — the expanded editor now uses the same virtualized viewer as JSON views, so large inputs scroll and render correctly instead of freezing. (2.74.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.74.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