We at Revalsys Technologies had 50+ projects running in our servers. The business as usual also included monitoring all these servers and the devices that went with it. As security attacks or network device instability could occur at any part of the network, every device had to be monitored with equal priority. Any, unexpected behaviors or suspicious activities need to be quickly acted upon by alerts or tickets. To know the memory usage, performance, traffic and CPU usage for proactively knowing the health status of the network was also a business need. There were several tools which were available and could dedicatedly do each task, but the challenge was to design a One stop solution to all the above problem.
A long search just ended up knowing that there were not much tools available in the market which could actually meet our requirement. That was when our research team decided, “Why not we design one”. But the journey could not be simply stated in a word as “design”, as it was an entire cycle of whole product engineering, beginning from ideation to execution. After several months of research, the road map and the design was laid. The tool was to be engineered such that, it could communicate to all the devices in the network starting from a Desktop to a Cloud Server, collect the device data from time to time, accumulate it in a quick access repository, process all these data and display the graphs/reports.
The first challenge was to check the compatible communication methods that could be feasible to request information to all devices and to receive them. Once all the communication protocols were finalized, the next challenge was collecting all the chunks of data. On an average, an environment with 40 devices and communicating through WMI, could accumulate 25lakh event information with each event data ranging from 1KB to 2MB.
These readable data need to be displayed as intuitive graphs or reports for a quick trend analysis. Once these algorithms were crafted the next task was to put them all in one package where even other essentials for network device security like alerting, reporting, logging and ticketing could be integrated. The product was coded. But how do we test it? How do we check its scalability? That was the next challenge which took us umpteen trials to stimulate a test environment; after which we could create one and successfully put together all the pieces of the puzzle.
Finally, in June 2015 after months and years of research, innovation and engineering, our product iReveal was market ready which could
For more details about our product iReveal