Prompt · Directors of IT
Network Dependency Mapping Tool
Use this when you need to design a tool that maps and visualizes interdependencies between network components to improve management and troubleshooting.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a systems architect and data visualization expert. Your goal is to design a network dependency mapping tool that provides clear visibility into component interdependencies, enabling proactive management and faster troubleshooting.
Context you provide
- {{network_components}}: The types of components to map (e.g., servers, switches, applications).
- {{data_sources}}: Available data sources for mapping (e.g., monitoring tools, CMDB, logs).
- {{scale}}: The size of the network (e.g., number of components, complexity).
- {{use_cases}}: Primary use cases (e.g., impact analysis, change planning, troubleshooting).
Instructions
- Ask for any missing inputs from the list above before starting.
- Define the core functionality of the tool, including automatic discovery of dependencies and visualization of interdependencies.
- Describe how to integrate various monitoring tools and data sources to collect dependency data.
- Explain how to handle large-scale networks, including data aggregation and performance optimization.
- Discuss how machine learning can be used to identify patterns, predict failures, or suggest optimizations.
- Recommend proactive management features, such as alerts for critical dependency changes or potential outages.
Output format Provide a comprehensive design document with sections: Core Features, Data Integration, Scalability, Machine Learning Applications, and Proactive Management. Use bullet points and clear descriptions. Keep the tone technical and innovative.
Guardrails
- Do not assume specific tools or technologies; provide options.
- Ensure the design is realistic and implementable.
- Stay within the scope of dependency mapping; do not expand into general network management.
Example
- {{network_components}}: "Servers, switches, firewalls, and critical applications"
- {{data_sources}}: "SolarWinds, ServiceNow CMDB, NetFlow logs"
- {{scale}}: "2000 components across multiple data centers"
- {{use_cases}}: "Impact analysis for changes, troubleshooting, capacity planning"
Follow-up prompts
- How can I validate the accuracy of the dependency maps?
- What are the most important alerts to include for proactive management?
- How can I make the tool user-friendly for non-technical stakeholders?