Note

 

This documentation supports the 20.17.01 version of Remedyforce.

To view the latest documentation, click

Verifying Discovery Server status

This section provides information about the Discovery Server status logs that you can monitor to identify issues related to the Discovery Server.

Overview of the Discovery Server status logs

The Discovery Server status logs help you to monitor the activities of the server, such as:

  • Enabling and disabling of discovery
  • Provisioning of the Discovery Server
  • Updating Discovery Server password
  • Viewing the success or failure status of the request to keep the Discovery Server alive

Note

If you have configured discovery in your organization, Remedyforce sends a request to the Discovery Server in every 24 hours to maintain and check that the link between the two is operating. In a sandbox organization, if this request is not sent continuously for a period of 10 days, the Discovery Server is deleted.

The Discovery Server logs are available to you in the Discovery Audit Logs object.

While monitoring, if you frequently see logs related to disabling of discovery, decommissioning of the Discovery Server, or failure of sending the request to keep the Discovery Server alive request (for example, you continuously see the Last_Discovery_KeepAlive_Failure_Exception log once in every 10 days), your Discovery Server might be impacted or accidentally deleted. To resolve the issue, contact BMC Support and provide the log details.

The following figure shows the logs generated for the Discovery Server.

The following table describes the Discovery Server status logs:

Log nameDetails
Last_Discovery_Enabled_Date

Stores the latest date on which discovery was enabled in your Salesforce organization.

Discovery_Server_first_Provisioning_DateStores the date of the first request to create the Discovery Server.
Last_Discovery_Provision_DateStores the latest date of the Discovery Server creation request.
Last_Discovery_KeepAlive_Success_Date

Stores the latest successful request sent to keep the Discovery Server alive.

Last_Discovery_KeepAlive_Failure_ExceptionStores the details of the last failure or exception that occurred when the request to keep the Discovery Server alive was unsuccessful.
Last_Discovery_KeepAliveFailure_AlertSent_DateStores the latest date on which an email notification was sent to inform failure in sending the request to keep the Discovery Server alive.
Last_Discovery_DaysRemaining_AlertSent_DateStores the latest date on which an email notification was sent to inform the number of days remaining to delete the Discovery Server.
Last_Discovery_DaysRemainingCrossed_DateStores the latest date when the number of days remaining to release the Discovery Server reaches 0 or less.
Discovery_Server_first_Decommissioning_DateStores the date when discovery was disabled in your Salesforce organization.
Last_Discovery_Decommission_DateStores the latest Discovery Server deletion date.
Last_Discovery_Disabled_DateStores the latest date on which discovery was disabled.
 

Accessing the Discovery Server status logs

The Discovery Server status logs are available to you in the Discovery Audit Logs object. To view the status logs, you will need to create a tab for the object.

  1. To create a tab for the Discovery Audit Logs object, perform the following actions:
    1. Click Setup > Tabs.
    2. On the Custom Object Tabs section, click New.
    3. On the Step 1. Enter the Details page, in the Object list, select Discovery Audit Logs.
    4. In the Tab Style field, select a tab style.
    5. (Optional) In the Description field, enter a short description of the custom object tab.
    6. Click Next.
    7. On the Step 2. Add to Profiles page, in the list corresponding to the Apply one tab visibility to all profiles radio button, select Default off.
    8. Select the Apply a different tab visibility for each profile radio button.
    9. In the Profile column, identify the Salesforce profile to which you have assigned the Remedyforce Administrator permission set (for example, System Administrator).
    10. In the Tab Visibility column, select Default On for the Salesforce user profile to which you have assigned the Remedyforce Administrator permission set.
    11. Click Next.
    12. On the Step 3. Add to Custom Apps page, in the Custom App column, identify BMC Remedyforce.
    13. In the Include Tab column clear the Include Tab check box and select BMC Remedyforce.
    14. Click Save.
  2. Click All Tabs (+).
  3. Click the Discovery Audit Logs tab.

Related topics

Enabling and configuring agentless discovery

Disabling discovery

How discovery works

Managing discovered devices

Troubleshooting BMC Remedyforce CMDB 2.0 issues

Was this page helpful? Yes No Submitting... Thank you

Comments