When discussing network devices, for example. When you enable network monitoring, you should be aware of what is being monitored, such as devices, switches, and hubs. You must be aware in order to enable monitoring, but when you try to discover a device within ScienceLogic, it performs granular discovery. You don't have to worry about which location, site, place, or subset or subset of devices is installed or placed. It performs granular discovery.
We know when we talk about certain appliances, such as XClarity or certain Cisco appliances or other appliances, many nodes or hub switches, servers, and devices are connected to a single hub in an appliance. When you find a specific appliance, it will perform a granular discovery until the last child is found. If you try to find a parent, it will only find up to the last child, which is not the case with other monitoring tools. This is one of ScienceLogic's best features.
This happened in our previous company's environment, they didn't have a proper inventory where they could have given us the details of devices, hubs, and switches, because if it's a large company with a large infrastructure, they rarely get to have an updated inventory. It is extremely difficult to obtain each and every inventory when working on such projects or transitions. That's when ScienceLogic came up with this granular discovery, in which it discovers each and every child within that specific parent, appliance, or device.
As a result, we were able to return a report. Essentially, ScienceLogic is used as a reporting tool. Instead of giving us the inventory, we ran a report after the entire discovery to show the customer, what they have in their environment that they were not aware of. It was a nice thing to boast about because they were unaware of their inventory, but we were able to provide them with that inventory.
Another application was to use ScienceLogic as a source of truth. When we say the source of truth, we generally refer to CMDB in large environments. When we go for ticketing or any kind of event management, it generally refers to the CMDB, pulls the data, pulls the server information, drags it to the ticketing into the system, and it provides all the details in the ticket.
But sometimes the CMDB is not updated, either because it requires manual updating or because someone is attempting to upgrade or update it through some script or something, and somewhere, there is a miss. However, when we use ScienceLogic as a source of truth, there is nothing to miss because whatever is discovered within ScienceLogic can be used as a source of truth. Essentially, ScienceLogic would have the information that CMDB does not have.
These were two cases, test cases, or things that we came across. And we were overjoyed to offer the customer the solution, that they could use ScienceLogic as a source of truth, instead of referring to CMDB. That's when we suggested that they integrate ServiceNow with ScienceLogic and use ticketing instead of a CMDB. At the time, we had completely removed CMDB. Maintaining CMDB is also an expense. We actually save the customer money with the help of ScienceLogic.