ServiceNow Discovery Reviews

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. 

We are primarily using Discovery to make sure that we have a single record in the CI, or a primary source of truth. Most of our customers are buying ServiceNow from the CMDB perspective as well as Discovery. Very few have moved on to the next level, which is the service mapping. Our primary use case is definitely in terms of the CMDB because they have all the processes working in silos including the SS or the CIs, it's all managed in silos. That is our biggest problem. Everybody has access to the CMDB so anybody can actually update the records. 

The other thing is that we wanted to make sure that they capture the CI, the relationship between the CIs. That is our other main objective and focus.

We are an elite partner of ServiceNow and I'm the solution architect for IT operations management.

The advantage of the solution is that it's a single system of record and it captures the relationship. I need to be able to enable the plugin for DRCOG data certification.

The patterns are the biggest area where improvement could be made. If there's no pattern for application X, then you can't discover that particular application. That is a drawback of the product. ServiceNow gives the URL or specifies an application they can discover and devices they can discover. But if the customer has something else, then it's a challenge. One of my customers had an NAS device and it couldn't discover it. If you don't have the back end of ServiceNow, then unfortunately it doesn't work.

None of this applies to iPhones. ServiceNow claims it can discover iPhones but the data is very limited. It's really not applicable.

I've been using Discovery for more than six years. 

I haven't had any issues with stability. 

I think the initial setup is more complex than it initially appears. 

Our client uses Qualys so I was comparing that with ServiceNow. The client already has Qualys in their infrastructure. They were hoping to continue using Qualys and ingesting the data into ServiceNow. That is not a helpful integration but I wanted to evaluate it so I will suggest they use ServiceNow separately. 

The advantage of ServiceNow is that it's a single system of record which allows you to build other modules on top of it. That's the advantage of ServiceNow, 

I would rate this product an eight out of 10. 

I am a consultant and I work with IT service management solutions such as ServiceNow Discovery.

The best part about ServiceNow Discovery is that it is included in the ServiceNow suite. With other solutions, it is a separate product. You still have to pay an additional fee, but it is within the same framework.

The architecture is really simple and it is easy to use.

The service mapping component is less developed than it is in other solutions, and is in need of improvement. For example, BMC uses a more sophisticated mechanism to make the link between the services and the infrastructure.

This solution is a little more difficult to manage because you have two CMDBs.

We have experienced no stability problems or technical difficulties.

We do not contact technical support directly because technical issues are dealt with by our integrator.

I have experience with BMC and Micro Focus solutions, and they are the two best products in this space. ServiceNow discovery is younger than either of these two solutions and although it is good, it is not as good as the others. The advantage of ServiceNow Discovery is that it is totally included in the ServiceNow Suite.

It is worth noting that the BMC and Micro Focus products are more than 20 years old. By comparison, ServiceNow is only about seven years old.

We work with an integrator who takes care of the installation. We describe what we want to see and the integrator does the job.

This solution is a paid option within the ServiceNow framework.

With most clients, we spend perhaps a week testing and evaluating different solutions before a decision is made on which one to implement.

ServiceNow is a fully cloud-based solution, but for the Discovery component, you are going to have a local server to perform discovery in the network. In fact, you need to have one discovery server in each local network area, within the secure zone.

I would rate this solution an eight out of ten.

There are a lot of use cases with ServiceNow Discovery, as it's a huge platform. We mostly use the solution's ITSM and ITOM capabilities in most workflows.

Since I'm very much involved in the ITOM workspace, I like CMDB, CSDM, and Discovery. That's why I have been exploring ServiceNow Discovery versus Tanium. I'm quite excited about the future cloud integration potential that ServiceNow can provide.

ServiceNow Discovery should improve its cloud capabilities.

I have been working with ServiceNow Discovery for seven to eight years.

I am not aware of any stability issues we had with ServiceNow Discovery.

ServiceNow Discovery's scalability is quite good.

ServiceNow Discovery's technical support is fine.

ServiceNow Discovery's initial setup is not straightforward. However, once you get a grip on it, it's quite good and easy to work with.

ServiceNow Discovery's deployment took a couple of months.

ServiceNow Discovery's licensing is not a very small investment, but it definitely pays off.

I would recommend ServiceNow Discovery to others who want to use it. The solution is easy to maintain and integrates very well with ServiceNow CMDB.

Overall, I rate ServiceNow Discovery an eight out of ten.