ServiceNow Discovery finds applications and devices on your network, and then updates the CMDB with the information it finds. Discovery is available as a separate subscription from the rest of the Now Platform.
| Type | Title | Date | |
|---|---|---|---|
| Category | IT Asset Management | Jun 1, 2025 | Download |
| Product | Reviews, tips, and advice from real users | Jun 1, 2025 | Download |
| Comparison | ServiceNow Discovery vs ServiceNow | Jun 1, 2025 | Download |
| Comparison | ServiceNow Discovery vs BMC Helix Discovery | Jun 1, 2025 | Download |
| Comparison | ServiceNow Discovery vs Qualys VMDR | Jun 1, 2025 | Download |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| ServiceNow | 4.3 | 20.9% | 92% | 220 interviewsAdd to research |
| Zabbix | 4.2 | N/A | 95% | 106 interviewsAdd to research |
We used the product to manage our desktop assets. We were expanding it to use the rest of the technology assets. The technology assets would be populated from Tanium. It is an incredibly valuable tool for what we need.
The service management and operations management modules are valuable.
The product could improve some of the visualization and architecture setups.
My previous organization used the solution.
I rate the solution’s stability a ten out of ten.
I rate the product’s scalability a ten out of ten. When I left the organization, 75 people were using the solution.
The initial setup was relatively straightforward but required the organization to have its policies and core processes defined. For building it out, ServiceNow gave us a basic set of processes that we can employ. However, these processes, like any SaaS tool, rarely work out of the box and require modification in order to work for an organization’s culture and practices. I knew that, so I designed those myself. We were ahead of the game, but it would have been much more difficult if we had just assumed and tried to enable their out-of-the-box solution. It required internal work.
The initial deployment took less than five months. We used a hybrid method to implement the solution. We used a third party, and internally my NOC manager became my architect. He was also the one that became a developer of the system.
If the solution is deployed properly, it is highly valuable. If the product is not deployed properly, it can be very expensive.
We used ITSM and portions of ITOM. ITSM is for incident, problem, change, and knowledge management. We also built asset management modules. Specifically, we built that module for all the desktop services I was responsible for. We were building it out to support all of the IT technology assets. We also built a custom security solution within the system. We're also building our compliance and integrating it with our internal HR solution.
My goal was to move the organization from a lot of individual solutions for each business unit to one enterprise-level solution that managed issues, problems, and changes across the entire enterprise. We wanted the product from an infrastructure perspective and integrated it with HR and security. We hadn't yet integrated it with the application stacks up to the point that I had left. However, we established enterprise-level dashboards from the executive level down to the front lines to manage tickets related to issues and problems. We wanted to leverage data to analyze the biggest challenges we had and the improvements that we were making.
ServiceNow is an incredible tool if managed right. The value of the tool as long as it's utilized properly is incredible. It provides a one-stop shop for a lot of things. We used all the elements of ITSM. We worked through most of the issues, like process changes and stuff like that. We deployed and modified it. The teams I worked with were incredibly responsive. People investing in the product must map their processes and understand their data flows. It's incredibly important. The more the internal policy process and data flows are defined, the better and the easier the deployment is.
Overall, I rate the solution a nine out of ten.
