ServiceNow Discovery Reviews

Our company uses the solution's to discover infrastructures. The ServiceNow instance is in the cloud and the Discovery servers are on-premises. 

We have five licensed configuration management practitioners and 3,000 end users. 

Cloud Discovery is valuable because it finds global, public cloud infrastructures and updates the integration management database, service catalogs, and asset management details. 

The store is a key differentiator because it offers many compatible third-party and OEM plugins for cloud integrations like AWS, Azure, Adobe, and Microsoft. For example, there are service providers for license and asset management, there is a mid-service for Quantum Discovery, and there are plugins from AWS for service or asset management and CMDB integrations. 

The solution too high priced. 

I have been using the solution for seven years. 

The solution is stable but some work is required. 

Only IP-based assets are discoverable. It takes time to get the related OIDs for newer models and patches do not come easily. Sometimes, we have to do research and discovery from the OEM's website to understand and manually create the required OIDs so the solution can identify the actual assets. 

Our main challenges are with network devices for Meraki and proper discovery for storage or backup solutions. 

The solution is very scalable. 

Technical support is always helpful. 

The setup is a bit complex. 

We implemented in-house which can be done if you have administrator or architect-level knowledge. 

Our implementation took ninety days. We went from on-premises Windows and Linux to Windows desktop laptops, to AWS, to Azure. The last step was SaaS integrations for applications like 365, Adobe Cloud, and Creative Cloud. 

The solution is very expensive. Our use is somewhere close to 50GB per user each month. 

We evaluated Manage Engine's ServiceDesk Plus, Jira Service Management, and Remedy. At the end of the day, the solution was the best fit during that time for our organizational strategy. 

Right now, we are looking for an alternate because the solution is very expensive. 

I recommend the solution and rate it an eight out of ten. 

We use the solution for configuration management.

Compared to other solutions, it is easy to implement.

The solution can prioritize the discovery of IP ranges. The product automatically places all Discovery CIs into the correct class within the CMDB.

Pricing could be improved to better accommodate various customer needs and business models. It ultimately depends on the specific requirements and budget constraints of each customer.

I have been using ServiceNow Discovery for eight months.

Compared to other solutions, the support is good. It's very fast and comprehensive. We have great integrated support from our community.

Positive

The initial setup is very simple and takes eight hours max to complete. It is a subscription module.

The solution is expensive.

I rate the product’s pricing a seven out of ten, where one is cheap and ten is expensive.

ServiceNow Discovery enables us to efficiently implement and discover all our assets within the organization. It's agility and ability to provide comprehensive information with correct CI relations and ServiceNow Service Catalog offerings. Compared to other solutions, it's easier to comprehend the entire structure.

It retrieves accurate information from the CIs within the company, establishing correct relationships with users, owners, and other processes such as incident and change management. It also improves the relationship between the CMDB and all the infrastructure components.

There are some specific challenges, such as discovering VIPs or Citrix machines, these issues are manageable. ServiceNow offers integration with third-party products through REST APIs and predefined connectors, facilitating seamless interoperability.

Overall, I rate the solution a ten out of ten.

ServiceNow Discovery is useful for discovering the servers, like the servers of Windows and Linux, from the client network.

Every single feature in every single version of ServiceNow Discovery has been valuable. The worthiness of a feature depends on our requirements. Every feature is unique, and every feature is important in the solution.

We can push some generative AI content to make ServiceNow Discovery more effective, but it's just a random thought. There are no particular use cases because of which the aforementioned changes need to be incorporated in ServiceNow Discovery. Debugging is a bit tough in ServiceNow Discovery, so debugging should be made very easy. Debugging should be made easy while developing the debugging pattern in ServiceNow Discovery.

I have been using ServiceNow Discovery for five years.

Stability-wise, I rate the solution a nine out of ten.

It is a scalable tool since it is deployed on the cloud, because of which there are no issues with scalability. The scalability of the product may depend on some subscriptions, which may be a challenge since one will have to invest money. If we remove the financial part, the product's deployment is quite easy.

It is a very scalable solution. Scalability-wise, I rate the solution a nine out of ten.

The technical support of ServiceNow DevOps can be challenging because we need to train the resources. If the resources don't receive the right training, and if one doesn't know what needs to be done during a particular scenario, then it can lead to a disaster for an enterprise. Proper training is required before using technical support since then only we can make sense of the support we expect to receive. We need to define a proper process for technical support, like whether it will be L1, L2, L3, or L4. The process should be very clear, and the right information should be provided to the right stakeholders. ServiceNow need not work on support because it is a tool. In ServiceNow, it's all about defining the process and training technical support, which is quite easy. The nuts and bolts required for technical support are catalogs, service requests, and incidents. I rate the technical support an eight out of ten.

Positive

The initial setup phase for ServiceNow Discovery was hard because a lot of communication had to be done with different stakeholders to understand their infrastructures and processes, which can take time. As a technical person, the installation of the product is just a matter of a few hours, but before that, we need to do a lot of exercises that are quite challenging. A lot of documentation needs to be done, and then we need to understand the perception of the stakeholder and what their expectations are, which can get challenging.

I rate the setup phase a seven out of ten.

The solution is deployed on the cloud.

The deployment process for the product is easy.

One needs to be more proactive and try to understand ServiceNow Discovery's process deeply. ServiceNow offers a similar offering for every client, and they have a similar kind of offer if one wants to install it, but every organization has a different process. There is a need for focus to understand an organization's process and stakeholder requirements, and vision.

Overall, I rate the solution a nine out of ten.

Our primary use case for the solution is compliance, understanding our assets, and mapping it against our business for services.

The ability to build CI relationships against our portfolio, services or applications is valuable. It has given us an understanding of each layer from a server application, network and the topography of how it's linked to an application or business process.

The price could be lower.

We have been using the solution for approximately four years.

The solution is stable. We've had some hurdles because whenever we changed networks, IPs or hardware, we forgot to ensure it reflected in ServiceNow Discovery. So we've added it as part of our process, but the solution has been stable. I rate the stability a nine out of ten.

The solution is scalable. Twenty-five people are currently using it in our organization. I rate the scalability a nine out of ten.

We haven't had many instances where we connected with support but when we have it has been a good experience. They provide a resolution within a good time frame. I rate them a nine out of ten.

Positive

The initial setup is straightforward. We initially had challenges because we had very tight security and firewalls that were a bit off, so we had to set up many rules around it to ensure the solution worked. Deployment took approximately three months.

We implemented through a vendor team, specifically by an integrator FlyForm.They are one of the best integrators we have used.

The solution is a good product, but it is slightly expensive. It is one of the most costly applications in terms of subscription costs. I rate the price a five out of ten.

I rate the solution an eight out of ten. The solution is good, but the price could be lower.

You can use it for network resources, servers, databases, and network gear. I've also used it in the past for asset management to discover desktop equipment, laptops, and peripherals.

It's pretty robust, and it's agentless for the most part. So, you don't need to deploy agents, which makes it a lot easier to stand up.

It's an expensive platform. In terms of features, it's pretty functional. You could always tweak it, but I don't have any problem with it. I don't find it to be at a disadvantage compared to something like SCCM, Intune, or any other tool that can do discoveries.

It is very stable. We have no problems with managing it and it being available for us.

It definitely seems very scalable. With it being agentless, you can set it up for IP ranges, and it'll go do what it needs to do. You don't have to implement it with agents to keep monitoring.

We have about 75 people who use this solution.

It was pretty straightforward.

It costs a lot. It is probably close to over a hundred thousand. It's an expensive platform, but you can't compare ServiceNow's Discovery functionality to other discovery tools. It's not an apples-to-apples comparison of ServiceNow to a configuration management tool to an asset management tool because it does those things, but it's not those things.

If it's too expensive, there are definitely a lot of alternatives out there that can do discovery just as well, especially if they have published APIs. I'm not wedded to ServiceNow's Discovery tool. You can get the same functionality from other applications like Device42 or SCCM. There are a lot of other options that are very cost-effective that can do exactly the same thing.

It's not perfect. I would rate it an eight out of ten. I have definitely seen other tools do a lot more, but they're more focused on other things.

I can't discuss the use cases related to the product since I don't have many projects to deal with in my company that need the use of ServiceNow Discovery.

The out-of-the-box probes and patterns in ServiceNow Discovery are great features.

ServiceNow Discovery is a great tool. ServiceNow Discovery should be updated to provide its users with more out-of-the-box information and attributes to support the routers and switches from Cisco. It would be great if the tool could handle more out-of-the-box functionalities to retrieve the information for routers, especially those from Cisco, including the updated devices.

I have experience with ServiceNow Discovery. My company has a partnership with ServiceNow.

Stability-wise, I feel it is a good product.

I do have experience with other tools similar to ServiceNow Discovery, but I don't remember the names of the tools I used in the past. Compared to the tools I have used previously, ServiceNow Discovery can be considered a useful product if someone wants to use an agentless solution, meaning you don't have to install any agent in your system.

The solution is deployed on an on-premises model.

The solution's deployment phase takes around a month to be completed.

I rate the overall solution an eight out of ten.

ServiceNow helps us keep our CMDB updated and populated with all the necessary information. 

ServiceNow Discovery works better than other products I've used. 

In a few instances, ServiceNow has failed to discover some basic things. Some other tools are better at network discovery than ServiceNow. I'm not talking about database servers or any other infrastructure—only networking. Cloud discovery could also be better.  

We have used ServiceNow Discovery for nine or ten years.

I rate ServiceNow Discovery seven out of 10 for stability.

ServiceNow Discovery is scalable enough. It could work for businesses of any size, depending on the use case. For example, if you're working with mostly cloud infrastructure, you might want to use something that is specifically designed for that. 

I rate ServiceNow support seven out of 10. Their support technicians can usually provide a solution, but they sometimes lack adequate knowledge and we need to escalate through multiple teams. 

Neutral

Deploying ServiceNow Discovery is straightforward. It takes three or four months, depending on your use case. For larger use cases, you might need seven to 10 people, including various kinds of solution architects. 

The price is somewhat high, but if you're buying multiple products from the same line as a bundle, you can get a discount. However, if you buy Discovery as a standalone product, it will be expensive. 

I rate ServiceNow Discovery eight out of 10. When implementing Discovery, you must first understand your use case and the solution's capabilities before you dive into it. ServiceNow might not be able to do everything you want out of the box, but it's customizable.

I use the tool for IT change management. 

I am impressed with the tool's incident problem change management. 

The product should improve its customer interface, web interface, and front end. I would like to see the integration of keyboard chat with the solution. 

I have been using the solution for three years. 

I would rate the product's stability an eight out of ten. 

I would rate the product's scalability a seven out of ten. The tool's discovery component was quite difficult to scale up. My company has thousands of users for the solution. We have plans to increase the usage. 

The tool's tech support has a slow response. We have encountered scenarios where there was a lack of response even. They didn't really understand the nature of the problem. 

Neutral

I evaluated the value of the BMC solution and found it to be better. 

The tool's setup was complex. It would rate its setup a six out of ten. The product's overall deployment took two and a half months to complete. We required five staff to complete the deployment process. 

We did the solution's deployment in-house. 

I would rate the product's pricing a six out of ten. We had availed some discount from the standard pricing. Even then, the tool's pricing is expensive. You have to pay some vendor service fees for the product's implementation. 

I would rate the product a seven out of ten. You need to consider the tool's alternatives before choosing the product.