Skip to main content

Wormly

Integrate Wormly with Cloudaware to inventory uptime checks, hosts, sensors, and sensor status for unified monitoring governance.

info
  • Audience: Cloudaware administrators, SRE teams, NOC teams, and monitoring teams
  • Outcome: Wormly uptime monitoring data is available in CMDB for host visibility, sensor status review, monitoring coverage, and reporting

Capabilities​

The integration supports:

  • Read-only discovery of Wormly hosts, sensors, sensor status, and daily uptime reports
  • CMDB visibility into uptime monitoring coverage and host sensor health
  • Monitoring governance reporting for uptime checks and related assets
  • Search and reporting for Wormly objects using CMDB Navigator, CMDB list views, and reports

Prerequisites​

Before you begin, make sure you have:

  • Access to a Cloudaware account.
  • A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
  • Wormly API key with read access.

Add a Wormly Account to Cloudaware​

  1. In Cloudaware, go to Admin.
  2. Find Wormly, then click + ADD.
  3. Enter the following values:
    • Name: A display name for the Wormly integration.
    • API Key: The Wormly API key with read access.
  4. Click Save.
  5. Confirm that the integration status indicator is green.
tip

Allow the initial discovery cycle to complete after enabling the integration.

View Wormly Data in CMDB​

  1. In Cloudaware, open CMDB Navigator.
  2. Search for objects, e.g., Wormly Hosts, to open the list view with relevant discovered records.

Supported Objects​

Cloudaware ingests the following Wormly objects:

Wormly ObjectCMDB Object API Name
Wormly Daily Uptime ReportCA10__CaWormlyDailyUptimeReport__c
Wormly HostCA10__CaWormlyHost__c
Wormly Host SensorCA10__CaWormlyHostSensor__c
Wormly Host Sensor StatusCA10__CaWormlyHostSensorStatus__c

Troubleshooting​

note

Initial data collection may take time to complete.

Authentication Fails or Integration Shows Red Status​

  • Verify that the Wormly API key is correct and active.
  • Confirm that the API key has read access to the expected Wormly hosts and sensors.
  • Re-enter the API key by editing the integration in Cloudaware.

No Wormly Data Appears in CMDB​

  • Allow the initial discovery cycle to complete.
  • Confirm that Wormly contains hosts, sensors, and uptime data for the expected monitoring scope.

Some Hosts or Sensors Are Missing​

  • Confirm that the missing hosts or sensors are visible in Wormly.
  • Check whether the API key has access to the monitoring scope that contains the missing records.
  • Review recent Wormly changes after the next Cloudaware discovery cycle completes.

Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name and a brief description of the issue.

Reconfigure or Remove the Integration​

warning

To rotate the Wormly API key, edit the existing integration instead of deleting and re-creating it.

Update the Integration Details​

  1. Go to Admin.
  2. Select Wormly.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Edit.
  5. Update the required fields.
  6. Click Save.

Remove the Integration from Cloudaware​

  1. Go to Admin.
  2. Select Wormly.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Delete.
  5. Confirm the deletion if prompted.

Security Notes​

  • Use a dedicated Wormly API key for Cloudaware discovery where possible.
  • Grant the API key only the read access required for host, sensor, and uptime report discovery.
  • Do not reuse personal administrator keys for production integrations.
  • Rotate the Wormly API key according to your organization's credential management policy.
  • Review Wormly data visibility with your monitoring team, because host names, sensor status, and uptime reports may contain sensitive operational context.
  • Revoke unused Wormly API keys when the integration is retired.