The most important part is the real-time network monitoring dashboard. It pops up when you log into the system so it gives you clear-cut, real-time availability of the firewall/gateway-level infrastructures.

My network team, the server team, and I have different dashboards. There is also a complaints manager who has different access. These different dashboards are important because we are in the life sciences domain, and segregation of duty is very important.

The role-based dashboards summarize data points as well as provide charts and topology diagrams in a single window. We support all other regions from India. Therefore, it is better that the dashboard is a single point of entry to each site, managing those infrastructures. 

The dashboards tell us the details. For example, even in the firewall, I can go to the port level. Then, on the port level, I can deep dive on the configuration. It will also go into the level of services, memory, CPU, and storage availability. From the dashboard, you can look at that specific infrastructure or asset.

The graphical user interface is very good. It is readable, which doesn't need a technical expert to do that. That is critical. You don't need a network administrator or some other administrator to see the monitoring or anything else. Non-technical people can log in and understand it. 

Infraon's individual tunnel monitoring capabilities are more critical on the firewall side because we have a lot of Point-to-Point Tunnels created. The tunnel usage is more critical when you have a ransomware attack or any other attack has happened. When I implement a policy for a particular configuration, it will apply to all the tunnels. That makes easy for us to manage or maintain. This is a very important feature.

The product is great. We integrated the ticketing tool with the monitoring tool. The agent ID creation is very easy when using this tool. It is so user-friendly. The user interface is good and also the pricing is great. 

The user interface is good, even a business user or layman can raise a ticket. 

They provide an all-in-one monitoring tool. If an issue happens, it gets integrated with the email, then proactively that ticket is being raised, which is good. 

The reporting is good. It is very clear. It is a customized report; however you want it, you can customize it.

We use the solution’s role-based dashboards. The head of IT wants to use it so he can see holistically what is happening, e.g., what are the tickets being raised, what is a major issue, and what escalations are happening. There are different dashboards that are customized. For our head of IT, we made a separate dashboard. Then, for the executives, we made a separate dashboard based on time, like hourly or daily. All these reports were customized.

While they didn't provide a BI dashboard, they provide a kind of graphical dashboard for whatever the issue is. Once you click on a particular ticket, it drills down to the issue, what it is and when the issue was raised. The drill down is good. It is more like a business intelligence (BI) tool. You can just scroll and zoom in. It goes deep into the issue. Once you click a particular dashboard, it will take you to the next page, then it takes you to the issue.

Infraon IMS provides workflow automation for real-world use cases. This makes our work easier. It is just drag and drop (no coding) to build the workflows. For example, a particular ticket is being raised. It gets routed to three important IT executives within our team. From our team, it gets routed to the next level. 

The learning curve is good. Initially, there were no issues. As soon as the users saw the product, they understood what the product was. There wasn't any kind of training required for this product because it is very straightforward.

The most valuable feature is alerting. We get email alerts when a link is down that tell us which device is having a problem.

The granularity of the reporting works well for us.

What I really like about it are the details that it provides whenever we click an icon or any of the objects on the dashboard. We get a detailed description. We're running 200-plus VMs in our infrastructure. If I click on any of the symbols I can see detailed information about a VM: the traffic, the resources utilized by that VM, and whether the SLA is being met by that VM and the services. That is visible on the dashboard. It's just a few clicks and you get all the details as required.

There are role-based access policies defined for our employees. For example, at the L1 level, we define the policies that they can view and the devices they can access. They can only view them, they cannot edit. Our higher-level guys can edit, add devices, and they can create multiple dashboards as required. This is important because each person in our NOC or our data center has specific, targeted goals. Some of the network admins only require seeing network traffic utilization. Some will require port utilization. They may require specific ports and specific devices to monitor a single application.

For example, we have a database system and we need to monitor the underlying network infrastructure related to it, as well as the application related to it. We created a customized dashboard and handed it to the application custodian or database custodian of that system so that he can get an overview of the condition of all the infrastructure that he is using.

We have set a role-based access policy for network admins and network operators so they will only be monitoring VPNs, network device connectivity, and all the tunnels. We are connected with multiple internet service providers, so we can monitor which of them is using a lot of traffic and where the traffic is coming from. 

The role-based dashboards provide data points and charts and topology diagrams in a single window. It's like a spider web, where the application, connectivity, and everything is defined for each user of those applications.

The granularity that Infraon IMS provides to us is really spectacular. If we see a VM in what may be an unhealthy state, we drill down and see what the issue is, whether it's a memory issue or a CPU issue, what time it was triggered, and how it was recovered. All these kinds of measurements are available via drill-down from an events list base.

In addition, the GUI is very interactive and customizable, because the dashboards are customizable. There are two parts to the GUI. One is the operation part where we can see reports and customize them. The other is the admin part where you can add devices. That has to be very quick because we are adding new devices every day, and it is very helpful. We are pretty satisfied with the GUI.

We were also amazed by the reporting capabilities. Previously, we were using open source monitoring systems, like Nagios and Cacti, and we were having a hard time with them. You need to customize each and every module and every parameter to generate an intuitive report view and a summarized query. So getting analytics or doing capacity planning was difficult. With Infraon IMS we're happy with the number of reports and the granularity. And its summarized view of the infrastructure helps us in planning.

Their discovery is very quick and they have a CSV file upload mechanism that allows you to onboard five thousand devices a day.

One of the most valuable features is configuration backup. If any changes are made subsequent to the backup then we are notified.

The reporting capabilities are good. If anything is wrong then I get an immediate email that contains the log.

Once the initial setup is complete, using it on a daily basis is easy. The initial learning curve is steep.

It is a stable product. After the initial configuration, you don't have to tweak it much. All systems of Everest IMS work perfectly.

Being an engineering product, the customization is easy for us compared to SolarWinds and ManageEngine.

It's a total integrated package. The feature that I like the most and the best part is the customization.

This product integrates well with any platform, and I don't see any issues with it.