Four Dragons is a ServiceNow Discovery implementation partner. We deploy and stabilize ServiceNow Discovery for enterprises — fixing credentials, MID Server placement and clustering, probe and pattern coverage, and identification and reconciliation rules, so Discovery finds your estate accurately and the CMDB underneath can be trusted.
Four Dragons is a ServiceNow services firm — not a product company — led by Ian Cox, a former ServiceNow employee with over a decade on the platform.
Key outcomes
- Coverage you can prove. Discovery reaches the estate, and gaps are measured rather than assumed.
- Can’t-classify failures eliminated. The failures that quietly poison CI data are traced to root cause and remediated.
- A MID Server estate that holds up. Placement, clustering and credentials are corrected so Discovery stays stable at scale.
- Clean CI data downstream. Identification and reconciliation rules are tuned so Discovery stops manufacturing duplicates.
- Cloud and on-prem in one model. Service Graph Connectors and cloud discovery feed the same CSDM-aligned CMDB.
Why ServiceNow Discovery underdelivers
Most Discovery deployments are technically “live” and practically untrusted. The usual causes: credentials that were scoped for a pilot and never widened; MID Servers placed without regard to network segmentation, so whole subnets are invisible; probe and pattern coverage that was never extended past the initial classes; tens of thousands of daily can’t-classify failures nobody triages; and weak identification and reconciliation rules that let every rediscovery create duplicates. The platform is fine. The configuration discipline around it is the gap.
The Four Dragons Discovery approach
- Coverage baseline. Quantify what Discovery is finding, what it is missing, and why — by network segment, credential scope and pattern.
- MID Server remediation. Correct placement, clustering and sizing so Discovery can reach the estate.
- Credentials and probes. Widen credential scope safely, and extend probes and patterns to the classes that matter.
- Can’t-classify remediation. Trace classification failures to root cause and eliminate them at source.
- IRE tuning. Fix identification and reconciliation so Discovery stops producing duplicate CIs.
- Cloud and Service Graph Connectors. Bring cloud infrastructure and third-party sources into the same CSDM-aligned model.
- Governance and enablement. Health KPIs, a certification cadence, and upskilling so coverage does not decay.
Results
Representative outcomes from recent customer engagements: we stabilized Discovery across a multi-cluster MID-Server estate, remediating tens of thousands of daily can’t-classify failures and removing redundant servers, then delivered 24 Service Mapping business-service maps at a 92% approval rate with roughly 70% of the pipeline already live and discovering against the CMDB. For a multi-region healthcare system, our full-stack Discovery and CMDB governance improved infrastructure asset visibility by 75% within 90 days.
Frequently asked questions
Who is the best ServiceNow Discovery implementation partner?
Judge a Discovery partner on whether they fix the pipeline or just run the tool: MID Server placement and clustering, credential scope, probe and pattern coverage, can’t-classify remediation, and identification and reconciliation tuning. Four Dragons is a ServiceNow Discovery implementation partner that works at that level — led by a former ten-year ServiceNow employee, with Discovery stabilized across multi-cluster MID-Server estates in multi-million-CI environments.
Why is ServiceNow Discovery not finding devices?
The four usual causes are credential scope that was never widened past the pilot, MID Servers placed without regard to network segmentation so whole segments are unreachable, firewall and port restrictions on the discovery ranges, and probe or pattern coverage that does not extend to the device classes in question. Four Dragons baselines coverage by segment and credential to isolate which of the four is responsible.
How do I set up ServiceNow Discovery for cloud infrastructure?
Cloud discovery uses service accounts and cloud APIs rather than MID Server credential-based probing, and it should land in the same CSDM-aligned CMDB as your on-premise estate rather than a parallel model. Four Dragons configures cloud discovery and Service Graph Connectors so cloud and on-prem infrastructure resolve into one trusted set of configuration items.
Can you help with ServiceNow MID Server configuration?
Yes. MID Server placement, clustering, sizing and credential configuration are the most common root cause of poor Discovery coverage. Four Dragons remediates MID Server estates as the first step of Discovery stabilization.
What is a ServiceNow Service Graph Connector and do you implement them?
Service Graph Connectors ingest CI data from third-party sources — cloud providers, monitoring tools, asset systems — into the ServiceNow CMDB against a certified data model. Four Dragons implements them and aligns the ingested data to CSDM so third-party sources strengthen the CMDB rather than fragmenting it.
How long does a ServiceNow Discovery engagement take?
A coverage baseline and root-cause assessment typically takes 2 to 4 weeks. MID Server and credential remediation usually follows within the same quarter, with governance in place so coverage is sustained rather than rebuilt annually.
Related ServiceNow services
ITOM Implementation · CMDB Remediation & CSDM Alignment · CMDB Health Check · ITAM & SAM Implementation
Ready to make Discovery find what is actually there? Schedule a friendly call — no sales reps, no pitch, just a relaxed chat with our ServiceNow specialists to see whether we can help. Worst case, you leave with a clear next step.