Skip to main content

NG 2.16.16

🗓️ ⏱️ 6 min read

Overview​

vuSmartMaps™ NG 2.16.16 introduces new monitoring capabilities along with enhancements across workflow monitoring, network monitoring, Syslog collection, and platform security. This release expands observability coverage, improves visibility into application and infrastructure performance, strengthens security controls, and enhances monitoring of network links and supported environments. The release also addresses an issue related to inactive user records and user-count consistency in User Management.

New O11ySource​

The following new O11ySources are introduced in this release:

O11ySource: Temporal Monitoring​

Introduced a new O11ySource for monitoring Temporal workflow execution, task queue health, worker performance, service latency, and failure rates. The O11ySource provides visibility into the operational behavior of Temporal workflows and the services responsible for processing workflow tasks.

This monitoring helps identify workflow execution issues and service disruptions that can affect dependent applications and services, enabling users to track Temporal workflow reliability and investigate execution-related conditions from vuSmartMaps™.

  • CCBD-4860: New O11ySource – Temporal Monitoring

O11ySource: Jenkins Monitoring​

Introduced a new O11ySource for collecting real-time health, performance, and operational metrics from Jenkins through the Jenkins REST API. The O11ySource monitors job status, build results, node health, executor utilization, queue state, and plugin inventory.

This extends observability coverage to Jenkins environments and provides centralized visibility into build activity and Jenkins resource utilization. Users can use the collected information to monitor Jenkins operational health and identify conditions affecting build and CI/CD workflows.

  • CCBD-4873: New O11ySource – Jenkins Monitoring

O11ySource: MinIO Monitoring​

Introduced a new O11ySource for monitoring MinIO object storage environments, providing centralized visibility into storage capacity, performance, node health, bucket-level usage, request errors, and latency.

The new O11ySource helps identify capacity exhaustion, request latency or throughput degradation, node and disk failures, and data distribution issues. It also provides dashboards and alerts to support proactive capacity planning, performance analysis, and faster identification of storage-related issues.

  • CCBD-3866: New O11ySource – MinIO Monitoring

O11ySource: IBM DB2 Database Monitoring​

Introduced a new O11ySource for collecting, processing, and visualizing IBM DB2 metrics and logs, providing visibility into database performance, health, and resource utilization. The O11ySource supports monitoring of database instance status, connection usage, locks, query execution times, buffer pool efficiency, sort operations, transaction throughput, CPU, memory, I/O, tablespace usage, and log-space consumption.

The monitoring capability helps users identify performance bottlenecks, resource constraints, lock waits, deadlocks, and long-running transactions. It also provides visibility into database availability, DB2 error logs and audit events, critical alert conditions, and historical performance trends, supporting proactive monitoring and investigation of IBM DB2 environments.

  • CCBD-3798: New O11ySource – IBM DB2 Database

Enhancements​

O11ySource: Syslog TLS Support Enhancement​

Enhanced the Syslog O11ySource to extend listener protocol support for Syslog data collection. The updated O11ySource supports UDP, TCP, and TLS, allowing Syslog data to be received using the listener protocol required by the source environment.

The Syslog workflow has also been updated so that the corresponding user inputs and deployment parameters support the available listener protocols. This provides greater flexibility for collecting Syslog data from environments that require UDP, TCP, or secure TLS-based communication.

  • CCBD-5767: Syslog O11ySource with TLS Support

O11ySource: FortiGate Firewall SLA Monitoring – SD-WAN and Monitored Link Enhancement​

Enhanced FortiGate Firewall SLA Monitoring by adding the required SNMP OIDs for SD-WAN Links and Monitored Links. The monitoring capability collects link-level information including link name, interface status, latency, jitter, packet transmission, packet reception, and packet loss.

The enhancement enables SLA metrics for both SD-WAN Links and Monitored Links to be collected and exposed through the configured SNMP OIDs. This provides broader visibility into FortiGate link status and performance and helps users monitor conditions that can affect network connectivity and service quality.

  • CCBD-5754: FortiGate Firewall SLA Monitoring – Add SD-WAN and Monitored Link OIDs

Strict CORS Origin Policy Enhancement​

Enhanced the platform's CORS (Cross-Origin Resource Sharing) configuration to enforce stricter origin validation. Previously, the CORS configuration could allow overly permissive access when wildcard (*) or null values were used in the Access-Control-Allow-Origin response header, increasing the possibility of unauthorized domains interacting with application resources.

The updated CORS policy restricts access to explicitly trusted and authorized domains by removing wildcard and null origin values. The policy also ensures that only the required HTTP methods, headers, and credential access are permitted, strengthening protection against unauthorized cross-origin access.

  • CCBD-5399: Enforce a Strict CORS Origin Policy at the Traefik Ingress

O11ySource: Log Collector – OTel Ingestion Enhancement​

Enhanced the Log Collector O11ySource by adding OpenTelemetry (OTel) Collector as an additional ingestion method for log collection. Users can select the required ingestion method based on the source environment, enabling logs to be collected through the existing Log Agent workflow or through an OTel Collector endpoint.

When OTel Collector is selected, logs are received through the OTel ingestion path and routed for processing within the existing log collection workflow. This provides greater flexibility for environments where the existing Log Agent-based ingestion method cannot be used and enables log data to be collected through an OpenTelemetry-based integration.

  • CCBD-5746: Add OTel Collector as an Ingestion Method for the Log Collector O11ySource

Bug Fixes​

User Login Details Dashboard Inactive User and User Count Fix​

Resolved an issue in the User Login Details dashboard where inactive user records could continue to be displayed after users were no longer active or had been removed from the corresponding LDAP source. The issue also resulted in an inconsistency between the total user count displayed across the User Management pages and the records available through pagination.

The user information displayed in User Management has been corrected so that inactive or disabled users are handled consistently and the displayed user count aligns with the corresponding user records. This improves the accuracy and consistency of user information displayed after LDAP user changes are synchronized.

  • VUQA-7128 & NCS-2652: User Login Details Dashboard Showing Inactive Users & User Count Mismatch in User Management

Summary​

With vuSmartMaps™ NG 2.16.16, the platform continues to expand observability coverage and improve the security and reliability of monitoring across supported environments. The release introduces broader monitoring capabilities, enhances network and log monitoring workflows, and strengthens platform security and data consistency. We look forward to building on these improvements in upcoming releases, with continued focus on usability, reliability, security, and broader observability coverage.