Skip to main content

Version 1.17.3

Release Date: July 25, 2026 Release Type: Release Candidate

This was a Release Candidate published to the staging channel; its content was validated and is included in 1.18.0, the first release on the single product version line. The headline of this release is resilient monitoring — automatic Elasticsearch ↔ PostgreSQL failover — together with per-flow log retention, a "No Payload" logging level and side-effect-free Flow Simulation.

Backend Server​

New Features​

  • Automatic monitoring failover between Elasticsearch and PostgreSQL: When Elasticsearch is the monitoring store and becomes unreachable or unable to accept writes, message-monitoring records automatically fail over to PostgreSQL and fail back on recovery, so no monitoring data is lost during an Elasticsearch outage. It detects both connectivity loss and write blocks such as a full disk, a red cluster, or rejected writes. Opt-in.
  • Side-effect-free Flow Simulation: Dry-run and mock simulations are now guaranteed not to touch external systems or pollute monitoring — they no longer write files, upload over FTP/SFTP, send e-mail, produce to Kafka/JMS/Solace, call cloud services, invoke RFC/OFTP2/WebDAV/MCP or external databases, and create no monitoring, attachment or trace records. Live Test still runs for real and is recorded, exactly as before.
  • Per-flow log retention and longer default: Log retention can be configured per flow, so a flow can keep its logs longer or shorter than the global default. The default log retention has been raised from 5 to 14 days.
  • "No Payload" logging level: A new logging level records message counts and success/failure without storing payload bodies on success, while still capturing payloads on error, reducing stored data volume and helping with data-privacy requirements.

Frontend Server​

New Features​

  • Flow simulation with a reusable mock library: Run a simulation before deploying a flow, watch step-by-step results stream in, keep a history of past runs, and save reusable mock responses to re-apply without retyping them.
  • Per-flow log retention, historical counts and longer default: Set a custom retention window for individual flows; report successful and error message counts per flow over any date range even after logs are cleaned up; and the default retention is now 14 days instead of 5.
  • Resilient, timezone-correct monitoring: If Elasticsearch becomes unavailable, monitoring automatically reads from the database and switches back on recovery, re-syncing the missed window. The time-range filter interprets dates in your configured business timezone and honors an explicit offset, and suppressed per-step payloads stay hidden in Show Full Log.

Frontend Web​

New Features​

  • Per-flow log retention: A new Flow Retention page in Database Management sets log-retention rules for individual flows, with clear hints and truncation warnings.
  • Clearer, more resilient monitoring: Loading spinners while payloads and full logs load, auto-focus on the failed connector in Show Full Log, refresh that recomputes the selected time range, an interface column and a MIP Message ID column for XI flow endpoints, and restored Sync Jobs and Component Health with a disk-usage column and per-node rows.
  • "No Payload" log level on the Endpoints selector.

Health Check​

New Features​

  • External system-health API: External systems and monitoring tools can pull a single consolidated MIP system-health snapshot over a secured endpoint — overall severity, the status of each component and node, current resource usage and detected anomalies. Access works with either an API token or a username and password, and the response clearly lists any section that could not be read instead of silently omitting it.
  • Per-component health overview: A new overview reports the live state of every MIP component — healthy, degraded, recovering, unhealthy or unknown — with its response time and check interval, broken out for each backend instance, each search-cluster node and each database instance, flagging high disk usage as a warning before it becomes an outage.

This is a Release Candidate (pre-release); its validated content ships in 1.18.0. Previous: 1.17.2