Release: May 9, 2022
Monitor Kubernetes namespaces
You can now customize the Kubernetes namespace on which the OpsRamp agent is deployed, in a Kubernetes cluster. You can specify a custom namespace in the agent deployment configuration file for Kubernetes. Prior to this release, the OpsRamp agent could only be deployed in an OpsRamp defined namespace.
End-of-Life OS versions no longer supported by OpsRamp agent
As announced earlier (see deprecation notice), starting agent version 12.0.0, the OpsRamp agent will not work on the following OS versions:
- Fedora Linux versions 30.X and prior versions.
- Oracle Linux versions 5.X and prior versions.
- Red Hat Linux versions 5.X and prior versions.
- SUSE Linux Enterprise Server (SLES) versions 11.3 and prior versions.
OpsRamp agents that are currently installed on these OS versions will stop working when they are upgraded to agent version 12.0.0.
Agent-based monitors re-trigger alerts every 6 hours
Agent-based monitors now re-trigger alerts every 6 hours, even if the original alert’s state has not changed. This is to ensure that alertable conditions that persist on managed resources are brought to the user’s attention again.
NoteGateway-based monitors already re-trigger alerts every 6 hours. With this enhancement, re-triggering of alerts works identically between gateway-based and agent-based monitors.
File integrity checks on agent-based custom monitor scripts and runbook scripts
OpsRamp agents now perform file integrity checks on custom monitor scripts and runbook automation scripts prior to running them. This enhances security by ensuring that scripts that run on managed resources have not tampered with. If the agent detects a script that has been tampered with, the agent will trigger an alert to notify users.