From infrastructure connections to service context
Parny Service Map connects infrastructure, services, and the domains they support. Use it to find a service, follow its dependencies, and investigate which other systems may be affected by a problem.
This guide updates the original InfraMap article. Infrastructure Visibility provides the agent-observed infrastructure graph; Service Map adds service and domain context. Service Map currently refreshes daily, so always check the map's timestamp alongside current alerts, logs, metrics, and recent changes.
The screenshots and animations retained in this article show the earlier InfraMap interface. Labels and controls may differ in your workspace. See the current Service Map overview for current product visuals.
What InfraMap and Service Map show
Infrastructure Visibility helps you explore observed relationships between hosts and endpoints. The legacy InfraMap interface includes agent selection, time intervals, and filters for ports, protocols, requests, direction, and status.
Service Map adds a broader context for those relationships. Infrastructure View helps you explore the technical environment. Domain View groups services into business-facing domains, making it easier to relate a technical dependency to the work it supports.
Coverage depends on the data available in your environment and the selected period. An absent connection is a reason to investigate coverage or recent changes; it is not proof that two systems never communicate.
Legacy InfraMap interface: agent selection and network filters.
Get started with the right setup instructions
Sign in to your Parny workspace and open Service Map.
If infrastructure collection still needs setup, use the agent download and setup instructions available in your authenticated workspace. Check the supported operating system, agent version, required permissions, and connection requirements before deployment.
Follow those instructions exactly. Product naming changes do not necessarily change executable names, package names, configuration keys, or command-line flags.
After setup, confirm that the expected services and infrastructure appear, then check the discovery timestamp before using the map.
If the setup instructions are unavailable in your workspace, contact support@parny.io. Use the workspace's current instructions rather than an old bookmarked installer or documentation route.
Earlier InfraMap discovery and navigation example.
Explore Infrastructure View and Domain View
Infrastructure View
Start here when your question concerns where services run and which technical systems surround them. The current Infrastructure View includes Runtime, Cloud, and Service tabs, a layout selector, and a search field for node names or IDs.
The Cloud example on the Service Map page groups the displayed environment into SaaS and third parties, AWS, Google Cloud, and Data center. The counts belong to that example environment; your map reflects your own available data.
Domain View
Use Domain View to explore business-facing service groups and their relationships. The example includes Payments & Checkout, Application Services, Data & Storage, Platform, and external calls. Click a node to inspect its connections and use the interface's drill-down controls to explore the services inside a group.
Choose the view that matches your question, locate the relevant service, and follow the displayed relationships to callers, callees, databases, caches, and external dependencies.
Legacy infrastructure map example. Current views are shown on the Service Map product page.
Use dependencies to guide incident triage
A map helps narrow an investigation. Start with the service named in the alert or customer report, inspect its direct dependencies, then look for shared components that could connect several symptoms.
Use Impact Analysis to explore potential failure propagation. Treat the result as a set of systems to check. A dependency does not establish that a service is currently failing, and a highlighted path does not prove the root cause.
For example, if checkout is slow and its map shows a database and an external payment service, inspect current latency, errors, availability, and recent changes for those dependencies. Confirm which component is unhealthy before deciding on a rollback, scaling change, or other response.
Service Map's daily discovery snapshot can be older than the incident. Check for deployments and topology changes since its timestamp before relying on a missing or existing edge.
Earlier InfraMap screenshot retained for infrastructure context.
Plan changes and review dependencies
Before a migration or deployment, use the map to build a checklist of connected services, data stores, platforms, and third-party dependencies. Review it with the teams responsible for those systems and compare it with your deployment plan.
After the change, check the next available discovery snapshot and validate critical paths with current monitoring and tests. Comparing two maps can support a review, but a map alone cannot guarantee that every connection is healthy or that a migration is complete.
Highly connected services may deserve extra attention because many systems rely on them. Connection counts show relationships, not bandwidth, latency, or proof of a performance bottleneck. Validate those questions with the relevant telemetry.
Legacy InfraMap example from the original guide.
Keep monitoring and mapping connected
Use dependency context alongside your configured monitoring and incident workflows. Review unexpected endpoints, ports, or protocols with the appropriate service owner, and check whether important dependencies have suitable monitoring coverage.
Do not assume that drawing a dependency automatically creates a monitor or an alert rule. Verify the monitoring source, alert conditions, ownership, and notification path in your workspace.
A practical review checklist
Check the discovery timestamp and the environment you are viewing.
Confirm expected services and dependencies are present.
Review shared dependencies and external services with their owners.
Validate possible impact against current alerts, logs, metrics, and recent changes.
Revisit the map after meaningful infrastructure or application changes.
Earlier InfraMap investigation example.
Summary
Use Infrastructure Visibility for observed infrastructure connections and Service Map for service and domain context. Together, they give teams a clearer starting point for dependency reviews, change planning, and incident investigation.
Start with the Service Map overview, or explore Infrastructure Visibility. For setup, use the current instructions inside your authenticated Parny workspace.
Comparing tools for your team? Use our guide to choosing service dependency mapping software to test coverage, freshness, investigation workflows, security, and cost.
