Deprecation Notices

Deprecation notices for features that will not be available in future updates.

Canonical metric names

Effective Date: June, 2020
Announcement Date: April, 2020

OpsRamp is migrating its metric naming convention. This change will bring greater visibility into the service being monitored and provide a consistent model for referencing metrics. Although this change is currently limited to AWS and GCP resources, OpsRamp will iterate on all metrics over time to get them into the same model.

For example:

  • Old metric convention: aws.write.throughput
  • New metric convention: aws_redshift_WriteThroughput

Behavior changes to be aware

For metrics that are common across multiple resources, the metrics will be separated using the new notation and placing the metrics in their respective cloud templates.

Graphing impact

  • For resources where the existing metric is updated to the new convention, metric data will continue to plot.
  • For resources where a new metric is added, the old graph will have the wrong metric name with the metric collection stopping for the old metric. The new metric graph will populate with the updating metric name convention.

Alert impact

Any existing alert based on an old metric will persist. However, heals/critical alerts will not be processed after the change. Alerts with old metric notation will not be updated and not updated with new metric notation.

Create user from email request integrations

Effective Date: June, 2020
Announcement Date: March, 2020

The option for creating new users from email request integrations is deprecated and will not be available after the effective date.

Information about the requestor is available in the comment section and is searchable on the Email-ID.

Email Requests

Email Requests

Device attribute device type

Effective Date: June, 2020
Announcement Date: January, 2019

The Device Type attribute is deprecated. This attribute is visible in various pages that involve resource selection filters and in the Resource Attributes page. Device Type is replaced by the Resource Type Attribute.

Attribute Name

Attribute Name

Mac agents

Effective Date: June, 2020
Announcement Date: December, 2019

Agent support on Macintosh operating system (Mac OS) will be stopped.

Neustar integration

Effective Date: June, 2020
Announcement Date: February, 2020

The Neustar monitoring integration has been deprecated and will no longer be available after the effective date. As an alternative, configure a webhook-based custom integration.

NodeJS synthetics

Effective Date: June, 2020
Announcement Date: November, 2019

Users will not be able to create custom HTTPs synthetics using Java script. As an alternative, use the Python Selenium script or leverage the Selenium web recorder.

Node.JS deprecation

Node.JS deprecation

Permanent suppress action on alerts

Effective Date: June, 2020
Announcement Date: February, 2020

The Permanent Suppress action on alert has been deprecated and will no longer be available after the effective date. Un-assigning monitors on the resource is the recommended approach to stop monitoring a resource.

Permanent Suppress

Permanent Suppress

Post-install access to integration key and secret

Effective Date: June, 2020
Announcement Date: February, 2020

Keeping with industry standard security practices, the secret generated for an integration will be visible only at the time the integration is installed. The secret will not be available after you navigate away from the integration. You must copy and save the secret for later use.
If you lose the secret for an integration, you can re-generate a new secret from the UI.

This change only impacts integrations that are newly installed after the effective date. Existing integrations will function as is.

Inference Secret

Inference Secret

Runbooks in specific languages

Effective Date: June, 2020
Announcement Date: February, 2020

Support for Runbook Automation (RBA) scripts in the following languages is deprecated and will not be available as an option after the effective date:

  • Windows: Windows Batch file, Windows Commands, Windows Visual Basic, Windows EXE, Windows MSI, Windows Download.
  • Linux: Perl.

Jobs that are configured to run RBA scripts in these deprecated languages will not work after the effective date.

RBA scripts in the following languages will continue to be supported:

  • Windows: Windows PowerShell.
  • Linux: Python and Bash.

 

Runbook Automation Scripts

Runbook Automation Scripts

Service monitor configuration

Effective Date: June, 2020
Announcement Date: February, 2020

Service monitor configuration section under the Setup module is deprecated and will no longer be available as of the effective date.

As a replacement, you need to leverage the existing template-based monitoring.

Custom integrations with no associated role

Effective Date: July, 2020
Announcement Date: November, 2019

Starting with OpsRamp 5.4.0, custom integrations required that a role be selected. Integrations defined before OpsRamp 5.4.0 will no longer function. You will need to define new custom integrations.

Legacy synthetics

Effective Date: July, 2020
Announcement Date: November, 2016

Ping, URL and DNS monitors will be moved to Synthetic monitoring. See Synthetics for a workaround.

Relocation of Monitors

Relocation of Monitors

Actions on Windows services

Effective Date: September, 2020
Announcement Date: June, 2020

The ability to start or stop Windows services will no longer be associated with the Device Manage permission value as of the effective date.

To start or stop Windows services, the Allow to run all commands permission value must be in the commands permission.

If the Allow to run all commands permission is not implemented by the effective date, you will lose ability to use this feature.

Discovered Services

Discovered Services

Agents with unsupported versions

Effective Date: September, 2020
Announcement Date: August, 2019

Starting with the effective date, agents in your environment with unsupported versions cannot connect to OpsRamp.

See OpsRamp’s N-2 support policy for reference.

See Updating Agents on how to update your agents.

Alert priority attribute

Effective Date: September, 2020
Announcement Date: May, 2019

Alert Priority attribute will now be deprecated from all the OpsRamp supported monitoring templates. Alert Priority will be removed from all OpsRamp supported monitors.

Alert priority will be removed from the following OpsRamp-supported monitors:

  1. Application Monitors
  2. Custom Monitors
  3. Event log monitors
  4. Log monitors
  5. Performance monitors
  6. Process Monitors
  7. SNMP monitors
Application Monitors

Application Monitors

Custom Monitors

Custom Monitors

Performance Monitors

Performance Monitors

Other Monitors

Other Monitors

Windows Services Monitor

Windows Services Monitor

Event Log Monitor

Event Log Monitor

SNMP Monitors

SNMP Monitors

Basic authentication for APIs

Effective Date: September, 2020
Announcement Date: February, 2020

Basic authentication has been deprecated and can no longer be used to authenticate after the effective date.

  • Customers using basic authentication for inbound integrations or APIs via custom integrations need to use OAuth 2.0 authentication.
  • For integrations, such as AppDynamics, that are using Basic authentication and do not support OAuth authentication, use webhook-based authentication.

Canonical metric names (update)

Effective Date: September, 2020
Announcement Date: August, 2020

OpsRamp is migrating its metric naming convention.

The previous canonical metric changes transformed the metric naming convention for AWS and Google Cloud metrics.

This canonical metric change includes metrics for:

  • Azure
  • Kubernetes
  • Docker
  • Linux hosts
  • Linux applications
  • vCenter

This change brings greater visibility into the service being monitored and provides a consistent model for referencing metrics.

OpsRamp will iterate on all metrics over time to get them into the same model.

Example change

Metric Convention Example Change
Old Metric ConventionNew Metric Convention
azure.ingress.blobazure_storage_blobservices_Ingress

Behavior changes

For metrics that are common across multiple resources, the metrics will be separated using the new notation and placed in their respective cloud templates.

  • Graphing impact
    • For resources where the existing metric is updated to the new convention, metric data will continue to plot.
    • For resources where a new metric is added, the old graph will have the wrong metric name with the metric collection stopping for the old metric. The new metric graph will populate with the updated metric name convention.
  • Alert impact
    • Any existing alert based on an old metric will persist. However, no heals or critical alerts will be processed after the change.
    • Alerts with old metric notation will not be updated nor updated with new metric notation.

Days parameter for HTTPs synthetics

Effective Date: September, 2020
Announcement Date: August, 2020

OpsRamp is removing support for the Days parameter in HTTPs synthetics.

Google SSL

Google SSL

To leverage alerts and availability for the synthetic resource without the days parameter, use the ssl.cert.expiry.check metric in the HTTPs monitoring template.

ssl.cert.expiry.check Metric

ssl.cert.expiry.check Metric

This change provides better scalability and management of SSL certificate expiry times and makes synthetic resource availability more consistent and understandable.

Device APIs

Effective Date: September, 2020
Announcement Date: January, 2019

The following APIs will not be accessible after the effective date; attempts to call these APIs will fail.

The following table lists the deprecated device APIs along with respective replacements:

Recommended Resource APIs
Deprecated Device APIsReplacement Resource APIs
Create DeviceCreate Resource
Update DeviceUpdate Resource
Get DeviceGet Resource
Search DeviceSearch Resource
Delete DeviceDelete Resource
Get Minimal Device TypesGet Minimal Details of Resource Types
Get Minimal DevicesGet Minimal Details of Resources
Get Device ApplicationsGet Resource Applications

Execution order in device management policies

Effective Date: September, 2020
Announcement Date: September, 2019

Users will no longer be able to assign an Execution Order to Device Management Policies. After this change, Device Management Policies will continue to function normally, and there will be no noticeable change in behavior.

Gateways with unsupported firmware

Effective Date: September, 2020
Announcement Date: November, 2019

Starting with the effective date, gateways in your environment running unsupported firmware versions cannot connect to OpsRamp. See OpsRamp’s N-2 support policy for reference.

See Updating Gateway Firmware on how to update your gateways.

Incident actions on suppressed alerts

Effective Date: September, 2020
Announcement Date: June, 2020

The Attach and Update Incident and Attach Incident actions on suppressed alerts have been deprecated and will no longer be available after the effective date.

Incident Actions on Suppressed Alerts

Incident Actions on Suppressed Alerts

Inference stats widget

Effective Date: September, 2020
Announcement Date: February, 2020

The Inference Status widget is deprecated and will not be available after the effective date. The new Alert Stats provides more detailed information on alerts volume reduction.

Inference stats widget

Inference stats widget

Resource attribute - device name

Effective Date: September, 2020
Announcement Date: September, 2018

The attribute that was formerly known as Device Name will be renamed to Name.

The Name attribute is derived first from the Alias Name (User Defined), Host Name (Agent Defined) and then Resource Name (Gateway, SNMP, vCenter defined).

This change ensures better parity between the API and the UI. This change does not have any impact on user as the API already references Name. The existing policies that were leveraging Device Name will continue to function, but will now be populated with Name instead.

Attribute Name

Attribute Name

Support for Linux versions on end of life

Effective Date: September, 2020
Announcement Date: November, 2019

Starting with the effective date, OpsRamp will not support monitoring and management of the following versions of Linux. These versions are already past end of life support from their vendor.

  • CentOS 5.x
  • Ubuntu 10.x
  • Ubuntu 11.x
  • Ubuntu 12.x

OpsRamp agents running on these versions cannot connect to OpsRamp after the effective date.

Trusted root certificates

Effective Date: September, 2020
Announcement Date: May, 2020

Servers must have trusted SSL/TLS root certificates from standard certificate authorities (CA) installed. Trusted certificate validation is done through OpsRamp agents. OpsRamp validates agent connections to ensure that a managed server has trusted root certificates.

By default, servers with standard OS installations should have trusted root certificates installed. This change should be transparent to your servers.

For servers with a non-standard OS installation, please make sure that trusted root certificates are installed.

Java-based remote consoles

Effective Date: January, 2021
Announcement Date: June, 2020

Java-based remote consoles will not be available after the effective date. Browser-based remote consoles offer comparable functionality with additional benefits.

The following protocols are deprecated:

  • File TRANSFER - Replaced by RDP Disk share
  • RMSHELL - Replaced by SSH + SFTP
  • VNC
Remote Console

Remote Console

Remote access integrations

Effective Date: January, 2021
Announcement Date: June, 2020

The following remote console integrations are deprecated and will not be functional as of the effective date.

  • Teamviewer
  • NEC UNIVERGE PC PRO
Remote Access Integrations

Remote Access Integrations

Status/State metric

Effective Date: February, 2021
Announcement Date: August, 2020

The Status/State metric will be no longer be available after the effective date.

This metric is derived from the discovery of resources and is not tied to the health of the actual resource in the respective cloud provider. Currently, this metric is heavily tied to the availability of the cloud resources. Accordingly, the availability metric will be transitioned to a new metric which will be dependent on the cloud resource type.

Status/State Metric

Status/State Metric