FireScope Discovery and Dependency Mapping (DDM)

Organizations that attempt to track IT service configuration through manual efforts cannot keep up with the rapid pace of change and complexity in the modern data center. This outdated or inaccurate configuration knowledge puts organizations at risk of repeated - and expensive - service outages caused by configuration errors and significant opportunities for increased efficiency are lost.

FireScope Discovery and Dependency Mapping (DDM) gives organizations a clear and timely view of IT Service configuration, automatically identifying the IT services that users are consuming, their infrastructure dependencies from applications down to the network, and continually refining this picture as infrastructure changes take place.

Yet, the endless state of change in the modern data center makes it impossible to manually keep track of every change or to fully understand the complex relationships between infrastructure assets.

  • Boost your confidence in configuration data by automating the mapping of your critical IT services and their dependencies, including application, physical and virtual elements.
  • Decrease your work load, with automated, real time discovery that eliminates the need to spend countless hours collecting configuration information and updating spreadsheets.
  • Learn more about your environment, with topology, network and API (VMware, AWS, etc.) discovery that adds deep configuration details.
  • Stay up to date, with no need to wait for scheduled scans to detect change and comparison views of authorized configuration versus actual.
  • Get all of IT on the same page, with integration with Cherwell Service Management CMDB that enables automatic population of service dependencies and asset configuration details.
  • Reclaim under-utilized resources that no longer contribute to operational services.
  • Simplify your life, with Software-as-a-Service (SaaS) delivery that offers value on day one, with no need to maintain a massive, dedicated infrastructure.

Watch the 7-Minute Demo

Want to learn more about FireScope? Complete the form below to see a short 7-minute demonstration of FireScope DDM and our integration with the Cherwell Service Management platform.

FireScope DDM for Service Management

Eliminate the doubts and effort involved in maintaining service configuration knowledge with FireScope DDM. This is the only solution on the market that persistently monitors connectivity between assets to identify changes in service topology as they happen and helps you ensure that you are always looking at the most accurate picture of service configuration.

  • Improve change impact analysis with trusted, real time maps of service dependency.
  • Enhance your Cherwell Service Management Configuration Management Database (CMDB) through automated federation from FireScope DDM.
  • Identify services that you might not be aware of, through continual url pattern discovery based on user requests.
  • Verify change execution and identify unauthorized changes by comparing actual topologies against their authorized baseline.

FireScope DDM for Operations Management

Virtualization, cloud, containers and other emerging technologies complicate efforts to keep track of change by hand. That's where FireScope DDM can help, offering a highly accurate and real-time view of IT service dependencies.

  • Reduce unplanned outages caused by misconfiguration.
  • Slash the time it takes to perform root-cause analysis.
  • Improve communication across IT disciplines.
  • Reclaim resources that are no longer contributing to services.

FireScope DDM for Application Management

Application performance can be severely impacted by the health and load of downstream dependencies, even if you aren't in charge of those elements. With FireScope DDM, you can easily map your applications across the whole of IT, and keep track of changes that may be impacting performance, as they happen.

  • Map applications across technology, functional or organizational silos for a clear picture of potential performance or capacity bottlenecks.
  • Identify changes as they happen to quickly trace their impact on application health and performance.
  • Spot potentially unknown external dependencies that may be impacting users, regardless of whether they exist within your data center.
  • Eliminate hundreds of man hours spent documenting applications, only to be out-of-date within an hour.

Compare FireScope DDM to the Competition

  By Hand BMC Discovery
(Formerly ADDM)
ServiceNow ServiceWatch FireScope DDM
Deployment Complex on-premise installation Cloud-based Deployment Cloud-based Deployment
Auto-detection of service entry points
Requires remote administrative privileges    
Primary discovery done via agent- and script-less technology
Scope includes network, virtual and physical topology if network, virtualization teams involved Partial
Able to discover and map custom applications out-of-the-box dependent on who is involved
Dependency mapping enriched with multiple discovery engines send multiple emails, hope for response
Able to identify service topology changes as they occur changes detected after outages occur
Integration with CMDB more work

 

Frequently Asked Questions

Download as a PDF

How does DDM discover a business service?

FireScope DDM listens to the URLs being requested by users to discover service endpoints. It can also listen for specific protocols or port traffic, such as LDAP or Oracle applications, to discover infrastructure service endpoints. From either starting point, the solution analyzes aggregate network traffic between virtual and physical servers to follow transactions through their downstream dependencies. Additional virtualization, storage and network discovery scans complete the picture by mapping the virtual and physical dependencies.

Do I have to open ports or enable remote administrative privileges to make it work?

No. A widely raised security concern for many discovery tools is the requirement that RPC ports must be opened and remote administrative privileges granted. With FireScope's approach, this is not necessary.

How are changes tracked? Can FireScope DDM track service dependencies that may be utilized infrequently or after hours, such as scheduled jobs or after hours data processing?

FireScope continually analyzes aggregate network traffic; which servers are communicating with other servers over specific ports or protocols. Once a service baseline has been created, all traffic is compared with this baseline to identify new connections as they happen or when connectivity between two assets has stopped for extended periods of time. As this is running continuously, there's no need to worry about what might me missed with schedule-based discovery.

What if I don’t/can’t have the network team involved in this project?

FireScope DDM includes a host of options to discover service dependencies. If access to network devices is unavailable, the solution can utilize optional sensors running on vms or servers.

What if I don’t/can’t have the server team involved in this project?

Discovery can still be performed by using port mirroring or NetFlow/sFlow from network devices. Additionally, the network discovery can identify OS, DNS name, running net- work applications (e.g. Apache, MySQL, Oracle) without the use of an agent. Agents do provide much deeper system con guration details, but are not required or could be rolled out at a later date.

What do I need to know about my Services before beginning discovery?

In short, nothing. For many competing solutions, you have to tell the solution where to start with each service (e.g. provide a url or server) and know a significant amount about the application's architecture. FireScope DDM can detect which urls are being requested by users, providing you a list of what we have automatically identified as potential services. Once you select the services you care about discovering, the solution does the rest.

Is this Application Dependency Discovery (ADDM)?

Application dependency discovery is limited to applications and the servers they run on, with little to no visibility into other dependencies that are just as critical such as at the network, storage and virtualization layers. FireScope DDM supports the complete picture, telling you which applications on which vms are depending on another, which physical hosts and data stores those vms are running on, and which routers and switches they are plugged into. This is absolutely critical for effective change impact analysis, as a failed switch can have a larger impact on the business than a failed server.

Can FireScope DDM map my custom applications?

Absolutely! At the network level, application architecture becomes moot. Web servers talk to application servers, application servers talk to database servers, regardless of whether they are written in Java, .Net or any other language. Because FireScope is looking at how different systems are communicating with each other, this allows it to discover any service topology, regardless of platform, architecture or whether they are commercial or custom.

Can I leverage existing repositories of configuration data?

Absolutely. Just a few of the more common scenarios are described below:

  • Spreadsheets – We often run into customers with considerable data in spreadsheets, which can be imported and mapped to attribute data.
  • SCOM, Solarwinds, asset management or monitoring tools – Leveraging FireScope DDM's Enterprise Service Bus and other methods, the solution can directly query these solutions for asset data. This data can then be verified and gaps filled in using FireScope DDM's native discovery capabilities.

Click here for a PDF of the FireScope DDM FAQs.