ManageEngine OpManager MSP

Pros: I liked that OpManager MSP had separate performance analysis of each customer’s networks in an efficient manner. Layer 2 maps helped me to visualize layout of the infrastructure ease because of the auto-discovery engine it included.

Cons: When using certain elements of SLA reports, I realized that some of the templates provided to me were somewhat limited.

Pros: OpManager MSP immediately understood the traffic trend for each client and then helped me set appropriate limits. Using the backup feature in the network also helped me a number of times whenever a failure occurred in the device.

Cons: The frequency at which the automated network audits are conducted may not be very rigid in their scheduling.

Pros: I specifically like the way ManageEngine Applications Manager helps in the monitoring of applications. It assists me in tracking diversified information across various platforms, whether servers or particular applications, which aids in diagnosing issues and enhancing overall performance swiftly.

Cons: There several restrictions when it comes to modifying reports for certain requirements.

Pros: The best about OpManager MSP is the extent of the custom reporting and display feature. It enables me to offer several specialized client reports that target significant figures in the network and maintain clients informed about their network health.

Cons: One of the challenges I have faced is the time it takes to set up multi-client alert system. It is also a challenge to set thresholds that are unique to each client network due to the difference in infrastructure.

Pros: I like especially one feature in this OpManager MSP and that is the degree of the performance review offered to aid in monitoring the performance. It enables me monitor networks’ status of various clients in real time hence giving me an advantage when it comes to timely detection on potential downtimes.

Cons: A downside is that there is sometimes a delay when auto-populating the fields in SQL View Map. Several times when adding new devices or networks, it may take some considerable amount of time to auto detect and create categories.

Pros: Since OpManager MSP can track numerous network resources, ranging from routers to virtual machines, the solution presents a broad picture of client networks. This comprehensive oversight is the reason why most unforeseen problems can be effectively prevented on time.​

Cons: It affects the discovery phase of the system because it misidentifies some devices and the user has to manually categorize them. Reducing the device classification time will in fact cut down the equipment setup time.​

Pros: The use of dashboards in OpManager MSP is very useful since one may customize the view for each client according to the client’s preferences. This personalization facilitates quick identification of issues and informed decision-making.​

Cons: Creating the generalized reports from records of history can be slow, most especially if large groups of data are involved.

Pros: OpManager MSP offers the best means of assessing the health of devices and network traffic as well as topology, and I can identify problems with solutions proactively. It makes me have a clear view of the networks of my clients in the real time.

Cons: I have come across the reduced capacity for event management on a large scale.

Pros: It would be desirable when using networks to monitor them without being restricted with location. OpManager MSP comes with multi-site monitoring, which gives the clients a chance to identify network problems before they become leaning towards an outage.

Cons: Periodically the auto-discovery functionality does not adequately reflect the current state of the devices.

Pros: The Manage Engine OpManager MSP is ideal for network monitoring since it allows one to monitor issues before they complicate by offering a broad variety of solutions. It assists in the control of many connected client networks, with continuous monitoring and the capability to alert when there is an issue that requires intervention.

Cons: Sometimes I have had to wait for a while to receive notifications on real-time alerts. It takes quite some time at moments to prompt alerts of the network events meaning that during critical emergent incidents diagnosis may be slowed down.

Pros: OpManager MSP supports a proper range of devices from the multiple vendors to make the work of the system effortless. The numerous device templates also help in quick implementation along with ensuring that all the devices being monitored are standardized.​

Cons: To develop templates I had to search for them on the Internet and set up the devices by myself. Expanding the existing template library helps to avoid such challenges.

Pros: OpManager MSP provided some benefit in when it came to allowing different monitored groups per client depending on the thresholds, schedules and report settings. It allowed for dealing with both big and minor clients at the same time, without affecting the primary processes.

Cons: When implementing new clients for those who already possess some infrastructure, the discovery engine misses some less popular SNMP-enabled devices unless I supply OIDS.

Pros: What I like most about OpManager MSP was its capability of monitoring dispersed networks. With the help of the probe, one can analyze the performance in each client location without installing full-scale monitoring servers and it helped to save our overhead.

Cons: The network mapping tool distorts various link statuses especially in other branches. There was actually no correspondence between the plotted nodes matrix and the real one, and to diagnose links degradation it created some confusion.

Pros: The system has its alerting feature which is another powerful feature implemented by OpManager MSP. It allows for customizing response actions by criticality level and also by defining client-specific SLAs. It provides me with that level of detail in fulfilling my contract which does not require constant monitoring 24/7.

Cons: I realized that it just does not commence turning on alerts directly after a maintenance window without another manual update.

Pros: From the experiences I have had with OpManager MSP, I was able to realize that the policy-based monitoring profiles are very useful. With these, I can create templates that apply to many client environments so as to have standard performance.

Cons: One issue arises with the option of adopting role-based access of junior technicians for certain client groups.

Pros: I like how OpManager MSP is able to compartmentalize large IT environments into unique customer instances but still provide a single point of access. The asset lifecycle management and the bandwidth tracking tools have especially been effective in resource planning for the long term.

Cons: In some cases the ‘live graphs’ do not update properly during high traffic periods. On the down side it slightly delayed my chances of identifying the actual time of congestion through the network whenever several clients were on the network load.

Pros: The approach OpManager MSP adopts in terms of specifying performance thresholds, notification profile and escalation chain per tenant makes it impossible for issues to go unnoticed. I can restore the faulty server anywhere between a few minutes of the downtime being noticed.

Cons: It seems occasional failure when applying configuration backups between multiple clients due to slight difference in the device firmware version. It does not alert you to any incompatibilities and this led to trial and error repeatedly.

Pros: Based on my work experience, I consider real-time performance dashboards and customizable client views as the most helpful. OpManager MSP enables me to sort out the alerts and resources separately for each individual client. The other benefit of the fact of the automation profiles is that the repetitive fault responses are easy to tackle.

Cons: There is a constraint while creating SLA reports for clients having mixed infrastructure. If a client has hybrid environments, devices are not separated accurately and I had to add filters to turn of unnecessary metrics.

Pros: I liked how OpManager MSP offers full visibility into the multi-client environment without having to switch between tools. I was able to respond proactively in real-life outage scenarios by segregating the devices based on the client accounts and alert settings and having automatic alerts for above-specified thresholds.

Cons: One of the challenges that I have come across is compatibility of SNMP credential in case clients have overlapping IP space. It can sometimes apply credential improperly which results in little disparity in the monitoring data.

Pros: OpManager MSP has a nice integrated feature of monitoring WAN link which has assisted us in determining ISP problem before the client complains. It is this capability to assign probe agents and then measure latency and packet loss at several different points that our support offer.

Cons: If I want to compare the usage of links in five clients, I need to go to each tenant’s profile individually which is an extra step.

Pros: I can monitor factors such as latency and packet loss through OpManager MSP and fix problematic issues before they become a concern for the clients. This has enhanced the team’s ability to manage the various client issues as well as made clients more satisfied with our services.​

Cons: Some vendors did not have their MIB files supported out-of-the-box and so, I had to load it myself, which was time consuming.​

Pros: The ability to manage several client networks from one interface is highly efficient. The multi-tenant feature in OpManager MSP makes it easier for me to view the CPU or memory usage of diverse clients without having to change contexts.

Cons: Despite the fact that the alerting is very effective, the alerts take time especially when there is a huge traffic.