2023 Collector Updates

Week of July 24, 2023 (15.1.0)

Classic Apps

Alert on missing components

We added support to Alert on missing components to gateway-based classic integrations and SDK App monitoring. When creating the template, select the Alert on missing component check box for the required metrics.

See Alert on Missing Component for more details.

VMware Monitoring Enhancement

Added monitoring support to VMware vSAN 8 version.

See VMware vSAN for more details.

MySQL Monitoring Improvement

Upgraded the MySQL jar version to support TLS-1.2 version.

Bug fixes

• Resolved the issues where the RAM attribute value was not displayed for SNMP discovered devices.
• Fixed the recurring hyperflex event alerts creation problem after vprobe service restart.
• Addressed the inventory and monitoring issues for IBM Storwize.
• Corrected the configuration backup connection issues.

NextGen Gateway

Known Issues in v15.0.0 to v15.1.0 upgrade

We are aware of a known issue in the v15.0.0 NextGen gateway. Few customers encountered difficulties upgrading their gateways from v15.0.0 to v15.1.0 through the OpsRamp UI. However, we have successfully addressed this issue in v15.1.0. To perform the upgrade from v15.0.0 to v15.1.0, customers are advised to manually upgrade their gateways using any one of the following solutions:

Note: Customer needs to allow the upgrade in the OpsRamp UI.

Solution 1:

1. Login to OpsRamp portal and navigate to Automation > scripts section.
2. Create a category (global or specific partner/client based on the required scope).

3. Create a script by selecting the below mentioned drop-down:
   • Select Script Type > Global Script / Partner or Client Script (Based on the required scope of the script).
   • Execution Type > SHELL
   • Platform > Supported on Linux and provide other required details.

4. Add the following script in the Script field:

#!/usr/bin/sh 

logFileName="/tmp/ondemand-job.log" 

echo "$(date) : Creating yaml file" >> $logFileName 

kubectl get cm vprobe-updater-cm -n $1 -o jsonpath='{.data.ondemand-job\.yaml}' > /tmp/ondemand-job.yaml 

  

if [ $? -eq 0 ]; then 

        echo "$(date) : Successfully created yaml file" >> $logFileName 

        echo "$(date) : Creating  on-demand job" >> $logFileName 

        kubectl apply -f /tmp/ondemand-job.yaml -n $1 

        if [ $? -eq 0 ]; then 

                 echo "$(date) : Successfully created on-demand job" >> $logFileName 

        else 

                 echo "$(date) : Failed to  created on-demand job" >> $logFileName 

        fi 

else 

       echo "$(date) : Failed to create yaml file" >> $logFileName 

fi

5. Add the following parameters to the script

6. Go to your script and click the Apply scripts to devices option.

7. Select following data:

8. Click Run Now.

9. To check the successful execution of script verify /tmp/ondemand-job.log file.

tail -f /tmp/ondemand-job.log

10. Verify ondemand pod status

    podname: nextgen-gw-updater-ondemand-jon-*

kubectl get pods

Solution 2:

If the gateway is not having an OpsRamp agent. Run the upgrade-gateway.sh script to upgrade gateways from v15.0.0 to v15.1.0.

1. Launch the gateway SSH console.
2. Create upgrade-gateway.sh file, add following content:

#!/usr/bin/sh 

logFileName="/tmp/ondemand-job.log" 

echo "$(date) : Creating yaml file" >> $logFileName 

kubectl get cm vprobe-updater-cm -n $1 -o jsonpath='{.data.ondemand-job\.yaml}' > /tmp/ondemand-job.yaml 

  

if [ $? -eq 0 ]; then 

        echo "$(date) : Successfully created yaml file" >> $logFileName 

        echo "$(date) : Creating  on-demand job" >> $logFileName 

        kubectl apply -f /tmp/ondemand-job.yaml -n $1 

        if [ $? -eq 0 ]; then 

                 echo "$(date) : Successfully created on-demand job" >> $logFileName 

        else 

                 echo "$(date) : Failed to  created on-demand job" >> $logFileName 

        fi 

else 

       echo "$(date) : Failed to create yaml file" >> $logFileName 

fi

3. Save the script and click Run.

sh upgrade-gateway.sh default

Note: If the gateway is running on another namespace, we recommend the namespace to be changed.

sh upgrade-gateway.sh {NAME SPACE} 

4. Verify /tmp/ondemand-job.log file, to check the successful execution of script.

tail -f /tmp/ondemand-job.log

5. Verify the ondemand pod status.
   podname: nextgen-gw-updater-ondemand-jon-*

kubectl get pods

Synthetics

Synthetic HTTP/s resource not working when setting post data option

Fixed the bug in the libcurl version that was causing issues with correctly posting data in HTTP/s POST Method calls.

Week of June 20, 2023 (15.0.0)

Agent Enhancements

Customized Windows event log monitor alert component

The ‘Alert Component’ filter will now support the Windows Event Logs Monitor. This update allows users to filter event logs by specifying a component name in the “Alert Component" field. By doing so, the agent will create separate event log alerts based on the given component name.

Note: This feature will be available from Agent version 15.0.0 and higher.

See Set up Windows Event Logging for more details.

Linux Agent Compatibility with IBM-Based 64-bit Architecture

The Linux Agent 15.0.0 now supports IBM Power Systems 64-bit architecture. This is currently in the beta release stage, and the support is for Red Hat 8.4 and CentOS 8.4 and above operating systems running on IBM Power Systems.

See Support Matrix for more details.

GPU Monitoring

With the release of Agent version 15.0.0, Nvidia GPU Monitoring is supported in Cloud Native environments.

See Nvidia GPU Monitor for more details.

NextGen Gateway Enhancements

External CSI Drivers Support

OpsRamp customers will now be able to provide their own CSI driver if they have multiple CSI drivers in their Kubernetes cluster for NextGen Gateway storage.

See OpsRamp Collector Bootstrap Tool for more details.

Ability to launch the Debugging container

NextGen has a new debugging feature to debug pods running (or crashing) on a Kubernetes Node.

See Troubleshooting Guide for more details.

Ability to generate thread dump and heap dump

The NextGen Gateway now supports the generating of thread dumps and heap dumps for the vProbe code base.

See Generate Thread Dump and Heap Dump for more details.

Running Squid Proxy as separate pod

Customers using the NextGen Gateway can now view the Squid proxy as a distinct pod. The OpsRamp agents connected to the gateway’s Squid proxy will remain unaffected in the event of a NextGen Gateway pod crash or restart.

Classic Gateway Enhancements

Classic Gateway to NextGen Gateway update

The migration to NextGen Gateway will bring a lot of benefits and enhancements, ensuring a more efficient and optimal gateway experience. Refer to NextGen Gateways, for the NextGen Gateway documentation.

Note: The migration from the Classic Gateway to the NextGen Gateway is optional, but highly recommended.

See Migration of Classic Gateway for more details.

Classic Gateway Support on Ubuntu 22.04 LTS OS

OpsRamp Classic Gateway 14.0.0 appliance is built around Ubuntu 18.04 LTS distribution. Since Ubuntu 18.04 LTS has reached the end of its life cycle and is now deprecated, the Linux distribution in the classic Gateway appliance is now upgraded to Ubuntu 22.04 LTS Server. By transitioning to the newer gateway version, you can take advantage of the improvements, and continuity of security upgrades in Ubuntu 22.04 LTS.

The latest version of Ubuntu 22.04-based Classic Gateway can be downloaded from the OpsRamp portal, Setup > Downloads > Gateway section.

To migrate from the existing ateway to the new gateway, refer to Major Updates documentation for detailed instructions.

To deploy the new gateway and registering it with the new management profile, refer to Deployment documentation for detailed instructions.

Week of February 28, 2023 (14.0.0)

Agent Enhancements

Agent support ARM based CPU architecture

Linux Agent has been extended to support 64-bit ARM based compute systems starting from Agent version 14.0.0.

See Support Matrix section for specific distributions and versions.

Creating G2 Agent template using G1 plugin

Agent version 14.0.0 and onwards we have advantages of achieving G2 template features (Like - component filters and component thresholds), using existing G1 templates and users will be able to create G2 templates out of G1 application monitors.

The G1 application monitoring template and corresponding G2 template will be available in the recommended templates section.

See Agent-based Templates section for more details.

Agent based Linux process monitoring

Now, Agent based G2 Process statistics template has an option to select process statistics matching criteria (process.stats.matching.criteria) with three options:

• Include Process Arguments
• Exclude Process Arguments
• Match Exact Process Name.

See Agent-based Templates section for more details.

Kubernetes/OKD setup

With 14.0.0 agents, containers are discovered with its actual name in Kubernetes/OKD cluster. Previously OpsRamp agents used to discover container by containerName_PodName.

Removed support for alerting on pod level kube events through agent from K8s agent 14.0.0

We have removed support for existing pod level kube events from K8s agent 14.0.0, which means that there will no longer be any alerts on pod events. Instead, we supported Template monitoring for pod status.

Agent 14.0.0 now supports kubernetes pods monitoring template

We introduced the template for monitoring the status of running pods per each kind of kubernetes deployment such as Daemonset, Deployment, Replicasets, and Statefulsets.

See K8s Pods Supported Monitor Metrics section for more details.

This template will have metrics for desired pods count, current running pods count, and percentage of running pods (Percentage of running pods = number of running pods * 100 / The number of desired pods) for all kinds of deployments such as daemonset, replicaset, deployment, and statefulset.

Note

If the user still wants to receive alerts for above pod events, they can add them to the other section of the kube-events config map in the agent deployment configuration yaml, as shown below.

NextGen Gateway Enhancements

General Availability (GA) with HA support

NextGen Gateway 14.0.0 is available for general use. Users can now deploy one or more NextGen Gateway collector services in a single Kubernetes cluster. The OpsRamp NextGen Gateway builds on our battle-tested and proven current Gateway to address the growing demands around high availability, scalability, ease of onboarding, and the need to simplify the overall discovery and monitoring of our customer’s ever-growing Hybrid Cloud environments.

See Installing NextGen Gateway in High Available Mode section for more details.

Zero-touch onboarding support

This feature helps users with easy onboarding of customer’s IT environments into OpsRamp SaaS platform. Zero-touch onboarding automates what is currently manual and separate steps to create credentials, configuring discovery profiles, and manually launching integrations in one single unified step. Users can now specify all these required details in a single YAML file and instruct the OpsRamp Gateway Bootstrap tool to read those details from the YAML file at the Gateway install time.

Post a successful Gateway install, the tool automates creation of all the required configuration artifacts which then trigger the discovery and monitoring processes on the Gateway without requiring any additional manual intervention from the user.

See Zero-touch Onboarding section for more details.

Multi Tenancy support

Users can now install more than one Gateway service in a single Kubernetes cluster each in its own Kubernetes namespace. All the resources discovered and monitored by each Gateway service are stored in the cloud in their respective tenancy scope tied with the Gateway at the time of Gateway service install.

The Gateway services operate independently of each other within the Kubernetes cluster and interact with the cloud independently via their own respective TLS connections with the cloud. Make sure that the Kubernetes nodes in the cluster are provisioned with the right amount of CPU, DRAM, and storage to host all the required Gateway service instances.

See Multi Tenancy section for more details.

Helm Chart deployment support

Now users can deploy the OpsRamp Gateway on any Kubernetes cluster using the OpsRamp generic Helm Chart without using the bootstrap tool.

See Helm Chart Based Deployment section for more details.

Classic Gateway Enhancements

Security and Vulnerability updates

OS level security improvements by upgrading OS packages to the latest version from Ubuntu 1804 repository.

Synthetic Enhancements

Providing support for Synthetic Monitoring - OAuth 2.0

HTTPS synthetic resource monitoring is enhanced and comes with an OAuth authentication mechanism.

Packet loss graph when device is down

The Packet loss graph now shows 100% for the Ping Synthetic monitoring, if the Packet loss for a device is 100%. This will help users in generating alerts.