To some degree, all the products do this. But ProactiveNet automatically creates performance thresholds and correlates devices into groups. As a device is added to ProactiveNet, it's categorized as an application server, Web server, mail server, router or switch, and then monitored based on further definitions, that could, for example, include MIB II, Host MIB, Enterprise MIB or Oracle SQL query data. The list of monitors is extensive. These thresholds determine what is normal or average over time and can be changed, though ProactiveNet recommends waiting until you've collected data for a few months and know how the thresholds are affected. We left them as is. The software also filters out unrelated data. Using the groupings and time-based correlation, ProactiveNet lists root-cause suggestions in order of decreasing likelihood.
ProactiveNet's second, separate set of static thresholds generate user-defined alarms. All the products we tested can set these types of alarms. Crossing a static threshold's value creates an event (such as "Threshold has been violated") and an alarm. We easily changed this product's canned thresholds to fit our testing environment.
We collected Web transaction data and ran it across a simulated WAN connection while we periodically overloaded a Web server. ProactiveNet accurately pointed to the slowdown on the server as the most likely problem, and then pointed to the increased utilization on a shared switch prior to the server. Without an agent on the server, ProactiveNet incorrectly identified the switch link's utilization as the problem. If you can't implement the server-side agents, be skeptical of the root-cause diagnosis.
At the top level, ProactiveNet reports on alarms and performance health. The alarm display clearly indicates problems without overwhelming users with excess data. The initial page shows a matrix of devices and monitored services. A green dot indicates the device is fine with the service listed; if something is amiss, a yellow or red icon appears and links to specifics, such as graphs and checks.
|
|
ProactiveNet lacks flexible client-side scripting, offering just two flavors. Both support Web transactions and network service checking of UDP and TCP ports. The first version, a standalone agent, runs the port checks and transactions and reports to the ProactiveNet server. The second acts as a proxy, gathering statistics like a midlevel distributed manager, focusing the data collection and reducing the upstream reporting to the ProactiveNet server. Ideal for gathering statistics on the other side of a constricted WAN circuit, this proxy function decreases the ProactiveNet server's traffic and reduces the bandwidth needed to support several distributed agents.
To realize the benefits of cloud-native software, an application must actually be cloud-native—designed to run in the cloud, interacting with disaggregated cloud services, fully manageable as code—to deliver the expected benefits.
By combining resources and expertise, the AI-Enabled ICT Workforce Consortium will offer a blueprint for how industries can adapt to an AI-dominated future.
IT leaders should heed the guidance of cybersecurity insurance providers who think businesses should prioritize security education, incident preparedness, regular internal audits, and ongoing vulnerability scanning and patching.
