H1-2024

Assign Monitors > Agent - Windows Service Monitor

• Effective Date: June 2024
• Announcement Date: April 2024

Recently we announced deprecation for the Assign Monitors option and you can find the deprecation here , all the options in the Assign Monitors section are removed and you have to create a template and assign it to the resource instead of assigning the monitor directly.

This deprecation is exclusively for the Agent - Windows Service Monitors option and you are not allowed to use this option after the effective date. Alternatively, you can create a template and monitor your Windows Services using the template by following the steps. Create a new template, select collector type as Agent, Monitor type G1, Applicable for Device, and add your Services in the Windows Service Monitor section and use the template.

Standard Reports

• Effective Date: June 2024
• Announcement Date: March 2024

As of the effective date:

The following reports will be deprecated in Standard Reports:

• Cloud Report
• Device Report
• Inventory Report
• Network backup report
• Login Activity Report
• Ticket Report
• Cloud Instances Report
• Monitor Details

After the deprecation date, you won’t be able to create the new ondemand/schedules reports for the above reports and the old data will no longer available.
Due to a change in architecture, existing schedules cannot be migrated. It is necessary to create new schedules within the reporting apps.

You can access the same reports with the enhanced capabilities through the reporting apps (Reports > Reporting Apps section). Utilize the respective apps for both on-demand and scheduled runs.

To view the Phase I deprecation list of standard reports, refer the document.

Classic Dashboards

• Effective Date: September 2024
• Announcement Date: March 2024

The classic dashboards are being deprecated, and users should now create any new dashboard requirements using Dashboards 2.0 which are feature-rich and customizable according to business needs. The default landing page is configurable to Dashboard 2.0 at the user level.

The following widgets are now end of life in Classic Dashboards and not available anymore. Only the existing instances are functional in classic dashboards and these will not be part of Dashboard 2.0 migration.

• Active live console stats.
• Antivirus stats.
• App integrations failures logs.
• Cloud cost trend.
• Inference stats
• Forward Schedule Change Widget
• Project Widget
• Task Widget
• Activity Log Widget

See Legacy Replacements for more information.

The conversion plan will be published in detail in the next upgrade; until then, the conversion functionality in beta release will have limited functionality. User can see the classic widgets getting convered to tiles to provide the equivalent rendering for all the supported classic widgets only. Limited functionality to download equivalent Dashboard 2.0 JSON. User needs to manually import the JSON file and see it as dashboard 2.0 with same name.

See Conversion Tool for more information.

The below are limitations of the beta tool:

• Dashboards existing sharing configuration is not supported.User needs to re-share again.
• Color visualization are with default colors.
• All the EOL classic widgets will not be the part of conversion.
• Image widget conversion is currently not supported and will get added later
• Patch Compliance and Cloud Insights deprecated Widgets are also not the part of conversion.

See Tile category mapped to Widgets table on how to use a tile category to make an equivalent widget to achieve the similar visualization.

Patch Compliance Widget

• Effective Date: May 2024
• Announcement Date: March 2024

The classic Patch Compliance Widget will be deprecated in Classic Dashboards. You will still be able to view the widgets that have already been created. After the deprecation date, you will not be able to create new instances of the Patch Compliance Widget.

Existing dashboards using these widgets may experience limited support, and users can refer to the Patch Management 2.0 dashboard and create Patch Compliance Cards. For any questions or assistance, feel free to contact our Support team.

Metrics Page

Effective Date: May 2024

Announcement Date: March 2024

The legacy “Metrics” on resource details view is getting deprecated and replaced by “Metric 2.0” which has more scalable metric data graph representation and follow industry standard metric nomenclature.

The below is the list of updated features user can find comparitively with legacy metrics:

The following Metric API’s are also getting deprecated:

• Post Time-Series Metric Data

• Time-Series Metric Data

This would be replaced by:

• Metrics

Note: The Ingesting metric data API is in progress

Audit Logs

• Effective Date: May 2024
• Announcement Date: March 2024

The Audit Logs functionality has been moved from Setup > Integrations to
Setup > Account > Integrations and Apps for all applicable integrations.

Assign option for Master Agent Profile

• Effective Date: May 2024
• Announcement Date: February 2024

The Assign Now option for the Master Agent Profile in the Resource > Attributes section will be removed after the effective date, as OpsRamp does not support Agent based management profiles.

Assign Monitors

• Effective Date: April 2024
• Announcement Date: May 2019

Assign Monitors option in Resource > Monitors > Monitors tab will be removed after the effective date and assigning a monitor directly to the resource will not be possible.

Alternatively, you can create a template and assign it to the resource.

Containers page

• Effective Date: July 2024
• Announcement Date: January 2024

The Containers page at Infrastructure > Containers will be deprecated by the effective date.

Reason

Based on the usage of this page, the overall feedback we have heard from customers, and alternatives available within OpsRamp to achieve the same use cases, OpsRamp is deprecating the page. This will also help reduce complexity in the product.

Alternatives available

• A curated dashboard will soon be available in Dashboard 2.0 that will replicate the information shown on the Containers page.

• The new resources page (Infrastructure > Search) will also list out the containers/nodes, their availability, and the tags on those resources as shown below:

Classic Apps

• Effective Date: March 2024
• Announcement Date: January 2024

As of the effective date:

The following Apps will be deprecated from the Integrations. You will still be able to use them if you have already installed them. After the deprecation date, any new installations of these apps will not be allowed:

• Azure Stack
• Java Virtual Machine
• Redhat Jboss
• IBM WebSphere (Legacy Classic App)
• WildFly
• Hitachi VSP (Legacy Classic App)
• VMware (SDK Beta Version)
• SNMP (SDK Beta Version)
• Contrail Controller
• Dell EMC VPLEX

Custom Integration

• Effective Date: March 2024
• Announcement Date: January 2024

As of the effective date:

The Custom category within Custom Integration is relocating to user management. This change won’t affect other Custom Integration categories.

To access Custom Integration:

1. Navigate to Setup > Users.
2. Enable the API option in the User Access field when creating or updating a user.

Notes:

• Existing Custom Integrations will remain visible under Integrations and Apps. However, support for them will decrease in future releases.
• For continuous support, create custom integrations using the steps mentioned above.

Should you have any inquiries or require aid, feel free to get in touch with the OpsRamp support team.

Resource Availability Score

• Effective Date: April 2024
• Announcement Date: January 2024

The resource availability score shown against an individual resource in the resource overview section will be replaced with individual availability states.

Reason

The current availability percentage score only considers the DOWN state of the resource (critical alert on availability metric); due to this limitation, the UNKNOWN and UNDEFINED states of the resource are not considered while calculating the availability score.

We will introduce individual resource availability states instead of showing the overall percentage. You will see four states along with the respective percentages of each availability state.

How is this going to affect

Example: A resource was onboarded in OpsRamp on January 1st, and on January 2nd, a monitoring template was assigned to the resource, but no monitoring data was collected for one day due to different reasons. On January 3rd, OpsRamp started collecting data, and there were no critical alerts on the availability metrics for one day. On January 4th, a critical alert was generated for the resource on the availability metric.

By considering the above example,

The last four days resource availability percentage with the current design will be 75%.

Because, in the above example the resource has a critical alert on availability metric for one day out of four days.

The last four days of resource availability state percentage after the new changes will be:

• UP: 25%
• DOWN: 25%
• UNKNOWN: 25%
• UNDEFINED: 25%

How will this benefit

With this change, you are going to see the individual states of the resources, and this helps you to exactly understand how much percentage of time a resource was in UP, DOWN, UNKNOWN, and UNDEFINED states.

Impacted areas

Due to the new changes, the following areas will be impacted:

Reports

• Standard Reports > Availability Report: The Availability(%) field in the report will be replaced with UP(%).
• Reporting Apps > Availability Details: As the individual availability scores are already displayed, the Availablity(%) field will be removed.

Schedule maintenance

Currently, while calculating the resource Availability Score (%), the scheduled maintenance time is not considered, and only unplanned downtime is considered.

Current availability formula: Availability Score (%) = ((Duration - UnPlannedDownTime) * 100) / Duration

Example: Let’s say you have a resource with Availability State DOWN from 10 AM to 2 PM, but you have enabled scheduled maintenance between 11 AM and 1 PM.

The Resource Availability Score (%) for 10 AM to 2 PM.

Here is the comparison:

• The Resource Availability Score (%) with the current design will be 50%.

  Because the 11 AM to 1 PM DOWN state is being treated as UP.

• The resource UP (%) after the new change will be 0%.

  Because the 11 AM to 1 PM scheduled maintenance time will be treated as DOWN.

  The new design represents the percentage of individual availability states, both UnPlannedDownTime and PlannedDownTime (scheduled maintenance time) will be treated as DOWN.

  If you want the PlannedDownTime (scheduled maintenance time) to be treated as UP, then you have the option to consider it as UP even if the resource is in the DOWN state during the scheduled maintenance time.

  You can do this by going to Setup > Accounts > Clients > Availability Settings.

APIs

The following two v2 APIs will be deprecated and replaced with the new v3 APIs

• Resource Availability: https://develop.opsramp.com/v2/api/resource-management/clientid-resources-resourceid-availability

• Service Availability: https://develop.opsramp.com/v2/api/resource-management/clientid-services-serviceid-availability

Management Profiles

• Effective Date: March 2024
• Announcement Date: December 2023

The Management Profiles option in the Setup > Resources section will be removed as of the effective date and this option will be replaced with Collector Profiles.

All the existing Gateway Management Profiles will be automatically moved to the Collector Profiles section after migration.

Note: The existing Agent Management Profiles will not be moved to the new Collector Profiles as we stopped supporting Agent-based profiles.

Agent-based Management Profile

• Effective Date: February 2024
• Announcement Date: December 2023

As of the effective date, the agent-based management profile option in Setup > Resources > Management Profiles > Add > Profile Type > Agent will be removed from the UI. This option was originally designed for first-generation agents, which OpsRamp no longer supports. Therefore, we have decided to completely remove this option.

OpsRamp will not delete any existing agent-based management profiles, but we strongly recommend that you manually delete them.

Note: The associated agent-based URL, DNS, and Ping (G1) monitors will be deleted from the resources after removing the agent-based management profile.

Agent-based G1 SNMP Monitors

• Effective Date: February 2024
• Announcement Date: December 2023

As of the effective date, the SNMP Monitors option on the Agent-based G1 template creation page will be removed. This feature was originally designed for first-generation agents, which OpsRamp no longer supports. Consequently, we have decided to completely eliminate this option.

Alternatively, you may choose to utilize gateway-based SNMP monitoring templates.

Legacy Ping, URL, and DNS monitors are replaced by Synthetics

• Effective Date: February 2024
• Announcement Date: November 2016

Agent based Ping Monitoring Configuration, URL Monitoring Configuration, and DNS Monitoring Configuration will be replaced with Synthetic monitoring.

SNMP Monitoring - Resource timeout alert

• Effective Date: February 2024
• Announcement Date: November 2023

SNMP monitoring from the OpsRamp gateway generates a critical alert if the target resource does not respond to the monitoring request from the gateway. The alert will be generated if two consecutive checks fail. With the current design in rare scenarios, short network glitches in the customer environment can create multiple critical alerts and as a result, there will be noise.

Scenario: Let’s assume a resource is applied with 1 min, and 2 min SNMP monitors and both monitoring frequencies will sync every 2 minutes and can generate an alert immediately at the 2nd minute in case of network issues. Here two consecutive checks happen at the same minute. Sometimes this creates huge noise.

To overcome this OpsRamp is going to change the logic from two consecutive checks to five minutes internal. If the resource stops responding to SNMP requests for more than 5 minutes then a critical alert will be generated.

This change will be available in both classic and next-generation gateway starting with version 17.0.0