Skip to main content

NG 2.16.14

🗓️ ⏱️ 14 min read

Overview​

vuSmartMaps™ NG 2.16.14 introduces new monitoring capabilities, enhancements, and fixes across Observability, Credential Management, ITSM Integration, and Platform Configuration. This release improves Monitoring Coverage, O11ySource Configuration, Alerting Workflows, Data Collection, and Deployment Reliability. It also addresses key issues across Alert Visibility, Dashboard Management, Database Monitoring, and O11ySource Onboarding.

New Features​

Credential File Upload Support​

Introduced credential file upload support to extend credential management for secure authentication and connectivity requirements. This update adds support for TLS Certificate Bundle, GCP Service Account JSON, and OCI Wallet Bundle credentials, allowing the required files to be uploaded and managed directly through vuSmartMaps.

TLS Certificate Bundle credentials support Private CA and mTLS modes, while GCP Service Account JSON supports JSON file upload, and OCI Wallet Bundle supports uploading the required ZIP file. In this release, TLS Certificate Bundle credentials are supported for configuring the MongoDB O11ySource. The GCP Service Account JSON and OCI Wallet Bundle credential definitions are introduced for use with other O11ySources in future releases. This enhancement simplifies file-based credential management and provides a more consistent workflow for configuring secure connections and integrations.

  • CCBD-5364: Credentials – Support for File Upload

New O11ySources​

The following new O11ySources are introduced in this release:

O11ySource: Quarkus Application Monitoring​

Introduced a new O11ySource for monitoring Quarkus-based applications. The O11ySource collects application and runtime metrics covering JVM memory and garbage collection, thread activity, CPU utilization, HTTP server activity, MicroProfile health information, application metrics, database connection pools, and other supported Quarkus runtime indicators.

The collected metrics are made available through the supported vuSmartMaps monitoring workflow, with dashboards and alert rules providing visibility into application health, JVM utilization, HTTP errors, garbage collection behavior, worker queues, and related operational conditions.

  • CCBD-5024: New O11ySource – Quarkus Metrics Monitoring

O11ySource: Apache Karaf Logs and Metrics Monitoring​

Introduced a new O11ySource for Apache Karaf environments to provide combined metrics and log monitoring. The O11ySource collects JVM metrics such as heap and non-heap memory, garbage collection, thread activity, and CPU utilization, along with Karaf-specific information covering bundles, features, HTTP/Jetty activity, and supported Camel route metrics.

Log monitoring includes supported Karaf runtime, audit, OSGi framework, and application logging sources. Dashboards and alert rules provide operational visibility into JVM health, bundle and feature state, authentication activity, memory utilization, garbage collection, HTTP errors, worker activity, and other monitored conditions.

  • CCBD-5026: New O11ySource – Apache Karaf Logs & Metrics Monitoring

O11ySource: IBM webMethods Logs and Metrics Monitoring​

Introduced a new O11ySource for IBM webMethods environments covering Integration Server and API Gateway monitoring. The O11ySource collects service execution, thread pool, connection pool, scheduled task, API Gateway, backend service, JVM, and messaging-related metrics required for monitoring webMethods components.

The O11ySource also supports collection of Integration Server, audit, error, API Gateway, and transaction logs. Dedicated dashboards and alert rules provide visibility into service performance, JVM health, connection usage, API Gateway behavior, backend latency, HTTP responses, transaction failures, and other supported operational conditions.

  • CCBD-5025: New O11ySource – IBM webMethods Logs & Metrics Monitoring

O11ySource: AWS MSK Monitoring​

Introduced a new O11ySource for AWS Managed Streaming for Apache Kafka (AWS MSK). The existing Kafka monitoring workflow is primarily designed for Kafka environments running on virtual machines with direct access to Kafka brokers, while AWS MSK operates as a managed Kafka service within AWS.

This new O11ySource extends Kafka monitoring coverage to AWS MSK environments and enables supported vuSmartMaps monitoring workflows for managed Kafka deployments.

  • NCS-2211: New O11ySource – Kafka Monitoring | AWS MSK

Enhancements​

Alert Analysis Dashboard Drilldown Enhancement​

Enhanced the Alert Analysis workflow to improve navigation from Alert Insights to the Alert Console. The update enables the Alert STAT drilldown in Alert Insights to direct users to the corresponding Alert Console view, providing a more consistent transition from alert summary information to detailed alert investigation.

This enhancement improves the dashboard drilldown experience by connecting alert-level analysis with the detailed alert information available in the Alert Console.

  • CCBD-5270: Alert Analysis Dashboard Drilldown to Alert Console

Custom Token Authentication Support for ITSM Integrations​

Enhanced ITSM integrations by introducing support for configurable Custom Token Authentication. Previously, token-based authentication used a fixed request structure, which limited integrations that required additional or differently structured authentication parameters.

The new Custom Token Authentication option allows the authentication request and token-related configuration to be defined through the ITSM configuration rather than requiring integration-specific code changes. This expands support for ITSM systems that use custom token-generation workflows or require additional authentication parameters.

  • CCBD-5433: Custom Token Authentication Support for ITSM Integrations

WebLogic Pipeline Timestamp Source Zone Update​

Enhanced timestamp handling for WebLogic and applicable vuAppAgent-based O11ySources by updating the pipeline datetime plugin source zone to UTC where required. The update ensures that timestamp processing remains consistent across environments and prevents discrepancies caused by differences in source timezone configuration.

This change improves alignment between collected data timestamps, ClickHouse processing, dashboard time ranges, and the time displayed through supported monitoring workflows.

  • CCBD-4972: Update Pipeline Datetime Plugin Source Zone to UTC for WebLogic

O11ySource: SAP ASE SSL Connection Support​

Enhanced the SAP ASE O11ySource to support SSL-based database connectivity. This update enables monitoring to operate in environments where SAP ASE database connections require SSL and addresses connectivity requirements introduced when secured server certificates are used.

The enhancement improves support for secured SAP ASE deployments and helps maintain monitoring and data collection when database communication is configured through SSL.

  • NCS-2544: Add SSL Connection Support for SAP ASE O11ySource

O11ySource: Kong Konnect Hybrid Mode Data Plane Monitoring Requirements​

Enhanced the Kong Konnect Hybrid Mode monitoring setup by updating the GSH requirements for Kong Data Plane monitoring. The update includes the network and access information required for the vuSmartMaps monitoring agent to reach the Kong Data Plane metrics endpoint in environments where access is controlled through a WAF or reverse proxy.

This ensures that the required monitoring traffic can be identified and allowed during deployment, improving setup consistency for Kong Konnect Hybrid Mode environments.

  • CCBD-5236: Update GSH for Kong Konnect Hybrid Mode Data Plane Monitoring Requirements

O11ySource: Keycloak Realm Metrics Monitoring​

Enhanced the Keycloak O11ySource to support collection of realm-level metrics for supported Keycloak environments. The update extends existing monitoring beyond authentication, login, and JVM information by adding realm-level usage and activity visibility.

Required Telegraf configuration, pipeline mapping, and dashboard updates have also been included so that the newly collected realm metrics are available through the Keycloak monitoring workflow. The enhancement provides broader visibility into realm activity while retaining the existing authentication and JVM monitoring capabilities.

  • CCBD-5290: Keycloak O11ySource Enhancement to Collect Realm Metrics

O11ySource: SQL Data Collector Custom Query Handling Enhancement​

Enhanced SQL Data Collector query handling for customer-defined SQL queries. The update improves custom-query parsing and execution behavior so that supported queries can be onboarded without causing the SQL Data Collector pod to restart or enter an unsuccessful execution state.

This enhancement improves reliability when configuring custom SQL queries and reduces data collection interruptions caused by query parsing behavior.

  • NCS-2360: SQL Data Collector Custom Query Handling Enhancement

O11ySource: Kafka KRaft Metrics Monitoring​

Enhanced the Kafka O11ySource to collect Kafka KRaft-specific metrics through Jolokia. The existing Kafka monitoring capability has been extended to support Kafka deployments operating in KRaft mode while retaining the existing Kafka metric collection workflow.

The update includes the required configuration, pipeline, and package-related changes for KRaft metric collection and supports end-to-end monitoring of Kafka KRaft environments through vuSmartMaps.

  • CCBD-5339: Enhancement to Collect Kafka KRaft Metrics in Kafka O11ySource

O11ySource: Log Collector Windows Logbeat Configuration Path Enhancement​

Enhanced the Log Collector O11ySource configuration for Windows Logbeat Agent deployments by updating path references used in the default configuration files. The earlier configuration contained path formats that were not aligned with Windows deployment requirements and could require manual changes before the agent could start successfully.

This update provides Windows-compatible configuration references so that the Logbeat Agent can load the required modules and inputs correctly during startup, reducing manual configuration during deployment.

  • CCBD-5415: Log Collector O11ySource – Windows Logbeat Agent Configuration Path Update

O11ySource: MySQL DBName, Pipeline, and Buffer Pool Enhancements​

Enhanced the MySQL O11ySource with DBName field support and updates to the InnoDB performance query and related pipeline processing. The pipeline manipulation logic has been updated to support the revised query fields and calculations required by MySQL monitoring.

The Buffer Pool Inefficiency panel calculation has also been updated to address scenarios where an infinite or incorrect value could be displayed. The revised calculation handles zero-value read requests without producing division-by-zero or invalid results, improving the accuracy of Buffer Pool Inefficiency information across supported MySQL environments.

  • CCBD-5362: MySQL O11ySource – DBName Field Support, Pipeline Manipulation Update, and Buffer Pool Inefficiency Panel Enhancement

O11ySource: Device Availability Collection Enhancement​

Enhanced the Device Availability O11ySource configuration to improve monitoring behavior when a large number of devices are collected at the same interval. Additional collection timing and ping configuration parameters have been introduced to distribute monitoring activity and provide additional tolerance for temporary network packet loss.

This update reduces false DOWN events that could occur when multiple monitoring requests were initiated simultaneously or when a single transient packet loss was encountered. The enhancement improves the reliability of device availability status reporting without changing the actual availability monitoring workflow.

  • CCBD-5521: Device Availability O11ySource Enhancement – Additional Configuration

O11ySource: PostgreSQL Configuration Reference Enhancement​

Enhanced the PostgreSQL O11ySource configuration by removing duplicate field name references that could cause O11ySource enablement to fail in vuBlock. Certain PostgreSQL field names were referenced multiple times in the ClickHouse configuration, resulting in configuration conflicts during enablement.

The update removes the duplicate references and aligns the related configuration so that the PostgreSQL O11ySource can be enabled successfully.

  • CCBD-5541: PostgreSQL O11ySource – Remove Duplicate Field Name References

O11ySource: SNMP Trap Deployment Template and Jinja Template Updates​

Enhanced the SNMP Trap O11ySource deployment configuration by updating the deployment template and Jinja template required for the supported deployment workflow. The update aligns the required network and runtime configuration used by the SNMP Trap receiver and includes the corresponding GSH-related changes.

These changes improve deployment consistency and ensure that the SNMP Trap O11ySource uses the expected configuration when receiving and processing trap information.

  • CCBD-5553: SNMP Trap – Deployment Template and Jinja Template Updates

Bug Fixes​

ITSM Dynamic Token Numeric Username Fix​

Resolved an issue where Dynamic Token authentication in Custom ITSM integrations did not accept usernames containing only numeric characters. The configured username could be rejected during validation even though numeric-only usernames were valid for the target ITSM system.

This fix updates the validation behavior so that supported numeric-only usernames can be configured and used successfully with Dynamic Token authentication.

  • VUQA-6904: ITSM – Custom ITSM Dynamic Token Authentication Does Not Accept Numeric-Only Username

Resolved an issue where triggered alerts were not displayed in the Alert Console even though the alert condition had been met. In addition, opening the notification link for an affected triggered alert could navigate to the Alert Console without displaying the corresponding alert information.

This fix ensures that triggered alerts are available in the Alert Console and that the associated notification workflow can display the expected alert details.

  • VUQA-6910: Triggered Alerts Not Displayed in Alert Console and Notification Link Shows No Data

O11ySource: Fortinet Firewall Default Alerts Fix​

Resolved an issue where default alerts were missing from the Fortinet Firewall O11ySource package. Because alert-based information is used by the associated monitoring views, the absence of the required alerts affected the availability of expected alert-driven information.

This fix ensures that the required Fortinet Firewall alerts are included as part of the supported O11ySource package and are available for the corresponding monitoring and alerting workflows.

  • CCBD-5435: The Alerts Are Missing in the Fortinet Firewall O11ySource

Dashboard Folder Name Casing Fix During Import​

Resolved an issue where the original casing of a dashboard folder name was not preserved when importing a dashboard through Manage Resources. Although the dashboard was imported successfully, the folder name could be automatically converted to lowercase instead of retaining the casing defined in the exported resource.

This fix ensures that imported dashboard folder names retain their original casing and remain consistent with the folder name contained in the exported resource.

  • VUQA-7013: Preserve Original Casing of Grafana Folder Title During Import

ClickHouse Materialized View Custom CASE Condition Fix​

Resolved an issue where custom CASE-based conditions could not be handled correctly while creating ClickHouse Materialized View definitions through metadata JSON. Conditional aggregation or custom CASE expressions could fail during Materialized View generation or execution.

This fix improves Materialized View metadata handling so that supported custom CASE conditions and conditional expressions can be processed correctly during table and Materialized View creation.

  • VUQA-6606: ClickHouse – Issue with Passing Custom CASE Conditions in ClickHouse MV Metadata JSON

Guardrails Dashboard Cleanup​

Updated the Guardrails dashboards to align with the currently supported guardrail configuration. Dashboard references associated with removed guardrails have been cleaned up so that the available dashboard information reflects the current guardrail set.

This fix improves consistency between the Guardrails dashboard and the guardrails available in the platform.

  • CCBD-4543: Clean Up Guardrails Dashboards to Reflect Removed Guardrail

O11ySource: Kong API Gateway Server Endpoint Validation Fix​

Resolved an issue where valid Kong API Gateway server endpoint URLs could be reported as invalid in the O11ySource configuration UI. The existing URL validation pattern did not correctly support certain valid URL formats, including supported domain structures and endpoint configurations.

The validation logic has been updated to support HTTP and HTTPS URLs using valid domain names or IP addresses with supported port information. This fix ensures that valid Kong server endpoints can be entered and saved successfully during O11ySource configuration.

  • VUQA-6881: Kong O11ySource Server Endpoint Says Invalid in UI

O11ySource: Nutanix Multi-Server Onboarding Fix​

Resolved an issue where users were unable to onboard multiple Nutanix servers using the expected vuSmartMaps O11ySource workflow. Attempting to add another Nutanix server could prevent the additional source from being configured as expected.

This fix enables the supported onboarding workflow to handle multiple Nutanix server configurations correctly, improving monitoring setup for environments containing more than one Nutanix server.

  • VUQA-6889: Unable to Add Multiple Nutanix Servers in vuSmartMaps

O11ySource: Syslog Deployment and Jinja Template Fix​

Resolved configuration issues in the Syslog O11ySource deployment template and Jinja template that could prevent the Syslog pod or Telegraf process from starting correctly. The deployment configuration contained an incorrectly structured container startup command, while the generated Telegraf configuration referenced an incorrect field for the Syslog server configuration.

The required deployment and Jinja template configuration has been corrected and the applicable vuTelegraf image reference has been updated. This fix ensures that the Syslog O11ySource can start with the expected configuration and receive and process Syslog messages through the supported deployment workflow.

  • CCBD-5373: Syslog O11ySource – Fix Jinja Template and Update vuTelegraf Image Tag for Release 2.16

Sybase Custom Query Connection Handling Fix​

Resolved an issue where custom monitoring queries executed against a Sybase database could interfere with other users attempting to establish new database connections. The monitoring workflow could leave database activity in a state that affected connection availability for other users.

The query and connection-handling behavior has been updated to prevent monitoring queries from blocking supported user connections, improving reliability of SAP ASE/Sybase monitoring alongside normal database activity.

  • NCS-2574: Sybase Custom Query Blocking Other User Connections

Summary​

With vuSmartMaps™ NG 2.16.14, the platform continues to evolve toward a more consistent and seamless observability experience across supported environments. New monitoring capabilities, focused enhancements, and targeted fixes help strengthen operational confidence and improve the overall monitoring and integration experience. We look forward to building on these improvements in upcoming releases with continued focus on usability, performance, and broader observability coverage.

Support​

support@vunetsystems.com