Nlyte Lights Up My Hosting Center Floor
Rating: 8 out of 10
February 12, 2019
Vetted Review
Verified User
2 years of experience
Nlyte is being used by the Data Center Operations group within my organization. We use Nlyte Asset Optimizer (NAO) to track every asset in our hosting centers. We also use Nlyte Energy Optimizer (NEO) to monitor the hosting center environment. These two modules can be integrated so that if an alarm occurs in NEO, NAO will show us the exact location of the asset causing the alarm.
- Nlyte Asset Optimizer (NAO) tracks every asset in our hosting centers and when integrated with Nlyte Energy Optimizer (NEO), which monitors the hosting center environment, we can see, at a glance, the asset causing the alarm and its exact location in the hosting center. This is a strength, as it provides for faster resolution of problems if/when they occur.
- Nlyte Asset Optimizer (NAO) has a lot of built-in reports that are great for looking at. For example, servers of a specific brand, or how many Us are taken up by servers. I see this as a strength and use this capability for capacity planning.
Cons
- Nlyte Asset Optimizer (NAO) is currently all manual entry of assets. It would be great if NAO could provide for automated discovery of hosting center assets. This automation would be limited to ICMP and SNMP communication so not every asset can provide automated discovery, but it would be great for all IP addressable devices.
- Nlyte has had a positive return on investment (ROI) for my organization. A big factor in the ROI is having faster resolution times when alarms occur.
I am still using the other three products as they have features that Nlyte does not have, and that are really out of scope for Nlyte. I can give one example because this product is an in-house application. It is our CMDB application, and it interfaces with several other in-house systems to provide data that Nlyte is not designed for. Example: If we get an alarm from a server, and if there is currently a planned outage with a Request For Change (RFC), we ignore the alarm unless it exceeds the RFC window.