CI Details: Understanding Configuration Item Detail Pages
Explore the full detail view for any configuration item including configuration, relationships, change history, and operational metrics
Every Configuration Item in Parascope has a detail page that gives you a complete picture of that asset -- its current configuration, relationships to other CIs, change history, and operational metrics.
Navigating to a CI
- Click any CI name in the CI list, dashboard, or change history
- CIs are also linked from relationship views and correlation panels
- URL format:
/configuration-items/{ci-id}
Header
The header shows at-a-glance identity:
- CI name with source-colored type badge
- Status indicator -- Active (green), Inactive (amber), Archived (gray)
- Last seen timestamp -- when the collector last observed this CI
- Breadcrumb -- back link to the CI list
Page Layout
The detail page has a main content area at the top followed by tabbed sections below.
Main Content
The upper section shows the CI's current state:
- Lineage Strip -- Shows the CI's position in the infrastructure hierarchy. For example, a Kubernetes pod shows its parent deployment, namespace, and cluster. Click any ancestor to navigate to it.
- Configuration Attributes -- The CI's tracked configuration data organized by category. Values include copyable IDs, external links for URLs, and expandable JSON tree viewers for complex objects.
- Type-Specific Detail -- Many CI types have purpose-built detail components (e.g., Kubernetes pods show container status, resource requests/limits; Proxmox VMs show hardware configuration). These are auto-discovered by naming convention.
Tabs
Below the main content, four tabs provide deeper context:
Relationships -- Two views of the CI's connections:
- Graph View -- Interactive visualization showing related CIs as color-coded nodes and relationship types as labeled edges. Zoom, pan, and click nodes to navigate.
- Table View -- Tabular list of all relationships with type, target CI, and confidence score.
Relationship types include: runs_on, contains, connects_to, manages, member_of, selects, mounts, references, and more.
Correlations -- Shows cross-system matches from the correlation engine:
- Correlated CIs from other sources
- Confidence scores
- Matching criteria that triggered the correlation
- Accept/reject actions for pending correlations
History -- Chronological timeline of every change detected for this CI:
- Change type -- Created, Updated, Deleted
- Timestamp -- When the change was detected
- Field-level diffs -- Old value to new value for each changed field
- Only config fields appear in change history (not metrics -- see below)
Raw Data -- Full JSON view of all CI attributes for debugging and exploration:
- Expandable/collapsible tree structure
- Copy buttons for JSON snippets
Config vs Metrics
Understanding what gets tracked in change history:
| Category | Tracked in Changes | Example |
|---|---|---|
| Config | Yes | VM CPU count, container image, network config |
| Metrics | No | CPU utilization %, memory usage, uptime |
Config represents intentional state -- things that change because someone or something made a deliberate change. These changes are valuable to track.
Metrics represent point-in-time measurements -- values that change constantly and would create noise in the change history.
Infrastructure Walkability
CI detail pages are designed for "infrastructure walkability" -- the ability to click through related CIs to understand your infrastructure:
- A Kubernetes pod links to its node, deployment, namespace, and cluster
- A Proxmox VM links to its node and storage
- An OS instance links to its parent VM and discovered software/certificates
- Each link takes you to the full detail page for that CI
Look for CI name links throughout the detail page -- they are all clickable navigation points.
Criticality Score
If criticality scoring is enabled, the CI detail page shows:
- Score (0-100) with color-coded tier badge
- Tier -- Critical (red), High (orange), Medium (yellow), Low (green)
- Breakdown -- Dependency impact, resource size, and type criticality components
Related Documentation
- Searching and Filtering CIs -- Finding CIs to view
- Change History -- Global change timeline
- Infrastructure Lineage -- How lineage works
- Criticality Scoring -- How scores are calculated
- Correlation Engine -- Cross-system matching