ServiceNow Discovery Reviews

My company uses ServiceNow Discovery to discover multiple CIs, servers, network devices, computers, etc.

In our company, importing and scanning IP addresses with ServiceNow Discovery is a straightforward and easy process.

Whenever you try to discover something with the solution, you get errors that are not descriptive enough. The aforementioned area can be considered for improvement in the solution.

The licensing cost of the solution is an area where ServiceNow can improve.

I have been using ServiceNow Discovery for more than three years.

It is a stable solution.

It is a scalable solution.

My company deals with multiple clients who prefer ServiceNow Discovery. I was involved with the implementation phase of the product for my company's clients.

The initial setup of the product is straightforward.

It doesn't take more than a week to implement the product.

As a part of the deployment process, you first need to understand the infrastructure of ServiceNow Discovery. Once you understand ServiceNow Discovery, you will be in a better position to use your data with the existing data in ServiceNow.

My company has a six-member team to take care of the product's implementation process.

There is a need to make payments every quarter of a year towards the licensing costs of the solution. ServiceNow Discovery is an expensive tool.

I rate the overall solution an eight out of ten.

My role right now in present projects is to deploy ServiceNow Discovery both on AWS cloud an on-premises. ServiceNow Discovery is populated directly into ServiceNow CMDB, so its use cases include managing CMDB identification and reconciliation, as well as creating dashboard reports and other types of reports.

In the past, I found troubleshooting difficult in ServiceNow Discovery because I didn't have much exposure to the platform during that time, but then I explored some troubleshooting features, and I found that it wasn't that tough, so this is one of the qualities I like about ServiceNow Discovery.

I also like that log reading in ServiceNow Discovery is much better than other tools.

Another valuable feature of the tool is that you don't need to install many tools to deploy ITSM. You only need to subscribe to the modules to deploy the proper ITSM in your organization.

What needs improvement in ServiceNow Discovery is the reporting UI because I didn't find it as friendly compared to other tools. Other tools have better reporting UI than what's currently in ServiceNow Discovery.

What I'd like to see in the next release of ServiceNow Discovery is more user-friendly out-of-the-box reporting that would be helpful for non-technical users. Some users such as managers would want to just do a few clicks to access the reports and shouldn't be required to do search queries, but right now, reporting in the tool isn't very user-friendly.

I've been learning ServiceNow Discovery since 2015, and I started working on it for the last two years only. I'm still using it, particularly the San Diego version for one project and the Rome version for another project.

ServiceNow Discovery is a stable tool.

ServiceNow Discovery is a scalable tool, especially because the industry has now properly recognized it, so many of the network companies, for example, Cisco, release product versions that have compatibility with ServiceNow Discovery. Companies that manufacture network devices and storage devices also create plugins that have more compatibility with ServiceNow Discovery, which makes the tool scalable.

I haven't had the chance to contact technical support for ServiceNow Discovery yet. My team once raised a ticket to get help, but it was for cleaning a different solution, CMDB.

For any troubleshooting questions and solutions, I check the community forum and documentation. My team and I still have some pending issues with some features of ServiceNow Discovery and we didn't find very specific resolutions or proper answers in the documentation and the community forum.

I found the initial setup of ServiceNow Discovery easy. The process is the same with other discovery tools where some prerequisites need to be deployed within your client's environment, both open and privileged requirements and service accounts to access the environment.

Setting up ServiceNow Discovery is easy because you're provided with a guided setup to install the features, so I found it easy.

The total time it takes to deploy the tool is between one to two days if you have all the required information. Once you have a subscription, you just need to enable some plugins and deploy one integration within your client's organization because ServiceNow Discovery is a cloud-based tool which means you need to deploy one application into the organization which doesn't take more than half an hour. That would also depend on how many MID servers are deployed, so in general, to make the environment ready to start discovery, it would take two days. What could take time would be the credential setups and other requirements provided by the clients, but in total, deployment would take just one to two days for ServiceNow Discovery.

You need a subscription to ServiceNow Discovery, so you can use its features. You can also use specific plugins with the tool, and some of the plugins are free. I don't have information on how much my company pays for the subscription to ServiceNow Discovery.

Nowadays, I've been working on BMC Discovery, ServiceNow Discovery, and CMDB projects.

My company is a partner/implementer for ServiceNow Discovery, but many consultants within the company, apart from myself, also use the tool.

My advice, if you're looking into using ServiceNow Discovery for the first time, is to compare it with other tools and also consider your requirements because not all discovery tools provide all the features you need. For example, one discovery tool could be strong in this area, while the other tool could be strong in another area or feature. You should go for ServiceNow Discovery if it meets your requirements. Otherwise, use another discovery tool. ServiceNow Discovery is a platform that provides full IT infrastructure services, and it's very good for any organization, but that still depends on company requirements, so you need to evaluate those requirements first. For example, check existing devices and infrastructure already deployed in your company and what you'd like to discover through ServiceNow Discovery, whether it's just servers or network devices, etc.

I'm rating ServiceNow Discovery eight out of ten. Though it's a very important tool for users, I'm unable to give it a ten because it still needs to be more user-friendly in terms of reporting. The documentation for the tool also needs improvement, particularly because some features aren't explained well. The tool has very powerful features with no proper documentation available, so some users still have to search for answers in the community forum.

I like ServiceNow Discovery's overall structure and the way data comes in without creating a different dashboard or interface. 

ServiceNow has a constant development environment. Hence they get constant bugs which result in incorrect performance. It should also improve customer service. 

I have been using the solution for quite some time. 

I would rate the solution's stability a ten out of ten. 

I would rate ServiceNow Discovery's scalability a ten out of ten. One of my current customers has over 10,000 users for the product. 

The product's setup is straightforward. 

The product is not cheap. 

I would rate ServiceNow Discovery a ten out of ten. You would need to go on training before using the solution. 

We use ServiceNow Discovery to look at assets, processes, and some process mining. On the other hand, we use ServiceNow ITSM to capture tickets and move away from Remedy. We also use ServiceNow ITSM APIs for contract management, focusing on change, configuration, release, incidents, and problems.

One of the most valuable features of ServiceNow Discovery is the automated discovery that helps identify dependencies, and then my company gets a report on that. My company has many applications, whether developed internally or bought off the shelf, and my company needs to know which application has a dependency on what. Sometimes, developer teams make changes to applications, which then causes other ecosystems to crash, which is where ServiceNow Discovery comes in.

Another valuable feature of the solution is security management related. The security landscape in this post-pandemic world is very different, so you don't want to have insecure access to any of the applications, especially ones focused explicitly on service management and service delivery for clients. Hence, my company also uses ServiceNow Discovery for more secure access and communication using certificates between different parties involved, which is beneficial.

ServiceNow Discovery has matured since the last time I got on the bandwagon, but its integration with legacy apps is one area for improvement. Right now, the ServiceNow Discovery APIs cater more to newer apps, whether the apps run on AWS or Azure, and it's much easier on more recent apps versus on-premises apps that don't necessarily have the proper API interfaces, such as REST or JSON. You need to do a lot of manual work to properly integrate ServiceNow Discovery with legacy apps compared to integrating it with newer apps.

ServiceNow Discovery isn't a plug-and-play solution, which is another area for improvement, as that causes a delay in the overall process. Making it a plug-and-play product is helpful.

ServiceNow Discovery offers out-of-the-box reports, and though that's okay, allowing easier report customization would improve the solution. Currently, customizing reports isn't as straightforward as some of the other tools in the market. It's challenging to build custom reports in ServiceNow Discovery. You can use the basic reports offered in the solution, but if you need analytics and more advanced reporting, there's a lot of work to be done.

The product also lacks training resources, which is another area for improvement. It would be very helpful if ServiceNow included some advanced training with the sale. Most team members have to either go online and search on Google for more advanced training. There's no issue with the basics as they're straightforward, but the white papers don't necessarily come with very good use cases of how someone has implemented an intelligent workflow. If ServiceNow could provide more ServiceNow Discovery videos, certification, or cheat sheets to make the overall implementation and configuration of the solution faster, it would be quite useful.

An additional feature I want to be added to ServiceNow Discovery is an integration studio that helps you map into legacy apps. It should be drag-and-drop and very visual.

I also want the ServiceNow Discovery pricing model to be more of a pay-as-you-use. The challenge right now is whether it's a subscription or whether it's perpetual. The licensing model costs a whole lot more than other solutions, so even though my company uses a public cloud to run ServiceNow Discovery, that doesn't mean you can enjoy the same benefits, and whether you use it more or use it less, you incur the same costs, which is not necessarily a more accurate positioning of how the overall business works for a particular year.

Cost-wise, ServiceNow Discovery seems to be from an era where it is more on-premise than sitting on the cloud, even though it is a cloud solution. ServiceNow should have a pay-per-use licensing model so that if my usage increases, I can pay more, rather than needing to pay the same amount whether my usage increases or decreases.

I've been using ServiceNow Discovery for two and a half years now. I've used ServiceNow ITSM longer, in particular, seven to eight years now.

ServiceNow Discovery stability is an eight out of ten because it never crashed. Still, sometimes, it has pending critical workloads because it needs connectors and visibility based on company protocols.

The stability of the solution isn't an issue, but its predictability is, though that has improved. There used to be dependency mapping issues where some critical workloads were excluded, so support worked on it, fixed it, and gave my company a patch.

ServiceNow Discovery is scalable but comparable to a Lego block set. You can do what you want with it, and you can do anything with it, but the question is "how easily can you scale it?"

If you were to look at commoditized functions as automated discovery and getting visibility into your workloads on the cloud, it's not rocket science, and it's pretty quickly done. However, when you're in an enterprise scenario where you have legacy apps, then the scaling, although it's possible, scaling ServiceNow Discovery becomes more complex.

Scalability-wise, it's a seven out of ten, and it's not merely about how many ServiceNow Discovery instances you're using or how many projects, but whether setting up reports, finishing service maps, etc., is easy.

The level one and level two technical support for ServiceNow Discovery were satisfactory, but the more senior support wasn't because only a few senior support was available. We had to wait at least three to four days to get more senior resources to help us with critical issues, and sometimes, they were not very strong, but basic support, for example, people who create tickets and get details from us, have been okay.

I'd rate the ServiceNow Discovery technical support as seven out of ten.

Neutral

The initial setup for ServiceNow Discovery was very straightforward, and you don't need to do much to set it up. After you set it up, that's when you'll have to take more steps. For example, when you configure intelligent workflows and integrate third-party apps, and if you want to put in graph connectors, that takes time.

I'd rate the ServiceNow Discovery initial setup as four out of ten because it takes time to configure and set up the workflows. My company expected to complete the setup in three months, but it took seven months to get it done.

ServiceNow Discovery has very broad pricing, so it becomes costly. It would be better if it had a pay-as-you-use licensing model because the total cost of ownership is quite high.

The ServiceNow Discovery unit price is comparable to other products, but if you look at the packaging, the TCO is much higher than others.

Overall, I'd rate the ServiceNow Discovery licensing costs as five out of ten.

My company works with various products. It partners with different platforms to build websites that run governance projects, provide RPA solutions, etc. For example, my company works with ServiceNow, Blue Prism, and Automation Anywhere.

ServiceNow is one of the platforms my company uses for internal IT request management, as well as an engine to help with the governance tool my company developed for clients and usage internally that helps with contract management.

I'm currently using both ServiceNow Discovery and ServiceNow ITSM.

Within my company, twenty to thirty people use ServiceNow Discovery, and each user has a different purpose. Some users use it internally, while some use it for client projects.

My rating for ServiceNow Discovery overall is seven out of ten.

My company is both a partner and a user of ServiceNow Discovery.

I am a consultant. We implement solutions for our clients.

The primary use case of this solution is to automate inventory management, asset management, and discovery. It also used to integrate with other monitoring tools for instant management change.

Mainly, the primary use case would be the automatic management of inventory.

We integrate with other products.

They keep expanding even for the cloud, and there are many plugins.

The biggest advantage of ServiceNow is the value that it brings.

They can expand on the plugins for some of the other tools.

In the next release, they can automate some of the workflows similar to what they have with TAM Pro.

With the integration, they can include some of the commonly used tools such as SCCM. They can benefit from bringing in other tools for their workflows.

We are hoping that they explore or leverage some of their existing tools such as Tanium for the purposes of discovery and monitoring.

I have used this solution in the last 12 months.

We are up-to-date with the latest versions, but it depends on what the clients prefer. We have Orlando and New York also.

It's stable. I have seen a few glitches, but not often. In general, it's pretty stable.

It's definitely scalable; you just have to add IP ranges and set it up.

Technical support is strong.

We have a technical account manager assigned to the product when we purchase it and then you can find support with a person. It is very diligent and it is pretty solid.

The initial setup is straightforward. It's not very complex, but there are a lot of dependencies for clients to set up their environments, such as IP ranges.

If they have a mature network architecture that is dependent on IP ranges then the setup will not be complex.

The value that they get from the product is good. Once you set it up, it's easily scalable and there's a large scope for automation and the product keeps expanding.

There are many licensing strategies. For example, discovery is based on the number of nodes or subscription units.

It's a bit expensive compared to other products in the market, but it's worth the money you pay because it's far advanced in terms of features, automation, and capabilities compared to other products.

The sentiment that we get from clients is that ServiceNow is expensive. 

I would rate ServiceNow an eight out of ten.

Primary use cases are below:

1. Infrastructure Discovery 

2. Perfect CMDB

3. Application Dependency 

4. More clarity on running software in the environment

5. Reduce the cost

Used this product for all environments

Based on discovered infrastructure, we made stable CMDB in customer environment and usage during change request.

• The security is a major part of the solution. Customers look for the best security.
• Console
• They provide the ability to see whatever customer wants to see into the Discovery tools . They offer the best tool view. 

In terms of improvement, I would like for it to be possible to use without coding. I would like dropdown ootion so that every customer can modify easily as per requirements and can understand it. They shouldn't need to learn Java or another scripting.

More than five years

It is very stable. It's very good. It's also scalable. Our clients are small, medium, and large size enterprises. 

Scalability is perfect.

The response time should be reduced for tickets. 

The initial setup is very straightforward. We need to provide some security information and that's it. It takes around one week to deploy all of the configurations, max. It depends on how customers move ahead with the process. 

Yes, we evaluated bmc, hp etc

I would recommend for ServiceNow. It's very good and straightforward.

I would rate it a nine out of ten. 

The dashboard should be more clear so that I can clearly see the errors. It should be a single console. I want it to be categorized by which specific issues everything is facing. 

When my team starting any project or learning a new environment, we always implement ServiceNow Discovery which can be used along with other products. We are able to extract details on the environment to help transition services.

This solution provides excellent insights.

Application discovery could be improved. Right now, ServiceNow needs to be coupled with another solution in order to verify the information.

It is a stable product.

This is a scalable product, especially since it is within a public cloud.

We have not needed to use support.

The initial setup is easy but expect to have to take some time to learn the product.

It is an expensive product with a price that depends on the models that you wish to purchase.

This is something that I would recommend for medium or large companies. 

I would rate this a seven out of ten.

We primarily use this solution for three things: hardware asset management, software asset management, and IT service management.

Within our organization, there are 500 employees using this solution. We definitely plan to continue using this solution.

I find that the Discovery and scripting features are the most useful.

On the Software Asset Management part of it, I expect additional reconciliation and Discovery features there.

I have been using this solution for a year and a half.

ServiceNow Discovery is definitely stable. 

ServiceNow Discovery is easy to scale. It's got different bolt-ons, so you can scale up or scale down, as you require.

I have raised tickets with them. I've not had to deal with them that much, but I've raised a few tickets when dealing with them, and they're quite good.

The is no installation process. There are plugins, but most of the product is in the cloud. That's the attraction. It's a SaaS product, so a lot of it's in the cloud.

There is a subscription for ServiceNow Discovery. It's expensive, but I think it's one of the best solutions on the market, so it's worth it.

I would absolutely recommend ServiceNow Discovery to others. Overall, on a scale from one to ten, I would give this solution a rating of seven.