Skip to main content

NG 3.2.2

πŸ—“οΈ ⏱️ 10 min read

Overview​

The vuSmartMapsβ„’ NG 3.2.2 patch release is centered on supporting OmniAgent migration in environments migrated from NG 2.16 to NG 3.2, including Telegraf-based O11ySources. This includes a dedicated Telegraf migration script and a new Advanced Configuration capability for O11ySources that lets supported custom and legacy agent configuration be carried forward safely during migration.

Beyond migration, this release delivers platform and O11ySource configuration enhancements, and addresses issues across O11ySource validation, APM dashboards, tracing, BRUM Session Replay, and other platform areas. Fixes include improved probe recovery after service crashes, support for dynamic HTTP payload capture URL patterns, and ClickHouse readiness checks before database migrations. Additional improvements resolve documentation link issues, restore access to the VQL User Guide, and fix pipeline editor visibility issues in ContextStreams.

OmniAgent Migration (including Telegraf Migration)​

NG 3.2.2 extends platform support for customers migrating from NG 2.16 to NG 3.2 using OmniAgent, including Telegraf-based O11ySources. This release adds a dedicated Telegraf migration script and introduces an Advanced Configuration capability that allows supported custom agent configuration to be preserved during migration, in addition to reliability fixes that improve the migration and post-migration OmniAgent experience.

Telegraf Migration Support (Migration Postjob)​

Added a Telegraf migration upgrade workflow consisting of a new manage_vublock o11ysource reapply vublock-store CLI command and three sequenced post-install upgrade jobs. The workflow creates the required Environment/Application records ahead of O11ySource reimport, reapplies and resaves Telegraf-based O11ySources (omni_dcm and vutelenode agent types) through existing Cairo APIs so they pick up the latest deployment templates and agent images, and removes older Telegraf deployment artifacts from MinIO after backing them up for rollback.

CCBD-5305: Telegraf migration (O11ySources) – migration postjob

Advanced Configuration Framework for O11ySource Components​

Added a generic Advanced Configuration framework for O11ySource components, spanning vublock-store metadata authoring, Cairo validation, ownership enforcement and merging into the generated agent configuration, and an O11ySource UI code editor field with starter content. Three ownership tiers are enforced: standard UI-owned fields, platform-controlled fields, and metadata-approved Advanced Configuration fields. Overrides cannot modify UI- or platform-owned settings.

The primary v1.0 use case is migrating legacy Healthbeat and Logbeat agent configuration to OmniAgent. A migration REST API and Django management command analyze a host's legacy configuration, classify each difference as an accepted Advanced Configuration override or a rejected finding, and provide the result to migration tooling so supported custom configuration is carried forward.

CCBD-5334, CCBD-5379: Introduce Advanced Configuration in the O11ySource UI

Migration Reliability Fixes​

Eventlogbeat Probe Visibility After OmniAgent Migration​

Fixed an issue where the eventlogbeat probe was not displayed in Host Landscape after OmniAgent migration. The probe agent-type filter now includes eventlogbeat.

VUQA-7166: Add eventlogbeat to probes agentType filter

Automatic Windows Service Restart After Crash​

Fixed an issue where the OmniAgent Windows service did not restart automatically after its process crashed. Windows service recovery actions are now configured at install time. Existing installations pick up this policy when omniagent install is rerun or an administrator applies it manually with sc failure.

VUQA-7176: Add automatic service restart after crash on Windows

Windows OmniAgent Package Distribution Fix​

Updated Windows OmniAgent package distribution to use a ZIP archive instead of TAR.GZ. This resolves migration failures on Windows Server 2016, where the tar utility is not available by default.

VUQA-7174: Ship the Windows OmniAgent package as ZIP

Enforce TLS 1.2 for Windows Remote Installation Downloads​

Updated the Windows remote installation download process to enforce TLS 1.2 when downloading the OmniAgent package.

VUQA-7174: Force TLS 1.2 in the Windows remote install download

Preserve Log Collector Configuration During OmniAgent Migration​

Fixed migration of Log Collector sources with multiple independently configured legacy inputs, which could merge inputs or drop custom fields. Migration now keeps each host/category's extra legacy inputs as independent Advanced Configuration entries and preserves root-level custom fields such as doc_type and log_file_path, so each input renders and routes correctly after migration.

VUQA-7179: Preserve independent Log Collector migration inputs

Probe Status and Recovery After OmniAgent Restart​

Fixed an issue where restarting OmniAgent caused the platform to stop and reinstall every probe because each probe reported an empty status on its first heartbeat. OmniAgent now reports each probe's last saved package and configuration status on startup. This also fixes bulk configuration updates waiting behind stale replays, failed package installs getting stuck without retrying, and one agent's configuration status incorrectly updating another agent's record.

VUQA-7189: Report saved probe status on cold start, and fix related package and config status faults

Enhancements​

Platform / Deployment Enhancements​

Accurate Patch Release Version Display​

Enhanced the About page to show the correct vuSmartMaps release version, including the patch number. The NG_VSMAPS_VERSION environment variable now takes precedence when configured, preventing incorrect version numbers caused by automatic increments in the .version file. If it is not set, the existing version retrieval mechanism is used.

CCBD-5808: Support NG_VSMAPS_VERSION env override for release version display

ClickHouse Installation Readiness Check​

Enhanced the ClickHouse Helm chart with a readiness check that makes Helm installation and upgrade operations wait until the ClickHouseInstallation (CHI) resource reaches the Completed state. The check includes least-privilege RBAC permissions and configurable settings, helping prevent deployments from being marked complete before ClickHouse is ready.

CCBD-6020: Add ClickHouse Installation Readiness Check as a Helm Hook

O11ySource Configuration​

Windows Server 2022 Datacenter Azure Edition Support​

Updated the Windows Monitor O11ySource GSH supported operating systems list to include Windows Server 2022 Datacenter: Azure Edition. Validation confirmed OmniAgent with the Healthbeat probe successfully collects and delivers data on Windows Server 2016, 2019, 2022 Standard, and 2022 Datacenter: Azure Edition.

CCBD-5960: Add Windows Server 2022 Datacenter Azure Edition to GSH supported OS list

Kafka Version and Data Format as User Inputs​

Added Kafka Version and Data Format as explicit, user-configurable inputs in the Kafka Data Collector O11ySource, giving users direct control over these parameters instead of relying on fixed defaults. This ports forward an enhancement already available in another release line to the 3.2 line.

CCBD-5732: Add Kafka Version and Data Format as User Inputs in Kafka Data Collector O11ySource

Kafka KRaft Metrics Support (via Jolokia)​

Enhanced the Kafka O11ySource to collect Kafka KRaft-mode metrics through Jolokia, alongside existing Kafka metrics. The package includes new KRaft dashboards and alerts, an updated metrics schema, and a UI option to enable Jolokia-based collection. Existing ZooKeeper-based Kafka monitoring is unaffected. This release also fixes Kafka O11ySource OmniAgent discovery, which was keyed on Instance Name instead of Instance IP, and restores the Advanced Configuration field in the Kafka O11ySource UI.

CCBD-5339, NCS-2694: Collect Kafka KRaft metrics via Jolokia and fix Kafka OmniAgent discovery

Bug Fixes​

O11ySource Bug Fixes​

Hidden Conditional Field Validation Fix​

Fixed O11ySource save validation when a required field is hidden by another field's value. Validation now skips the required check for conditionally hidden fields. Also fixed source field order drifting after repeated edits due to Postgres not preserving field order: the source definition's field order is now authoritative, and existing sources with incorrect order self-heal automatically.

CCBD-5793: Fix O11ySource save validation for hidden fields and source field-order drift

Kafka O11ySource Required Field Validation​

Fixed Kafka O11ySource wizard fields being treated as optional regardless of the selected Package Type. Field configuration now correctly identifies mandatory values for the selected type, while applicable service-specific fields remain optional.

CCBD-5792: Kafka O11ySource wizard shows required fields as optional regardless of Package Type

Correct Supported Operating Systems for IIS O11ySource​

Updated IIS O11ySource GSH configuration to include only supported Windows operating systems, removing Linux and other non-Windows entries from both the supported OS list and packaged agent binaries.

CCBD-5908: Update GSH Supported OS List for IIS O11ySource to retain only Windows-based operating systems

APM / Tracing Bug Fixes​

Smart Frame Label Standardization and Trace Map Span Ordering​

Standardized Smart Frame labels so Transaction page labels align with the Service Catalogue. Trace Map spans at each level are now displayed in chronological timestamp order. Refer to APM Dashboards – Latency Insights and APM Dashboards – Error Insights.

VUQA-7145: Replace β€œRCA” terminology with β€œInsights” and standardize metric labels across APM dashboards
VUQA-7136: Fix Trace Map spans not displayed in chronological timestamp order

Wildcard Support for HTTP Payload Capture URL Matching​

Enhanced HTTP payload capture URL matching to support dynamic URL patterns: {id} matches a variable path segment and * matches trailing segments. This release also fixes Java tracing agent startup on Java 8, excludes application/x-www-form-urlencoded request and response bodies from capture to avoid capturing personal data, and isolates capture failures so one problematic rule does not affect application request handling or other rules.

VUQA-7152: Wildcard support missing in HTTP payload capture URL matching

BRUM Session Replay DOM Desynchronization Fix​

Fixed BRUM Session Replay showing a blank or corrupted page instead of user interactions. Replay now sends event batches one at a time in order and automatically resynchronizes with a fresh snapshot if events are lost. Inline images and web fonts are no longer captured by default because they were a main cause of oversized batches; they can be re-enabled through replayCapture.

VUQA-7137: Fix DOM desynchronization in BRUM Session Replay

Database Upgrade Readiness Bug Fixes​

ClickHouse Readiness Check Before Migrations​

Added a readiness check before database migrations to verify that the default Postgres database and every ClickHouse shard and replica are reachable. If any are unavailable, migration stops immediately with a clear error listing unreachable databases instead of starting and failing partway through.

VUQA-7185: Check DB reachability before running migrations

Other Platform Bug Fixes​

Fixed broken and outdated links from O11ySource Get Started and configuration pages. OmniAgent installation, Traces instrumentation, and MRUM instrumentation links now point to the correct documentation paths.

VUQA-7180: Fix documentation links from the Get Started page and update APM Dashboard documentation

Restored the VQL help links in Data Explorer's search bar, selected-filters row, and Query Form. They now open the VQL User Guide with noopener and noreferrer security attributes.

VUQA-7190: Restore VQL user-guide link

Pipeline Editor Info Tab Visibility Fix​

Fixed a ContextStreams Pipeline Editor layout issue that caused the tabs bar to appear squeezed or collapsed. The page content is now grouped under a single container so the tabs and content render at full size.

VUQA-7193: Fix Pipeline Editor tabs shrinking

Summary​

The NG 3.2.2 patch release supports OmniAgent migration for environments moving from NG 2.16 to NG 3.2. It adds Telegraf migration support and an Advanced Configuration framework that safely preserves supported custom agent configuration, alongside migration reliability fixes. The release also improves platform and O11ySource configuration and addresses issues with field validation, APM dashboard labels and trace ordering, BRUM Session Replay, database migration readiness, documentation access, and ContextStreams pipeline editing. Together, these updates provide a safer migration path and a more consistent, reliable experience for vuSmartMaps users.