Skip to main content

NG 3.2.3

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

Overview​

The vuSmartMapsβ„’ NG 3.2.3 patch release continues to build out ingestion and integration options for O11ySources, adding an OTel Collector-based ingestion path for Log Collector and Custom Token Authentication support across ITSM and WhatsApp alerting integrations. This release also introduces Server-role TLS certificate support, used first by a revamped Syslog O11ySource with UDP, TCP and TLS listeners, and ships a round of Telegraf service-routing and deployment-template fixes that resolve shared-module ambiguity and a ConfigMap size-limit regression.

Beyond these new capabilities, 3.2.3 addresses issues across alerting (Alert Analysis dashboard queries, hyperscale and threshold-based alert conditions, and WhatsApp channel template handling), several O11ySource dashboards and configuration pages (Radware, FortiGate, SPV, RUM/MRUM, Disk Usage, and more), and platform reliability (PostgreSQL read-after-write consistency behind pgpool, Kafka materialized-view handling, and report generation recovery after lost database connections).

Log Ingestion & ITSM Integration Enhancements​

NG 3.2.3 adds a new, agentless method for Log Collector sources to deliver logs, and extends Custom Token Authentication β€” already used by ITSM integrations β€” to the WhatsApp alerting channel, alongside automatic Jira ticket status transitions driven by the alarm lifecycle.

Log Collector: OTel Collector Ingestion Method​

OTel Collector as an Alternative Log Ingestion Method​

Log Collector sources can now send their logs to VuNet's OTel Collector using OTLP, as an alternative to the existing Log Agent method (vulogagent/logbeat), which requires installing an agent on the host. This is a per-source choice, so sources that keep using Log Agent are unaffected. When OTel Collector is selected, Cairo deploys a dedicated OTel Collector container for the source in Kubernetes, the same way it already deploys the traces and RUM collectors, backed by a new deployment template, a VUGENLOG_INSTANCES environment variable so replicas split configuration correctly, and a corresponding image-sync mapping. A Kafka topic-naming bug that had sent OTel-ingested logs to a topic no ClickHouse table actually consumed from was also fixed, along with an is_managed_by_omniagent check that could incorrectly route an OTel-mode source's host down the OmniAgent push path.

CCBD-5746: Log Collector β€” add OTel Collector as a log ingestion method (cairo, vublock-store, hanoi)

ITSM & Alerting Channel Integrations​

Custom Token Authentication for ITSM Integrations​

Added Custom Token Authentication to the Go alert engine, bringing it to parity with the existing Python implementation. The new auth type logs in to a separate authorization server, reads the token from the response, caches it in memory until expiry (refreshing a minute early), and clears the cached token on a 401/403 response. This release also brings the custom ITSM flow in Go in line with Python in several places that had drifted: configured HTTP methods are now honored, a 404 on ticket lookup now falls back to a search by summary instead of always creating a duplicate ticket, custom headers are sent as headers rather than merged into the body, and proxy settings (scoped to auth, ITSM, or both) are now respected.

CCBD-5433: Custom Token Authentication support for ITSM integrations (rosario)

Custom Token Authentication in the WhatsApp Channel​

Custom Token Authentication is now a selectable authentication type for the WhatsApp channel's Custom API type, reusing the Custom Token Auth engine already used by ITSM. A new optional token_expiry.expires_at setting supports gateways whose login response has no expiry field of its own. The shared cached-token handling was also hardened: a 401/403 now clears the cached token so the next call logs in again, a cached token is treated as expired 60 seconds early, and saving the WhatsApp or ITSM preference now deletes the cached token so a changed secret, URL, or header takes effect immediately rather than after the old token expires.

CCBD-5918: Support Custom Token Authentication in the WhatsApp channel (cairo)

Jira Ticket Status Transitions on the Alarm Lifecycle​

When an alarm creates, updates, or clears a ticket, the linked Jira ticket now also changes status, using the Jira transitions API β€” previously the ticket remained in the β€œTo Do” status even after the alarm was cleared, even after the alarm cleared. The target status for each action is configurable under transition_config (with sensible VUNETTRACK defaults: update β†’ In Progress, close β†’ Completed), and the whole behavior can be turned off with a single setting. A failed status change is only logged; the underlying ticket creation, update, or close still succeeds.

VUQA-7200: Move the Jira ticket to the configured status on alarm create, update and clear (cairo)

Server-Role TLS Certificate Support​

This release adds Server-role TLS credentials across the platform, alongside the existing Client-role credentials, so O11ySources that terminate incoming TLS connections β€” rather than only call out over TLS β€” are now supported end to end.

TLS Certificate/Key Support for Server-Role Credentials​

Added role-aware TLS certificate and private-key handling across Cairo (validation, compatibility filtering, and runtime file resolution/materialization) and Kolar (a Client/Server role selector and role-specific certificate and key slots in the credential UI), including CA support for mutual TLS. Legacy credentials with no role set are preserved as Client-role credentials, so existing configurations are unaffected.

CCBD-5765, CCBD-5766: Add Server-role TLS certificate/key support with role-aware validation and resolution (cairo, kolar)

Syslog O11ySource with TLS Support​

Revamped the Syslog O11ySource onboarding and configuration experience to add TLS alongside the existing UDP and TCP listeners (UDP/TCP on port 5514, TLS on port 6514), support for RFC5424, RFC3164, and common Cisco Syslog formats, and custom Grok patterns shared across all configured listeners. TLS listeners require a server-role tls_certificate_bundle credential. Dashboards were updated to use a normalized Syslog view with new Location, Environment, and Server Name filters, and Kafka partition distribution and Syslog metric processing were improved.

CCBD-5767: Syslog O11ySource with TLS Support (vublock-store)

Telegraf Service Routing & Deployment Fixes​

Shared Telegraf Module Routing Fix​

Fixed Telegraf routing so that when a module (for example, exec) belongs to more than one cluster-config group, the source's own deployment template is used to select exactly one matching service, with an explicit error if the match is missing or ambiguous, instead of silently taking the first match in JSON order. The NetFlow O11ySource was also pointed at the unified telegraf_global_receiver.yaml template, and Hanoi's release/3.2 cluster config now identifies the deployment template filename for each existing Telegraf group.

CCBD-5928: Fix Telegraf service routing for shared modules (cairo, hanoi, vublock-store)

Telegraf ConfigMap Size-Limit Regression Fix​

Restored startup fetching of configuration from MinIO for every Telegraf deployment with settings, independently of credential delivery mode. Without this fix, Telegraf deployments without file-delivery credentials fell back to ConfigMaps on release/3.2, reintroducing Kubernetes' 1 MiB size limit for an individual config file.

CCBD-5924: Fix Telegraf ConfigMap size limit regression (vuLauncher)

Hanoi Template Updates for Syslog TLS​

Exposed the Syslog TLS receiver on TCP port 6514, moved the existing plain TCP listener to port 5514 using hostPort while retaining UDP on 5514, and allowed receiver volumes to use a Kubernetes Secret when a SecretName is supplied, while retaining ConfigMap volumes for other entries.

CCBD-5909: Update Hanoi release/3.2 templates (hanoi)

Enhancements​

Platform / Deployment Enhancements​

LiteLLM and VectorServe Backport​

Backported the LiteLLM service and VectorServe (including the DM_MCP app code for data-model discovery) to release/3.2, together with supporting vserve memory, worker-count, and config.yaml changes needed to run them on this release line.

CCBD-5598, CCBD-6064: Backport LiteLLM and VectorServe to release/3.2 (hanoi, muscat, perth, VectorServe)

Bundle & Version Management​

Added a new only-ML bundle type (dropping vuKube), stamped NG_VSMAPS_VERSION into vunodes at bundle time, and fixed the hotfix bundle type and manifest.json release file handling.

CCBD-6082, CCBD-5808, CCBD-6250: Bundle type, version stamping and release manifest changes (hanoi)

MRUM / BRUM Enhancements​

Delivered a set of MRUM enhancements for release 3.2, added Session Replay and Trace Map dashboards for brum_v2, and updated the Kubernetes role bindings used by the BRUM and MRUM collector pods.

CCBD-6105, CCBD-6239, CCBD-6100: MRUM/BRUM dashboard and role-binding updates (vublock-store, hanoi)

FortiGate and Palo Alto O11ySource Enhancements​

Ported the complete Palo Alto package from develop to release/3.2, and added SD-WAN and Monitored Link OIDs to FortiGate Firewall SLA Monitoring.

CCBD-5794, CCBD-6314: Palo Alto package port and FortiGate SD-WAN/link OID support (vublock-store, cairo)

Kafka Consumer Message Metadata​

Added Kafka message metadata to the kafka_consumer input plugin.

CCBD-6330: Add Kafka message metadata to kafka_consumer input plugin (helsinki)

Other Platform Changes​

The release also includes: Teams webhook and OmniAgent-enable documentation updates, a systemd-managed single health binary for vuHealth, use of an App token for private Go module access, and removal of the unused Temporal services entry from vuLauncher's config.yaml.

CCBD-6107: Use App token for private Go modules (helsinki)

O11ySource Configuration​

Hyperscale & Postgres O11ySource Metadata Normalization​

Normalized hyperscale O11ySource metadata, fixed Postgres O11ySource repackaging (a missing targets_field/target_identifier_field combination), and corrected the URL validation regex used by the HTTP Poller O11ySource.

CCBD-6068, CCBD-6099, CCBD-6087: O11ySource metadata and validation fixes (vublock-store)

Updated Get Started Here (GSH) configuration, alert definitions, documentation links, and O11ySource fields.

NCS-2718: Update GSH configuration, alerts, documentation links and O11ySource fields (vublock-store)

Credential Handling Fix for O11ySources​

Fixed an issue where credential values were generated as null for O11ySources.

CCBD-5899: O11ySources β€” credential values generated as null (kolar)

Bug Fixes​

Alerting Bug Fixes​

Alert Analysis Dashboard Query & Upgrade Fixes​

Fixed two panels in the Alert Analysis dashboard that queried incorrect data, and ensured the dashboard is overwritten β€” rather than skipped β€” during upgrade, so the fix actually reaches environments that are upgraded from an earlier version.

VUQA-7254: Fix incorrect Alert Analysis dashboard queries and ensure the dashboard is overwritten on upgrade

Alert Summary Drill-Down O11ySource Filter​

Fixed the Alert Summary drill-down so that it filters with respect to the correct O11ySource instead of returning unfiltered results.

VUQA-7231: Fix Alert Summary drill-down O11ySource filtering

Hyperscale and Threshold-Based Alert Condition Fixes​

Fixed hyperscale alert scripts that always fired, never fired, or raised errors; added a missing check for None values to the EIGRP High RTO alert; and fixed always-firing alert conditions on the Nginx and Tomcat O11ySources.

CCBD-6226, CCBD-6225: Fix hyperscale, EIGRP, Nginx and Tomcat alert condition bugs (vublock-store)

WhatsApp Alert Channel Template Handling​

Fixed the WhatsApp alert channel being disabled when a UI-saved alert rule had no template specified.

NCS-2696: Fix WhatsApp alert channel disabled with no template specified for UI-saved rules (cairo)

Alert Console UI Migration Fixes​

Fixed Alert Console UI migration issues that carried over from an earlier change.

CCBD-2215: Alert Console UI migration fixes (cairo)

O11ySource Bug Fixes​

Dashboard Field & Metric Fixes​

Fixed O11ySource dashboards that displayed raw argMax() column names because field overrides still referenced anyLast(); fixed the Disk Usage panel showing incorrect values due to an invalid metric configured in the Override section; and updated the Trace ID data links in the Transaction Analytics dashboard.

VUQA-7241, VUQA-7237, VUQA-7240: Dashboard field, metric and data-link fixes (vublock-store)

Dashboard Filter & Navigation Fixes​

Fixed a Radware Load Balancer dashboard filter mismatch and its GSH port configuration; fixed O11ySource landing pages redirecting to the old Alert Console URL from the Active Alerts panel; fixed clicking the VuNet logo resetting the user's configured home page; and fixed axis-label text measurement in the theme font so chart labels are no longer clipped.

VUQA-7223, VUQA-7202, VUQA-7222, VUQA-7230: Dashboard filter, navigation and axis-label fixes (vublock-store, nairobi)

Agent & Collector Fixes​

Fixed VuAppAgent failing to initialize due to missing package configuration and an empty lib directory; fixed the Traces Collector pod getting stuck in Container Creating state; replaced the inventory Kafka reader when partitions have no consumer; fixed the pgpool split-brain-prevention sidecar pulling an unbundled kubectl image; updated the MRUM deployment template's Traefik API version; and updated role bindings for the BRUM and MRUM collector pods.

VUQA-7249, VUQA-7226, VUQA-7208, CCBD-6180, CCBD-6258, CCBD-6100: Agent and collector reliability fixes (vuAppAgent, vuLauncher, kyoto, hanoi)

Configuration & Access Fixes​

Fixed the SPV Config page not loading; fixed a service monitoring issue at the source level; prevented in-form VuButtons from submitting forms unintentionally; fixed the SQL query editor autocomplete returning no suggestions; fixed outdated documentation links on the O11ySource Get Started pages; and updated the license and user-count checks to count only enabled users.

VUQA-7121, VUQA-7205, VUQA-7201, VUQA-7195, VUQA-7180, VUQA-7210/VUQA-7128: Configuration, UI and licensing fixes (vublock-store, kolar, vu_auth_provider, cairo)

Platform & Database Bug Fixes​

PostgreSQL Read-After-Write Consistency Behind Pgpool​

Fixed PostgreSQL read-after-write consistency issues occurring behind pgpool, ported across Cairo, vu_auth_provider, and the datamodel-create path.

VUQA-7178: Fix PostgreSQL read-after-write consistency issues behind pgpool (cairo, vu_auth_provider, denver)

Materialized View and Kafka Master-Topic Distribution Fixes​

Fixed a materialized view (MV) query handling bug that caused an IndexError on repeated creation calls against the same object, ensured every custom MV query is validated, and improved Kafka master-topic distribution so unique topics are balanced evenly across the minimum required number of masters instead of filling one master before moving to the next.

CCBD-5903, CCBD-5894: Fix materialized view query handling and Kafka master-topic distribution (vu_auth_provider)

Report Generation Recovery After Lost DB Connections​

Fixed report generation so that it recovers from lost database connections instead of failing outright.

VUQA-6890: Recover report generation from lost DB connections (cairo)

Post-Install Orchestrator Upgrade Fix​

Fixed the vu-post-install-orchestrator service failing to upgrade on NG-3.2.

VUQA-7204: Fix vu-post-install-orchestrator service upgrade failure (vu-postinstall-orchestrator)

Pgpool/Repmgr Failover Hardening​

Hardened Pgpool/repmgr failover handling, tuned PostgreSQL memory settings, and reduced Pgpool logging noise.

DVSO-1193: Harden Pgpool/repmgr failover and tune PostgreSQL memory (hanoi)

Minor Fixes​

Test Cleanup​

Removed a JUnit 3 template test and an unused dependency from otel-class-method.

VUQA-7191: Remove JUnit 3 template test and dependency from otel-class-method (java-otel-sdk-extension)

Summary​

The NG 3.2.3 patch release expands O11ySource integration options with an OTel Collector ingestion path for Log Collector, Custom Token Authentication for both ITSM and WhatsApp channels, automatic Jira ticket status transitions, and Server-role TLS certificate support β€” used first by a revamped Syslog O11ySource. It also includes Telegraf service-routing and deployment-template fixes, platform enhancements spanning LiteLLM/VectorServe backports, bundle and version management, and MRUM/BRUM dashboards, plus bug fixes across alerting, O11ySource dashboards and configuration, and platform database reliability. Together, these updates round out the 3.2 line with safer ingestion options, stronger TLS support, and a more reliable alerting and dashboarding experience.