We are excited to officially announce the release of Diagnostics 3.2.0
This release marks a major step forward in expanding monitoring visibility, simplifying architecture, and providing smooth, resilient upgrades—particularly for customers managing Splunk 10+ migrations.
Streamlined Licensing Architecture: Moving to Collector-Centric Verification
In earlier builds, administrators were required to install and maintain separate license files across both the track and archiver components in SW. Version 3.2.0 replaces this multi-point model with a centralized licensing engine built directly into the Diagnostics Collector.
Enhancements and fixes
Diagnostics 3.2 includes a number of improvements across the platform:
- Shifted license installation from the GE Smallworld (SW) component to the Diagnostics Collector, centralizing license management into a single point of verification.
- Deprecated and removed the legacy
diagnostics_collector.rpminstaller. - Introduced the Unique Value Allocators (UVAs) dashboard.
- Enabled running SW Monitor concurrently with Datastore Monitor, with added support for generating all monitor configuration XMLs.
- Added “Explain This View” context-help manuals across React dashboards and the Alerts Configuration view.
- Updated the Diagnostics Upgrade Manual with mandatory SSL certificate validation checks for Splunk 10+ KV store upgrades.
- Resolved a token-forwarding bug on Application Details drilldowns.
- Fixed trail chart rendering issues on the SWMFS List dashboard.
- Reverted to legacy APIs when querying frozen files to preserve compatibility with CST 4.2.
- Updated the
swmfs_test 23output parser to handle variations in the “elapsed time” line across older CST versions. - Prevented unfiltered search results from leaking into result sets within the
diagnostics_entity_searchmacro.
For a detailed overview of all the changes, please check our Release Notes.
If you’d like help switching your Collectors to Docker or upgrading from an older release, our team is ready to support you.
Diagnostics 3: Bringing insight out

Leave A Comment