Share your experience using AppPulse Suite [EOL]

We're a bank. We do use the predictive tools for the different products of the bank and the application which the bank utilizes.

AppD improves the productivity of Application Engineers, development teams, and other integrated items. Slowness or leak issue is a nut for the team now. Also, the team resolves or understands the network and query path every easy and resolves efficiently.

Our application uptime, increased by 10%, and overall productivity up by 30%.

Ticket or issue down by 12% over five years of use and experience.

Open to be applied and test any area and suite.

The tracing is the most important aspect of the solution. The way it traces the information within the particular application or within the particular infrastructure is great. That actually helps. Apart from that, all of the data that's in the production APM is good.  

Technical support is helpful.

The solution scales well.

The stability is good. 

We do have a combination of areas that need improvement. We do have the integration, such as end-user integration and experience that could be better. It is not just from the response point of view; it is more from the error and error detection point of view. This is due to the fact that these are all the banking applications as used by the banking staff, not by the end-user directly. Based on the banking staff feedback, based on the staff security or maybe dealing with the capital market, there needs to be some improvement.

They do provide the input growth on a daily basis in terms of what is coming in and how we receive the applications and how many we have. We've now started looking for a particular product that can make sure that it should connect with files and statements inside the product. 

The IO ratio, which we are looking for in terms of a report, is one of the concerns. We do monitor those details from AppDynamics, however, reporting and monitoring could be better.

There needs to be more analytics. That is what we are missing from the tool point of view. We need more information geared more towards helping us in making better decisions. When you do the coding that's for a banking situation or maybe in the incidents or capital market, it becomes very important that how much time I'm investing inside the transaction. A transaction which needs to be carried out for either confirming the payments or maybe either releasing the payments - these kinds of things. What I have seen with the use, as of now, is a bit of a lag when we are running on the global cloud or the public clouds, like Azure or the Google platform. 

Right now, we are fighting between three different stakeholders. With the networks, we have a different chat, with the vendors we have a different chat, and with the application team, we have a different chat. This approach doesn't provide a holistic view. Everyone has their own excuses and everyone has their own reasoning and conditions. 

If it can be able to intelligently provide all the things we need to look at, from a data point of view, that would be very useful.

I would say that I have between seven and eight years of experience, hands-on. However, later on in the time frame, over the last four or five years, I have not has as much hands-on experience with the tool. I'm more involved in various solution discussions and strategy building with the platform on top of the tool.

I would say it's very steady and for now, it's very reliable as well. It's stable. We don't have issues with bugs or crashes. 

The solution is very scalable so far in any testing scenario. It performs very well and gives us the expected output which we are looking to improve. 

We are using the solution for more than 600 small and big applications. We have around 78,000 people, including the back-end staff and the development team, that use the solution.

Overall, technical support has been very good. We're very satisfied with their level of support. So far, it's been very good for the bank.

Positive

We have used HPE BSM (now called MF APM). 

Due to these factors, we switch:

1. Costly

2. Implementation complexity

3. Multiple products and Integration

4. Not end-user friendly. 

I was not involved in the initial implementation. Nowadays, the way we approach the teams, sometimes it's very easy when it's an application with a known language like Python or maybe with Ruby or a kind of Java application. In terms of gateways inside the product, sometimes it is very tough, and sometimes it is very easy to get deployed. We're not using any out-of-the-box security. 

We have used model Train for the trainers and enforced all employees with operational training.

We achieve a great number, in terms of applications user availability increase by 30%. In treading, and agents, needs a smooth performance before the market starts. AppD provide a depth to measure any performances challenges, leak issue or even a chain linked issue story.

The pricing is a mixed bag. In some areas they are reasonably priced, however, in others, it's a bit expensive. 

We look for ease of implementation, diagnostics information shared, and controls to the team for working.

We're just an end-user of the product.

We're using the latest version of the solution. 

The deployment model depends on the solution or the size of the product which we are using, as the banks do have private and public clouds. In public clouds, we don't have much of the production instances. It's mainly the development. The free cloud and the cloud environment are completely on a private or in-house, on-premises solution with different ecosystems.

If a proper study has been done, and the solution makes sense for the company, I would recommend the solution. 

I would like to rate the solution at a seven out of ten. That consideration is mainly due to the fact that it covers a large portfolio of the product. It does have support for many other ERP tools. A lot of open customization is available and the product support team can help to customize the product. I've found this tool very useful and helpful on that.

The use case involves evaluating a mobile application's performance and user experience. We seek insights into peak usage hours, the application's status, and that of secondary services, such as databases and APIs, to gauge the mobile user experience.

We also want to identify potential bottlenecks and mobile degradation. We aim to ensure that mobile user monitoring is effective, similar to other forms of user monitoring. Although mobile devices present a different medium, they aim to detect errors, service degradations, slowdowns, and other issues. 

In the case of a mobile banking application, AppDynamics Mobile Real-User Monitoring successfully reduced the response time from eight seconds to just one second. In another example, the tool identified an issue within the mobile app, causing lost transactions in the billing system.

The product offers end-to-end visibility. This means seeing a user's actions, such as which mobile version they're using, their operating system, location, and the specific services they're accessing. This visibility allows for effective troubleshooting of their session. Additionally, end-to-end visibility provides insights into how the application performs across different layers, such as the backend infrastructure, including application servers, integrations, and databases.

The tool offers many entry points to observe issues from the backend, for example, through dashboards or tracking business transactions for degradation. You can then drill down to specific user sessions to identify slow ones and trace them back to the backend to understand the issue. That's the product's most useful technical feature. 

The user session tracking feature is embedded in the infrastructure and correlates all lines, including API and database calls. It also correlates with other metrics from the infrastructure and database.

The only improvement I see is intercepting calls in a mobile application without injecting additional code. Currently, when instrumenting or monitoring a mobile application, it's necessary to release updates, prompt users to upgrade, and inject code into the backend. It would be beneficial if there were a method to intercept these calls without requiring users to download and upgrade the application. However, I'm unsure about the feasibility of such an approach. 

Additionally, there's potential for enhancing the pricing structure, particularly as scaling up can become expensive. Given the continual growth of the mobile landscape, revisiting the pricing model could be beneficial. 

I have been working with the product for four years. 

I rate AppDynamics Mobile Real-User Monitoring's stability as nine out of ten. 

I rate the tool's scalability a nine out of ten. 

AppDynamics Mobile Real-User Monitoring's support tickets are tricky. We are a major partner, and we get instant support. 

Positive

I rate the tool's deployment a nine out of ten. It is easy. The deployment time for this solution is typically quite fast. Most typical technologies, such as Java or .NET applications, can take days. However, for more complex scenarios, it might take a few weeks. Overall, the deployment process is generally swift.

The usual deployment process starts with a technical assessment. Following this, the appropriate technology is acquired. Next, access to the client's systems is obtained, enabling the deployment of the agent onto their systems.

I rate AppDynamics Mobile Real-User Monitoring's pricing as seven out of ten. Mobile monitoring is paid based on the number of instances utilizing the mobile monitoring service, which increases as the scale grows. Consequently, your mobile user count can proportionally surpass all other applications.

Our customers for AppDynamics Mobile Real-User Monitoring are enterprises. If they have a critical mobile application, I think it's necessary to consider a monitoring tool. When your business relies on it, you need visibility into what's happening—peak hours, virtual access, performance, user experience, drop-off rates, conversion rate, and other relevant metrics.

Integrating AppDynamics Mobile Real-User Monitoring with existing mobile application infrastructure is generally straightforward, although there's room for improvement to make it even easier. I would rate it at nine out of ten in terms of ease of integration. However, sometimes, clients hesitate to interfere with their CI/CD pipelines. 

I rate the overall product a nine out of ten.