There is no centralized database. It is an issue if you use a local database and have multiple borders. However, if you have an external database, you can keep the same old data from an old border up to 100 borders. In addition, if we want to create an ABI or use an ABI to connect data, there is no competition when we ask for support. If we want to modify the calculation matrix or equation, we have to raise a professional service. Other competitors like Micro Focus, a network management system, have a new supportability matrix in the market every quarter.
In the most recent versions, Entuity has removed the Explorer navigation feature. This was very useful, and Entuity would be improved by restoring it. Entuity's internal coding also tends to lag and crash. In the next release, Entuity should add support for more devices.
Entuity can improve the fetching of device configuration. The solution uses scripts and I could not understand them or find any recourses on the internet to learn about the language that is used in the script. It could be more user-friendly and the device configuration management could be enhanced. In a future release, it would be useful if they could add a packet sniffer. that could perform a deep packet inspection in Entuity instead of doing it with another solution.
The configuration of the logging could be improved because if someone deleted any note or inventory, or some change to the inventory, we are not able to identify which user or which administrator modifies these details. For example, there should be read-only locks on maps to prevent their deletion. This way people can only read and cannot delete that particular map. There is room for improvement in the integration with other tools, such as firewalls and other networking tools. All the traffic should be directly visible with the help of Entuity because nowadays we require very particular dashboards for the visualization of network traffic. The geographical map should show which IP address belongs to what and from which area and the communication that happens. This kind of interactive dashboard should be there for the mapping visualization of communication. This way I would be better able to visualize what is happening in the network.
Entuity could improve by having more integration because now network management is not a standalone solution. You have to integrate it with your network, applications, and everything else. We have to collect that information from those solutions or relevant managers. Additionally, the SLA dashboard should be improved. The integration point is very important because there are a lot of third-party, open-source, solutions on the market, such as Kubernetes, and until you pick up the data from one of them, they cannot be correlated and you cannot currently have the comprehensive single dashboard that is required.
It is pretty straightforward and pretty easy to use. What might be improved for the user may be the depth of insight into the events that do happen and the ease of integration. I'm sure the typical user may want to enhance the reporting side of things as far as the depth of reporting and ease of doing so. It could be easier for the end user to do integration. The perfect solution will do everything a user needs, right from covering networking to servers to end users. It would just work end to end. That type of coverage comes at a price. Finding a balance between the price point and coverage is where any monitoring solution out becomes a stumbling block. The end user needs to find a solution that balances between the coverage and price. It would be nice to have one solution that does everything that was inexpensive. That may not really match with those who have a budget.
Entuity network management software continually monitors network bandwidth, network error rate and network congestion, which are all factors that impact overall network throughput. Events can be raised in response to abnormal traffic to allow remedial action before users are impacted. The Entuity network monitor continually evaluates network latency and network jitter to calculate MOS and ICPIF scores. Events can be raised when these scores are unacceptable for business application, voice and...
Entuity could integrate with other solutions and collect more information from IoT devices.
Entuity can expand its coverage on monitoring VoIP solutions a little bit more.
There is no centralized database. It is an issue if you use a local database and have multiple borders. However, if you have an external database, you can keep the same old data from an old border up to 100 borders. In addition, if we want to create an ABI or use an ABI to connect data, there is no competition when we ask for support. If we want to modify the calculation matrix or equation, we have to raise a professional service. Other competitors like Micro Focus, a network management system, have a new supportability matrix in the market every quarter.
In the most recent versions, Entuity has removed the Explorer navigation feature. This was very useful, and Entuity would be improved by restoring it. Entuity's internal coding also tends to lag and crash. In the next release, Entuity should add support for more devices.
Entuity can improve the fetching of device configuration. The solution uses scripts and I could not understand them or find any recourses on the internet to learn about the language that is used in the script. It could be more user-friendly and the device configuration management could be enhanced. In a future release, it would be useful if they could add a packet sniffer. that could perform a deep packet inspection in Entuity instead of doing it with another solution.
The configuration of the logging could be improved because if someone deleted any note or inventory, or some change to the inventory, we are not able to identify which user or which administrator modifies these details. For example, there should be read-only locks on maps to prevent their deletion. This way people can only read and cannot delete that particular map. There is room for improvement in the integration with other tools, such as firewalls and other networking tools. All the traffic should be directly visible with the help of Entuity because nowadays we require very particular dashboards for the visualization of network traffic. The geographical map should show which IP address belongs to what and from which area and the communication that happens. This kind of interactive dashboard should be there for the mapping visualization of communication. This way I would be better able to visualize what is happening in the network.
Entuity could improve by having more integration because now network management is not a standalone solution. You have to integrate it with your network, applications, and everything else. We have to collect that information from those solutions or relevant managers. Additionally, the SLA dashboard should be improved. The integration point is very important because there are a lot of third-party, open-source, solutions on the market, such as Kubernetes, and until you pick up the data from one of them, they cannot be correlated and you cannot currently have the comprehensive single dashboard that is required.
It is pretty straightforward and pretty easy to use. What might be improved for the user may be the depth of insight into the events that do happen and the ease of integration. I'm sure the typical user may want to enhance the reporting side of things as far as the depth of reporting and ease of doing so. It could be easier for the end user to do integration. The perfect solution will do everything a user needs, right from covering networking to servers to end users. It would just work end to end. That type of coverage comes at a price. Finding a balance between the price point and coverage is where any monitoring solution out becomes a stumbling block. The end user needs to find a solution that balances between the coverage and price. It would be nice to have one solution that does everything that was inexpensive. That may not really match with those who have a budget.