Autotask integration

  • Effective Date: November 2021
  • Announcement Date: April 2021

As of the effective date:

  • Autotask integrations are upgraded to support v1.6 API/SOAP calls.
  • Autotask v1.5 API/SOAP calls on outbound configurations are not supported.

EOL for Fedora Linux v30.x

  • Effective Date: November 2021
  • Announcement Date: June 2021

As of the effective date:

  • Fedora Linux versions 30.x and below are not supported for monitoring and management functionality.

Agent updates for Fedora Linux v30.x and below will be stopped. These versions are already past end-of-life support from the vendor.

EOL for Oracle Linux v5.x

  • Effective Date: November 2021
  • Announcement Date: June 2021

As of the effective date:

  • Oracle Linux versions 5.x and below are not supported for monitoring and management functionality.

Agent updates for Oracle Linux 5.x and below will be stopped. These versions are already past end-of-life support from the vendor.

EOL for Red Hat Linux v5.x

  • Effective Date: November 2021
  • Announcement Date: June 2021

As of the effective date:

  • Red Hat Linux versions 5.x and below are not supported for monitoring and management functionality.

  • Agent updates for Red Hat Linux v5.x and below will be stopped. These versions are already past end-of-life support from the vendor

EOL for SLES Linux v11.3

  • Effective Date: November 2021
  • Announcement Date: June 2021

As of the effective date:

  • SUSE Linux Enterprise Server (SLES) versions 11.3 and below are not supported for monitoring and management functionality.

  • Agent updates for SLES Linux v11.3 and below will be stopped. These versions are already past end-of-life support from the vendor.

Legacy Webhook URI for Alerts and Incidents

  • Effective Date: September 2021
  • Announcement Date: June 2020

The following integrations that use the legacy webhook URI for alerts and incidents inbound communication will not be functional after the effective date. This applies only to installed integrations that use the legacy format and for which users are recommended to replace the existing legacy URI with the following format:

Alert

Alert Logic

ApplicabilityURI
Legacy URIhttps://api.opsramp.com/integrations/alertlogic/{tenantId}/alerts?vtoken={token}
New URIhttps://api.opsramp.com/integrations/alertsWebhook/{tenantId}/alerts?vtoken={vtoken}

Pingdom

ApplicabilityURI
Legacy URIhttps://api.opsramp.com/integrations/pingdom/{tenentId}/alerts?vtoken={token}
New URIhttps://api.opsramp.com/integrations/alertsWebhook/{tenantId}/alerts?vtoken={vtoken}

NewRelic

ApplicabilityURI
Legacy URIhttps://api.opsramp.com/integrations/newrelic/{tenentId}/alerts?vtoken={token}
New URIhttps://api.opsramp.com/integrations/alertsWebhook/{tenantId}/alerts?vtoken={vtoken}

Incidents

Autotask

ApplicabilityURI
Legacy URIhttps://api.opsramp.com/integrations/autotask/{clientId}/incidents/{vtoken}
New URIhttps://api.opsramp.com/integrations/incidentWebhook/{clientId}/incidents?vtoken={vtoken}

Jira

ApplicabilityURI
Legacy URIhttps://api.opsramp.com/integrations/jira/{clientId}/incidents/{vtoken}
New URIhttps://api.opsramp.com/integrations/incidentWebhook/{clientId}/incidents?vtoken={vtoken}

Status/State metric

  • Effective Date: November 2021
  • Announcement Date: August 2020

As of the effective date:

  • Status/State metric is no longer available.

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 cloud resources. Accordingly, the availability metric is transitioned to a new metric, which is dependent on the cloud resource type.

Status/State Metric

Trusted root certificates

  • Effective Date: November 2021
  • Announcement Date: May 2020

As of the effective date:

  • Servers must have trusted SSL/TLS root certificates from standard certificate authorities (CA) installed.

  • Trusted certificates are validated done through OpsRamp agents. Agent connections are validated 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.