Tracking the results of a cloud discovery

Discovery and Service Mapping administrators can track the results of cloud discovery, including a failed discovery, by accessing different types of records in the instance.

Record type Description
Cloud API Trail and Cloud Orchestration Trail View the discovery operations run by the Cloud API, view the payload that the instance receives, and any errors that occurred. A discovery of close resources creates a record in both trails. Both trails provide error messages that you can use for debugging a failed cloud discovery.

After you run discovery on a service account, look in these trails.

Discovery status See a summary of a discovery that you initiated from a discovery schedule on resources in a cloud environment. When you perform the initial discovery of datacenters for a service account, a discovery status is not created.
You can also access these records related to the discovery:

Access the Cloud API Trail after discovery

After you run Discovery on datacenters in an AWS or Azure cloud, you can check the Cloud API trail for the results of the discovery and for log entries.

Before you begin

Role required: discovery_admin

About this task

You can also check the Cloud Orchestration Trail after discovery.

Procedure

  1. Navigate to Cloud API > Cloud CAPI Trail.
  2. Sort or filter the list by the desired field, such as Date created or Status. A failed discovery displays Error in the Status column.
  3. Review the values in the form fields (see table).
    The Cloud API Trail form
    Field Description
    Dynamic route ID An auto-generated ID number for the entry.
    Mid name The name of the MID Server through which the discovery was performed.
    Route status Whether or not the discovery operation run by the API was successful. Possible values are:
    • success
    • error
    • executing
    Input parameters The input parameter that generated the API trail record. This value is usually the datacenter in which the discovery was run.
    Interface name
    Invoked by This value is always CMP when running cloud discovery.
    Method name The interface operation from the Cloud API that processed this record.
    Provider name The cloud provider.
    Version The version specified in the Cloud API.
  4. Click on any of the log messages to learn more about these items:
    Log key Description
    route_data Information about the Cloud API calls.
    dynamic_route Information about the actual route the data took, including URIs.
    route_result The payload received by the instance, or a description of the result of the data transfer. The payload
    chunk_number The number of data chunks that the instance received.
    route_status Whether or not the route connection and payload transfer was successful.
    route_error The error that occurred. For example, the error Failed to list loadbalancer Failed : HTTP error code : 403 means that your credentials were incorrect and Discovery could not access the cloud resource.
    error_detail More details about the error, including the Cloud Management API and connector that was used in the attempted discovery, and the errors that the cloud provider threw.

Access the Cloud Orchestration Trail after discovery

Before you begin

Role required: discovery_admin

About this task

You can also check the Cloud API Trail after discovery.

Procedure

  1. Navigate to Cloud API > Cloud CAPI Trail.
  2. Sort or filter the list by the desired field, such as Date created or Status. A failed discovery displays Error in the Status column.
  3. Review the values in the form fields (see table).
    The Cloud Orchestration Trail form
    Field Description
    Number An auto-generated number for the trail entry.
    Level One of the following:
    • Debug
    • Info
    • Warn
    • Error
    Template The component, such as a resource block or blueprint, on which a Cloud Management action was applied.
    Template Instance The datacenter in which the cloud resource is located.
    User The user involved in the transaction.
    User group The user group that the user belongs to.
    Created The date and time that the system created the entry.
    Milestone If this transaction is a milestone. You can configure the form to see this field.
    Request Item The service catalog request generated for the transaction.
    Step The step that identifies additional information about the transaction, including the component and the stage. You can configure the form to see this field.
    Catalog Item The catalog item, if any, that was involved in the execution.
    Message The error message or successful completion message. This could include items like the ID of the corresponding message in the Cloud API Trail record or the Cloud API that was invoked.
    Message details Details about the error, such as an HTTP error.