We’re excited to announce that io.Connect Desktop 10.1 is here. It introduces major observability capabilities through io.Insights, group visibility operations in the default platform mode, a more flexible User-Agent configuration, and gives control over username case sensitivity in io.Connect Gateway. It also upgrades the platform to Electron 40.8.3, Chromium 144.0.7559.236, and Node.js 24.14.0.
io.Insights – Traces, Metrics, Logs
The biggest addition in 10.1 is the improved io.Insights implementation. io.Connect Desktop now publishes traces and logs, and also supports custom metrics, enabling observability for both the platform and interop-enabled apps. Few
- Trace instrumentation has been added across the platform and the
@interopio/desktoplibrary, making it easier to observe platform operations and API usage. - Insights API is now available with the
@interopio/otelpackage providing support for publishing OpenTelemetry metrics, traces, and logs from your apps. - Custom metrics like
custom_counter,custom_gauge,custom_histogram,custom observable_counterand a few more were added - The platform configuration under the
otelkey has been extended substantially, and the available settings have been extracted into a dedicatedotel.jsonschema.
There’s much more here:
Breaking change to note
For io.Insights, the defaultMetricsEnabled property under otel.metrics has been renamed to platformMetricsEnabled.
Groups Visibility Operations in the Default Platform Mode
If you’re using the default platform mode, group visibility operations are now supported there as well. You can hide and show groups programmatically with myGroup.hide() and myGroup.show(true) without needing advanced mode.
Details here:
- Window Management > JavaScript
User Agent Configuration
The userAgent property is now more flexible. Besides accepting a plain string, it can also take an object that lets you choose between a clean Chromium user agent or a fully custom one, and optionally append a suffix. This can be configured globally in system.json or per app in the app definition.
This is useful when you need tighter control over how requests identify themselves to upstream services, while still avoiding the default Electron token when needed.
Details here:
- System configuration > Window Settings > User Agent
- Application configuration > User Agent
io.Connect Gateway Username Case Sensitivity
By default, io.Connect Gateway treats usernames as case-insensitive.. In 10.1, you can now change that behavior by setting usernameCaseSensitive to true in the gateway authentication configuration.
Details here:
- System configuration > io.Connect Gateway > Username Case Sensitivity
Full changelog: