Skip to main content

Custom Fields from Facts

Cloudaware Fact2Field functionality allows users to select Breeze facts that Cloudaware should convert to fields on objects.

Cloudaware propagates fields that contain the caFact_ prefix when they match a Breeze fact. For example, if you create a caFact_uptimehours field, Cloudaware searches for the uptime_hours fact and uses its value.

This guide explains how to turn discovered facts, custom facts, and integration signals into CMDB fields that teams can use in list views, reports, dashboards, policies, and automation.

When to Use This Guide​

Use this guide when a fact is already available in Cloudaware, but users need it exposed, normalized, or derived as a stable CMDB field.

Typical examples include:

  • Creating a custom field from a Breeze Agent custom fact.
  • Deriving a business-friendly field from an OS, Ansible, Chef, or other integration fact.
  • Normalizing several raw fact values into one reporting field.
  • Making fact-based values available for reports, dashboards, policies, or outbound integrations.

High-Level Implementation Flow​

  1. Identify the fact source and confirm that the fact is present on the expected CI records.
  2. Decide whether the target value should be a direct custom field, a formula field, a rollup, or an enrichment output.
  3. Define the field label, API name, data type, ownership, and field-level security.
  4. Populate or derive the field from the source fact.
  5. Add the field to the relevant page layout, list views, reports, or dashboards.
  6. Validate the field on a small record sample before wider rollout.

Supported Objects​

caFact_ fields are supported for the following Cloudaware objects:

Object
AWS EC2 Instance
AWS EKS Cluster
Azure Virtual Machine
Azure VM Scale Set Instance
Azure AKS Cluster
Google GCE Instance
VCenter Virtual Machine
CloudAware Physical Server

Create a caFact Field​

  1. Log in to Cloudaware and go to Setup.

  2. Go to Object Manager.

  3. Select an object, for example CloudAware Physical Server.

  4. Select Fields & Relationships.

  5. Click New.

  6. For the field type, select one of the Text field types, then click Next.

  7. Enter the field details:

    FieldValue
    Field LabelSet a human-readable field name, for example User ID.
    Field NameReplace the auto-generated name with a value that starts with caFact_, for example caFact_userId. Field names are case-sensitive.
    Help TextProvide the full fact name, for example ansible.user_id.

  8. Click Next.

  9. Select the user profiles that should be able to see the new field, then click Next.

  10. Select the layout where the new field should be visible.

  11. Click Save.

note

caFact_ fields may not populate immediately after a new field is added. Allow time for the update action on the Fact object to process.

Breeze Fact Examples​

Linux examples:

  • architecture
  • bios_release_date
  • bios_version
  • breeze_agent_id
  • domain
  • ec2_metadata
  • ec2_product_codes
  • ec2_userdata
  • memorysize
  • memorysize_mb
  • os
  • system_uptime
  • uptime_seconds

Windows examples:

  • azure
  • domain
  • ec2_metadata
  • ec2_userdata
  • fact_role
  • facterverversion
  • interfaces
  • macaddress_ethernet
  • netmask_ethernet
  • puppetversion
  • rubyplatform
  • rubyversion
  • serialnumber
  • timezone

For the full supported fact list, see OS Facts Matrix.