Sr. Solution Architect, Project Manager at a financial services firm with 5,001-10,000 employees
Real User
Top 20
2024-11-15T04:30:03Z
Nov 15, 2024
The diagnostics perspective, particularly in terms of the root cause analysis of failures, should be improved. There needs to be more development in this area, as the support and the number of people working on the tool are decreasing.
OpenText Technical Support at CMS Computer PVT LTD
Real User
Top 5
2024-08-11T07:49:22Z
Aug 11, 2024
The solution's technical support presents a lot of issues with too many delays. Emergency support is unavailable when we raise a P1 ticket for production downtime.
Sr. Solution Architect, Project Manager at a financial services firm with 5,001-10,000 employees
Real User
Top 20
2022-10-20T13:56:29Z
Oct 20, 2022
Real User Monitor needs to cover more protocols to provide more in-depth information. It could also be better at monitoring voice-related traffic. There is currently no visibility in that channel.
Presales Manager at a tech services company with 51-200 employees
Real User
2021-11-02T12:23:47Z
Nov 2, 2021
Everybody is moving away from traffic and installing agents on the application to do the job, but Micro Focus is using traditional ways to collect the traffic. They should change their architecture completely.
Learn what your peers think about OpenText Real User Monitoring. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
Unit Manager | Management Systems and Automation at a tech services company with 1,001-5,000 employees
Real User
Top 5
2021-07-03T01:01:27Z
Jul 3, 2021
This technology is considered to be older. We are using the type of data collection that is mirroring traffic from application servers to Real User Monitor servers. Many other vendors such as AppDynamics, and Dynatrace, are using code injection and the values are more true with code injection. But for the mirroring, or data mirroring, it is not as true. On the technical side, the data mirroring is easier to configure. The code injection needs development. You have to direct the development team on what to do, for you to use the data. For the data mirroring, you can ask the network team to mirror the application server data to my server. You can get all of the data. it is very easy to configure. Most of the dashboards require a lot of configuration. We are not happy with the dashboard. It is simple but you need to do some extra configuration, and you need to know another reporting tool that needs to integrate with. It is very difficult to manage this process
IT Specialist at a financial services firm with 5,001-10,000 employees
Real User
2020-09-06T08:04:00Z
Sep 6, 2020
This solution needs to be more lightweight. It requires that you purchase a Microsoft or Oracle database, which adds extra costs. This product still uses Java, which has been removed from most of the browsers and it requires an additional install step for the client. You need to purchase a lot of extra products from Micro Focus because the integration with them is required before you get a final, working solution. It is an old design that has not changed in the past ten years, other than the name of it. It takes 20 to 30 minutes to start the application. When we want to monitor our encrypted traffic, this product doesn't work because our cipher is not supported. Because RUM is based on port sniffing, it means that you need to configure a port on the network or switch. This works fine in an on-premises deployment, but we are moving to the cloud and user monitoring is done differently.
We would like to see support for non-Windows environments. Right now, we have to use it on a Windows server, but some of our customers don't like this. I would like to see improvements made in terms of agent-based support. As it is now, we can install an agent on the application server, but it is not recommended for systems that are in production. In our experience, it is a really good option that we can implement for customers that do not want to reconfigure or change their network.
CEO at a tech services company with 51-200 employees
Real User
2019-11-04T06:14:00Z
Nov 4, 2019
One area to improve is the user interface, of course. The second one is their R&D has virtually stopped building a product roadmap. They need to really do a catch-up game with many of their incoming competitors. They actually need to completely revisit their product development strategy and overall product approach, if they wish to remain relevant in the APM market.
Real User Monitoring (RUM) an End user monitoring that gives you visibility into user behavior for fast, targeted problem resolution. It monitors the performance and availability of business-critical application services for all users at all locations all the time. It automatically discovers underlying infrastructure and classifies user actions - giving you instant visibility into session and whole service health over web, cloud, and mobile user experience. It allows you to trace user...
The diagnostics perspective, particularly in terms of the root cause analysis of failures, should be improved. There needs to be more development in this area, as the support and the number of people working on the tool are decreasing.
The solution's technical support presents a lot of issues with too many delays. Emergency support is unavailable when we raise a P1 ticket for production downtime.
The product needs more R&D to make it easier and more compatible with other software.
Real User Monitor needs to cover more protocols to provide more in-depth information. It could also be better at monitoring voice-related traffic. There is currently no visibility in that channel.
There have been some issues with customers implementing this solution and with login errors, which could be areas for improvement.
Everybody is moving away from traffic and installing agents on the application to do the job, but Micro Focus is using traditional ways to collect the traffic. They should change their architecture completely.
This technology is considered to be older. We are using the type of data collection that is mirroring traffic from application servers to Real User Monitor servers. Many other vendors such as AppDynamics, and Dynatrace, are using code injection and the values are more true with code injection. But for the mirroring, or data mirroring, it is not as true. On the technical side, the data mirroring is easier to configure. The code injection needs development. You have to direct the development team on what to do, for you to use the data. For the data mirroring, you can ask the network team to mirror the application server data to my server. You can get all of the data. it is very easy to configure. Most of the dashboards require a lot of configuration. We are not happy with the dashboard. It is simple but you need to do some extra configuration, and you need to know another reporting tool that needs to integrate with. It is very difficult to manage this process
This solution needs to be more lightweight. It requires that you purchase a Microsoft or Oracle database, which adds extra costs. This product still uses Java, which has been removed from most of the browsers and it requires an additional install step for the client. You need to purchase a lot of extra products from Micro Focus because the integration with them is required before you get a final, working solution. It is an old design that has not changed in the past ten years, other than the name of it. It takes 20 to 30 minutes to start the application. When we want to monitor our encrypted traffic, this product doesn't work because our cipher is not supported. Because RUM is based on port sniffing, it means that you need to configure a port on the network or switch. This works fine in an on-premises deployment, but we are moving to the cloud and user monitoring is done differently.
We would like to see support for non-Windows environments. Right now, we have to use it on a Windows server, but some of our customers don't like this. I would like to see improvements made in terms of agent-based support. As it is now, we can install an agent on the application server, but it is not recommended for systems that are in production. In our experience, it is a really good option that we can implement for customers that do not want to reconfigure or change their network.
One area to improve is the user interface, of course. The second one is their R&D has virtually stopped building a product roadmap. They need to really do a catch-up game with many of their incoming competitors. They actually need to completely revisit their product development strategy and overall product approach, if they wish to remain relevant in the APM market.