Skip to main content

CI Detail Page Layout

This guide describes the layout and key sections of a CMDB configuration item (CI) detail page. The AWS EC2 instance layout is used as an example.

Header Bar (Top)​

The header bar provides high‑level context and global actions for the CI:

  • CI type and title (left) – shows the CI class/type label (for example, AWS EC2 Instance) with the CI display name or identifier beneath it.
  • Global actions (right) – icons such as:
    • Refresh (circular arrow) to reload the CI from CMDB.
    • Link/Share (chain link) to copy a direct link to the CI.
  • Primary actions – prominent buttons including:
    • ATTACH TO APPLICATION – associates the CI with a Cloudaware application record.
    • TAG AWS EC2 INSTANCE (or equivalent for other resource types) – manages provider tags for the resource.
    • A three-dot menu (⋮) that exposes additional layout-specific actions.

Summary KPI Tiles​

Below the header, a horizontal row of compact tiles summarizes key posture, cost, and operational signals for the CI, such as:

  • 30‑Day Cost – recent cost associated with the CI.
  • Breeze – Breeze data availability (for example, Data is being collected or No data if the agent is not installed or reporting).
  • Upgradable Packages – upgrade information for installed packages (Security/Optional) where available.
  • Application – application association status (for example, Application/Tier names or Application is not set up when no application is linked).
  • Scans – security scanning status (for example, High severity or Not being scanned).
  • Backups – backup configuration status (for example, Backups Health: {Number}% or Backups are not set up).
  • Blended Cost – blended cost metric for the CI.

These tiles provide at‑a‑glance signals and act as entry points into the corresponding modules (cost, Breeze, vulnerability scanning, IDS, backups, applications, etc.).

Not all tiles appear for every CI type. Some tiles are shown only when the underlying data or module is available and relevant to that object (for example, Breeze and Upgradable Packages on Breeze‑enabled compute, or Backups when backup policies apply).

tip

Many tiles are clickable. Selecting a tile can take you directly to the corresponding tab on the left or open an otherwise hidden view. For example, clicking Upgradable Packages on an EC2 instance can open the CloudAware Upgradable Packages section for that CI.

Left Navigation Panel (Tabs)​

Along the left side of the CI detail page, a vertical navigation panel organizes tabs to view related data for the CI, for example:

  • DETAILS (the main information view for the CI; typically the default selection).
  • RELATED CIs – related infrastructure objects and dependencies.
  • CAPACITY REPORT – capacity, utilization, and sizing information where available.
  • SECURITY – security posture, findings, and related controls.
  • APPLICATION – application associations and context.
  • BACKUPS – backup configuration and status.
  • CHANGE MANAGEMENT – change records and approvals associated with the CI.
  • TAGS – tag management and metadata views.
  • SYSTEMS MANAGER – provider‑specific systems management integration (for example, AWS Systems Manager).

Each navigation item can include a small status indicator (a toggle‑style icon) to show whether the module is enabled, configured, or has data (for example, green for active/data available).

tip

Not all tabs appear for every CI type. Some modules are only available or relevant for specific classes of objects (for example, capacity or Systems Manager on compute resources, or backups on resources that support backup policies).

Details Tab​

The DETAILS tab is a primary CI record view.

Core CI Record Information​

At the top of the main content area, a structured information block shows core CMDB metadata:

  • Name – CI display name
  • Owner – record ownership field
  • Created By – user or system that created the record, with timestamp.
  • Last Modified By – user or system that last updated the record, with timestamp.

In many cases, Cloudaware system identities (for example, CloudAware) appear as the creator/modifier for records that are maintained automatically by ingestion or data synchronization runs.

tip

If you hover over a field label on the CI layout, a small field summary icon may appear. Clicking this icon opens a built‑in details window showing:

  • Description – human‑readable explanation of the field.
  • Specification – technical details such as field type and API name.
  • Value Metrics – statistics such as row count, distinct values, and null values for that field across the dataset.

Location​

The Location section describes where the resource lives in cloud/account and regional terms. For example, typical fields on the EC2 instance layout include:

  • Account – AWS account that owns the EC2 instance.
  • Region Name - AWS Region code where the EC2 instance is running (e.g., us-east-1).
  • Availability Zone Name - Availability Zone label for the EC2 instance’s placement.

These fields help you quickly confirm the account, region, and availability zone context for the CI.

Special Fields​

A dedicated area highlights CI‑class‑specific identifiers and system fields, such as:

  • Deleted From AWS – indicator showing whether the resource has been removed from the provider while still represented in CMDB.
  • Instance ID (External ID, Unique) – primary provider identifier for the resource.
  • CloudAware UUID – internal unique identifier used by CMDB for correlation and deduplication.

Together with the header and navigation elements, these sections provide a consistent way to understand what the CI is, where it runs, and how it is tracked inside Cloudaware.

State (Instance Runtime and Health)​

The State section provides a quick operational snapshot of the instance runtime and health, including:

  • State Name – current lifecycle state (for example, running), often shown as a green pill/tag and in a highlighted banner.
  • State Code – numeric provider state code (for example, 16 for an AWS EC2 instance in running state).
  • State Transition Reason – text describing why the last state change occurred (blank when not applicable).
  • State Reason Code / State Reason Message – additional provider status details (blank when not applicable).
  • Instance Status / Instance Status Details – instance‑level health checks (for example, ok, reachability: passed).
  • System Status / System Status Details – system‑level health checks (for example, ok, reachability: passed).

Together, these fields summarize lifecycle state and AWS instance/system reachability checks in one place.

Source (Discovered AWS/EC2 Attributes)​

The Source section surfaces raw attributes discovered from the provider (for example, AWS EC2 instance properties). For example, typical EC2 fields include:

  • Architecture – CPU architecture (for example, x86_64).
  • ARN – instance Amazon Resource Name.
  • Auto Scaling Group ARN / Auto Scaling Group / Auto Scaling Group Name – identifiers and names when the instance is part of an Auto Scaling group (blank when not applicable).
  • Image ID — AMI used to launch the instance; key for provenance and rebuild/patch baselines.
  • Instance Type — compute shape (CPU/memory class) that drives capacity and cost.
  • Key Pair Name — SSH/RDP access lineage (who/what key was used to provision access), useful for governance.
  • Platform — OS family and display label (e.g., Windows/Linux), used for ops and compliance segmentation.
  • Private IP Address — primary internal address for reachability, dependency mapping, and troubleshooting.
  • Subnet ID — network segment placement (often implies AZ) and routing/security context.
  • VPC ID — network boundary/tenant context.

These provider facts support troubleshooting, auditing, and enrichment use cases (for example, understanding ASG/Beanstalk membership, reservation posture, CPU configuration, and boot mode).

Custom Fields​

The Custom Fields section holds organization‑defined attributes that extend the standard provider schema. For example, on AWS EC2 instance layout:

  • Environment PL – a custom environment or platform‑line field.

Custom fields capture business context that is not native to AWS or other providers, such as environment classification, platform line, cost domain, or application lineage.

Tags: Standard Fields​

The Tags section shows tag coverage and content in both human‑readable and structured forms. Typical fields include:

  • Tag Count – number of tags applied to the resource.
  • Tags – a rendered list or summary of key/value tags.
  • Tags JSON – an expandable JSON/tree view of all tags (for example, a root object with keys such as Name: "...").

This view provides a normalized tag representation for humans while keeping the raw JSON structure available for automation and compliance checks.

Cost​

The Cost section surfaces object‑level cost metrics derived from billing data. For example:

  • Cost: Blended, 30‑Day – blended cost for the CI over the last 30 days.
  • Cost: Unblended, 30‑Day / MTD – unblended (per‑rate) cost for the last 30 days and month‑to‑date.
  • Instance Utilization, 30‑Day / MTD – utilization indicators for the instance over the last 30 days and month‑to‑date (for example, based on CPU or other utilization signals).

These fields provide a quick view of recent spend and basic efficiency for the resource. They can serve as a jumping‑off point for deeper Cost Management reports and dashboards.

Breeze​

The Breeze section tracks Cloudaware Breeze agent deployment and data collection for the CI. Common fields include:

  • Breeze Path – path or identifier used by Breeze.
  • Breeze Agent – agent status or identifier.
  • Breeze: Last Update – timestamp of the last Breeze data update.
  • Breeze Is Active – checkbox/indicator showing whether Breeze is currently active.
  • Instance ID – instance identifier reference used by Breeze.
  • Breeze: Upgradable Packages, Security / Optional / Total – counts of upgradable packages by category.
  • Breeze: Platform – platform information detected by Breeze.

These fields show whether Breeze is installed and reporting, and surface package upgrade counts that feed patching and security workflows.

OS Info​

The OS Info section summarizes operating system lifecycle and metadata, often enriched from OS catalog sources. Example fields include:

  • OS Info: EOAS From – End of Active Support date.
  • OS Info: EOL From – End of Life date.
  • OS Info: Release Date – original OS release date.
  • OS Info: Latest Version Link – reference link to the latest supported version.
  • OS Info: Source – where the OS lifecycle data comes from.
  • OS Info: EOES From – End of Extended Support date.
  • OS Info: LTS From – Long‑Term Support start date or related context.
  • OS Info: Maintained – indicator showing whether the OS version is still maintained.

This information supports lifecycle risk management by making it easy to identify EOL/EOS systems and plan upgrades.

The RELATED CIs tab focuses on relationships and dependencies for the current CI.

For AWS EC2 instances, this tab surfaces provider and integration objects, such as:

  • AWS EC2 Instance Facts (Breeze Fact) – Breeze‑collected facts as key/value rows and JSON (agent version, identity/credential facts, maintenance/event facts).
  • AWS EC2 Instance Mount Points (Breeze Mount Point) – filesystem mount inventory with total size, utilization percentage, and filesystem type.
  • AWS Compute Optimizer EC2 Instance Recs. – rightsizing and optimization recommendations from AWS Compute Optimizer.
  • AWS EC2 Images – AMIs/images related to the instance context, showing image names and AMI IDs.
  • AWS EC2 Images (Source Instance) – AMIs specifically tied to the instance’s source lineage, with image names and AMI IDs.
  • AWS EC2 Instance SG Links – instance‑to‑security group associations with security group names and IDs.
  • PagerDuty Incidents – incident records linked to the CI, including incident IDs, summaries, and creation timestamps.

The tab may also surface related Cloudaware objects, such as:

  • CloudAware Vulnerability Scan CVEs – CVE‑level vulnerability scan results with titles, CVE identifiers, and CVSS base scores.
  • CloudAware OS Services – discovered OS services with status (running/stopped) and version information.
  • CloudAware OS Users – local OS user accounts with login capability and, where available, last‑login timestamps.
  • CloudAware Upgradable Packages – packages with available upgrades, including platform, security flag, package age, and Windows update metadata when applicable.
  • CloudAware Linux Packages – installed package inventory showing current and available versions and security flags.
  • CloudAware Vulnerabilities – roll‑up vulnerability records with CVSS, priority/severity/risk, scan dates, and vulnerability age.

This tab helps you understand the impact and blast radius, consolidate related operational and security context, and is often used for troubleshooting and change impact analysis.

Capacity Report Tab​

The CAPACITY REPORT tab provides time‑series performance charts plus a roll‑up performance table across common time windows. It is used for utilization review, trend analysis, and right‑sizing.

Time‑Range Selector​

At the top of the tab, a time‑range selector controls all charts and table calculations. Common quick filters include:

  • 1 DAY
  • 7 DAYS
  • 14 DAYS
  • 90 DAYS

A small settings (gear) icon is present to adjust view/options.

Performance Charts​

The top row typically contains three side‑by‑side charts:

  1. EC2 Instance CPU Utilization, %

    • Aggregation dropdown to switch between Minimum/Maximum/Average/SampleCount.
    • Line chart of CPU utilization over the selected time range.

  2. EC2 Instance Network In/Out, MB/s

    • Aggregation dropdown with Minimum/Maximum/Average/SampleCount.
    • Time series for inbound and outbound network throughput.

  3. EC2 Instance (Agent) Used Memory, %

    • Agent‑derived memory utilization (requires agent/telemetry).
    • Shows No data to display when agent data is not available.

Performance Summary Table​

A Performance table at the bottom summarizes key metrics over multiple windows. It typically includes:

  • A values‑mode dropdown (for example, CONVERTED VALUES) to normalize units (MB, %, etc.).
  • Time‑window columns such as 1‑Day, 7‑Day, 14‑Day, 30‑Day, 60‑Day, 90‑Day.
  • Rows for metrics such as:
    • CPU Utilization, Average, %
    • CPU Utilization, Max, %
    • Metadata No Token, Sum, Calls (IMDS/metadata access)
    • Disk Read, Sum/Max, Megabytes
    • Disk Write, Sum/Max, Megabytes
    • Network In, Sum, Megabytes
    • Network Out, Sum, Megabytes
    • Memory Used, Average, % (agent‑derived; shows “No data” when unavailable)
    • Disk Used, Average, % (agent‑derived; shows “No data” when unavailable)

Monitoring Status and Metrics​

Sections related to monitoring tools such as Zabbix, New Relic, Datadog, etc., may also be present. They typically include the monitoring agent status, host ID, the number of incidents, and other fields.

Data Availability and Gaps​

The tab clearly indicates collection gaps:

  • Charts can display No data to display when metrics are missing (for example, memory without an agent).
  • Table cells can show No data or blanks/dashes for metrics that are not collected or not available for the selected window.

In practice, CPU and network metrics usually come from cloud provider monitoring, while memory‑ and disk‑utilization metrics typically require an agent or equivalent OS‑level telemetry integration.

Security Tab​

The SECURITY tab surfaces security posture and findings for the CI. It typically includes:

  • Security Groups Rules – network controls affecting the instance, showing CIDR/subnet context and rule decisions for ingress/egress (for example, CIDR Block, Protocol, Port Range, Rule Action with allow/deny as colored pills).
  • CloudTrail Events – AWS API activity tied to the instance for audit and forensics (for example, CreateImage events on an EC2 Instance with event time and acting user).
  • Vulnerability Scanning – high‑level scan posture with last scan timestamp/result plus open findings by severity (Critical/High/Medium/Low).
  • CloudAware Upgradable Packages – patch backlog view listing packages with available updates, security flags, and age (the columns include the package name, e.g., nano or libxml2, Platform, the Security checkbox, Package Age).
  • CloudAware Vulnerabilities – roll‑up vulnerability records with scoring and prioritization (for example, CVSS Base Score, Priority, Risk, Scan Date, and Vulnerability Age).

The sections Benchmarks and CloudAware Policy Violations (CloudAware Operations) may be present if Cloudaware Compliance Engine (v1) is enabled.

Together, these sections help security, compliance and operations teams understand exposure, prioritize remediation, and trace changes or events that affect the CI.

Application Tab​

The APPLICATION tab shows how the CI (e.g., an EC2 instance) is mapped to an Application and an Application Tier. It combines a concise header, a visual attachment view, and a field‑level mapping table.

Application Header (Summary Strip)​

A compact summary area at the top surfaces the application context and cost:

  • Application – application name (display label).
  • Tier – application tier the CI belongs to (display label).
  • Cost: Total, 30‑Day – rolled‑up 30‑day cost attributed to the CI within the application context.

Attachment/Relationship Visualization​

Below the header, a horizontal relationship row visually describes how the CI is attached to the application. It typically includes:

  • Attachment method – the badge indicates how the CI–application association was created (for example, attached manually).
  • CI node – shows the CI class (for example, AWS EC2 Instance) and CI name/identifier.
  • Status – current operational state of the instance (for example, running).
  • Location attributes – key placement fields such as:
    • Region (for example, us-east-1).
    • Availability Zone (for example, us-east-1a).
    • Account Availability Zone (for example, us-east-1a).

This visualization is intended for quick validation that the correct CI is attached to the correct tier, and to provide immediate runtime/location context.

Application Mapping Fields​

At the bottom, a key-value table shows the resolved application and tier fields associated with the CI. Common fields include:

  • Application – application reference/name.
  • Application Tier – tier reference/name.
  • Application Tier Parent Type – parent object/type for the tier (if applicable).
  • Application Tier Parent UUID – unique identifier of the parent tier or object.
  • Application Tier Unique Name – unique display identifier for the tier.
  • Application Tier Api Name – API‑safe identifier used for integrations and automation.
  • Application Tier Client Name – client‑facing name/label for the tier.
  • Application Tier Cascade Attach – checkbox flag controlling whether attachment cascades via tier relationships.

Most values on this tab are read‑only context; associations and changes are usually performed through actions such as ATTACH TO APPLICATION in the CI header or directly in the Application UI layout. The tab mixes business context (application/tier) with operational context (state and region/AZ) to support ownership, impact analysis, and reporting.

Backups Tab​

The BACKUPS tab summarizes backup posture and recovery configuration for the CI. It combines a health summary, policy configuration, history lists, and detailed metadata.

Backup Health (Summary Card)​

At the top, a summary card provides a quick signal of backup coverage and recency:

  • A large circular gauge showing overall Backup Health (for example, 100%).
  • An Overview checklist with coverage by cadence, such as:
    • Daily Backups: x/x
    • Weekly Backups: x/x
    • Monthly Backups: x/x Each row shows a green check when the cadence is satisfied.
  • Last available backup – a timestamp/date link (for example, Thu, March 5, 2026).

Backup Policy (Configuration Card)​

A Backup Policy card shows the policy cadence being applied and, where permitted, allows editing:

  • Header: Backup Policy with a pencil Edit icon to adjust settings.
  • Policy cadence buttons, for example:
    • 1 day
    • 1 week
    • 1 month

These controls are used to view or configure policy behavior per retention period.

Backups History (Tabbed List)​

The history area displays backup records by cadence and as a combined list. It typically includes sub‑tabs:

  • Backups List - combined view, showing: Date – sortable date/time (for example, Fri, March 6, 2026). Period – a label indicating the cadence (Daily/Weekly/Monthly). Status – a label indicating state (for example, Normal).
  • Daily Backups - calendar view (month grid) that shows the selected month with left/right arrows to navigate months. he daily backup indicator shows a completed daily backup by highlighting the date cell with a green bar. The backup indicator is clickable.
  • Weekly Backups - calendar view (month grid) that highlights the week window (often shown as a bar spanning multiple days in that week, or a marker on the week’s scheduled day). Used to quickly confirm that one backup occurred for each week in the month. The backup indicator is clickable.
  • Monthly Backups - calendar view (commonly a month selector) that indicates whether the monthly backup exists for that month. The backup indicator is clickable.

This section provides quick validation that backups are occurring according to schedule and completing successfully.

Backup Details (Metadata Section)​

A metadata section surfaces the current backup posture and identifiers for the most recent backup artifacts. Common fields include:

  • Backup Health – overall health percentage.
  • Backup Tag – policy tag encoding cadence/retention (for example, 1d1w1m).
  • Last Backup AMI ID – identifier for the most recent backup image or artifact.
  • Last Backup AMI – linked reference to the AMI record.
  • Last Backup Date – timestamp of the last backup.
  • Replicate Tag – replication/target‑region tags (for example, 2@us-west-1; 1@us-west-2).

Visual Conventions​

  • Health and success states are emphasized in green (gauge ring, checkmarks, Normal status labels).
  • Cadence is encoded with coloured labels (Daily/Weekly/Monthly).
  • Most fields are read‑only status and identifiers; policy changes, when allowed, are initiated via the pencil/edit control.

This view helps ensure that critical resources have appropriate backup and recovery coverage, and highlights gaps that require action.

Change Management Tab​

The CHANGE MANAGEMENT tab focuses on change governance and operational history for the CI. It is organized into two audit‑style panels: Approval History and Changes History, both of which support clear “empty state” messaging when no records exist.

Approval History​

The section tracks approval workflow events tied to the CI (for example, approval requests, approvals, and rejections). Use:

  • Primary action button (top‑right): SUBMIT FOR APPROVAL – initiates an approval request for the CI or related change record.
  • Content area: table/list region that displays approval entries when present.
  • Empty state: centered message such as No records to display when no approval requests or approvals exist.

Changes History​

The section displays a chronological log of recorded changes or actions related to the CI. Use:

  • Time filter (top‑right), for example: PERIOD: LAST 30 DAYS – a dropdown to change the reporting window.
  • Table columns, typically:
    • Date – sortable, with a sort indicator on the header.
    • User – who performed the change.
    • Action – what was changed or executed.
  • Empty state: table message such as No records found for selected period. when the filter returns no entries.

In practice, you submit a CI for approval (where required by process) and then use Changes History to review who changed what and when, scoped by the selected period. This tab helps connect CMDB data with formal change processes and supports audits and post‑incident reviews.

Tags Tab​

The TAGS tab provides a table‑based interface for viewing and managing user‑defined tags (key/value metadata) on the CI.

Header Actions​

Header actions in the top‑right corner drive analysis and tag management:

  • SHOW IN TAG ANALYZER – opens the CI’s tags in a dedicated tag analysis view for cross‑resource/tag reporting.
  • + ADD TAG – adds a new tag entry (key/value pair).
  • DELETE SELECTED – bulk delete for selected rows; disabled until at least one row is selected.

Tags Table​

The main grid lists one row per tag and supports both bulk and per‑row operations. Typical columns and controls include:

  • Row checkbox – select tags for bulk actions.
  • Name – tag key (for example, Environment, Name, etc.).
  • Value – tag value (for example, prod, 1d1w1m, etc.).
  • CaTag Enabled – per‑tag checkbox used to mark the tag for Cloudaware tagging behavior (for example, governance or propagation flags).
  • Row actions – actions on the right, such as:
    • EDIT (pencil) – edit tag name/value and related settings.
    • DELETE (trash) – remove the single tag.

Footer/Count​

At the bottom, a summary line shows tag usage, for example:

  • Tags (user‑defined) – current number of user‑defined tags versus the maximum provider-allowed for the CI.

The table supports bulk selection via checkboxes and per‑row management via Edit/Delete links. DELETE SELECTED is context‑sensitive and only enabled when at least one tag is selected. This tab is frequently used to enforce tagging standards and drive cost, ownership, and compliance reporting.

Systems Manager Tab​

The SYSTEMS MANAGER tab shows integration with host‑ and OS‑level management tools such as AWS Systems Manager (SSM). It surfaces whether the instance is enrolled in SSM and key health and update status fields.

Typical fields include:

  • EC2 Systems Manager: Activation ID – SSM activation identifier, commonly used for hybrid/managed activation scenarios.
  • EC2 Systems Manager: Agent Version – installed SSM agent version when detected.
  • EC2 Systems Manager: Association Status – status of SSM associations applied to the instance (for example, State Manager or configuration associations).
  • EC2 Systems Manager: Is Managed – checkbox indicating whether Systems Manager currently manages the instance.
  • EC2 Systems Manager: Ping Status – connectivity/heartbeat status between the instance and SSM.
  • EC2 Systems Manager: Updates Installed – count or status of updates successfully installed (patch compliance signal).
  • EC2 Systems Manager: Updates Needed – count or status of missing updates.
  • EC2 Systems Manager: Updates With Error – count or status of updates that failed or reported errors.

Values are displayed inline in the grid; booleans appear as checkboxes (for example, Is Managed). When Systems Manager data is unavailable, these fields may be blank or unpopulated, indicating that SSM does not manage the instance or that telemetry is not currently being collected.