Our primary application of this solution revolves around IT infrastructure monitoring. We focus on alert consolidation from core network and service levels to enhance our service management framework.

There are many purposes for which ManageEngine Applications Manager gets used in our company. If I have to list a few use cases of the solution, it would be more on the application modernization part and the monitoring of the performance of those applications. If you want to know something specific, then maybe I can drill down into it.

The primary use case is for services and incident management.  

I am a user as well as a functional person who understands the process, suggests flows, and asks ManageEngine some announcement queries. I internally guided the team through the asset module, problem module, incident module, and change module implementations. That is something I did the last year.

My use case for ManageEngine Applications Manager is monitoring.

We are resellers of this solution and I'm the enterprise senior account manager. 

We are using the latest version of ManageEngine Applications Manager. We recently updated it. We are monitoring the performance of the GMR service using the Application Manager. We can collect the JVM parameters and that helps us to analyze the heat memory without even going into the missions or the servers. We can also monitor what other processes are running and check which one is occupying more memory. And we can also set the alarms, automatic alarms like email alerts, if something crosses a threshold. We monitor 1200 users and 25 servers with the Applications Manager.

We use the ManageEngine suite in many dimensions. We not only use it for application monitoring and troubleshooting; we also do our services through this suite. We manage services in general, and to provide our services, we use the ManageEngine suite. Depending on what a customer needs, we put different modules and applications. Sometimes, the customers buy the solution or software, and sometimes they buy just the services. We put the software as a service. 

The main product that we have here is for a banking client, and they have the latest version. Its version, however, varies based on the customer. In general, it is deployed on-premises, and our big customers require it in data centers. We hope to be in the cloud soon.

Normally, the customer uses ManageEngine to monitor an application by inserting it into the IBM solution from the back-end to find out the root cause of any application problem. 

I use ManageEngine to test-compile my products. Sometimes I use it for the summary clips with CF quotas. My experience with ManageEngine is primarily with the application performance management side. 

I also use ManageEngine to research and compare CF quotas and then appraise them so I can propose to the customer which solution is suitable for their organization.

For a small organization, I think ManageEngine is pretty nice, I think it's enough.

We use this solution for application monitoring.

We have an on-premises deployment model.

It is used primarily to monitor applications. 

The primary use case is for monitoring SQL and nodes.