When you enable Historic Data Collection, vRealize Operations Manager learns the Dynamic Thresholds for your environment faster. Instead of the usual 2‐6 weeks it takes for vROps to collect enough data to determine appropriate Dynamic Thresholds, this feature enables you to pre‐load historic data into vROps in, for example, about 10 hours for 30 days of historic data.

  • Configuring Historic Data Collection for a New Adapter Instance
  • Load Historical Data for an Existing Adapter Instance

Prerequisites

Configuring Historic Data Collection for a New Adapter Instance

Use this procedure to import existing historical data to your Epic Care Systems Analytics adapter.

  1. Log in to vRealize Operations Manager virtual machine as root. For example, use an ssh command.
  2. Open the epiccare.properties file in an editor.

    /usr/lib/vmware-vrops/user/plugins/inbound/epiccare_adapter3/conf/epiccare.properties

  3. Locate the control parameters at the end of the file. For example:

    collectHistoricDataEnabled=false

    historicDataToCollectInHours=0

    historicDataChunkCollectionInHours=1

    • collectHistoricDataEnabled controls whether historic data collection is enabled or not. It can either be true or false. To enable Historic Data Collection, set this to true.
    • historicDataToCollectInHours is the number of hours to go back and start collection. This is typically set to 30 days, which is 720 hours.
    • historicDataChunkCollectionInHours is the number of hours of data to collect in every collect cycle.

      The default collect cycle for the adapter is 5 minutes and the adapter tries to collect historicDataChunkCollectionInHours hours of data in every cycle. This can typically be set to 6 hours. Depending on your configuration of System Pulse, you can reduce this to 2 or 1 hour if 6 hours causes too much load on System Pulse.

      For example, the adapter configured for Historic Data Collection for the last 30 days using a chunk size of 6 hours will have the following configuration:

      collectHistoricDataEnabled=true

      historicDataToCollectInHours=720

      historicDataChunkCollectionInHours=6

  4. Create an adapter instance. See: Creating an Adapter Instance (Care Systems Analytics).

    • Historic data should be available for viewing in about 10 minutes.
    • When the Historic Data Collection is current, the Epic Adapter continues to collect the latest metrics from System Pulse.

Load Historical Data for an Existing Adapter Instance

If the Care Systems Analytics adapter instance exists, complete the procedure below.

  1. Configure an adapter instance. See: Creating an Adapter Instance (Care Systems Analytics).
  2. Stop adapter collection.

    From the Environment Overview tab, expand the Adapter Instances list, select the Care Systems Analytics for Epic adapter instance list. In the list detail, select the Care Systems Analytics for Epic adapter instance and click the Stop Collection icon.

    Note: DO NOT expand the Care Systems Analytics for Epic adapter instance list. You want to stop collection for the entire Care Systems Analytics for Epic adapter instance.
  3. Log in to vRealize Operations Manager virtual machine as root. For example, use an ssh command.
  4. Delete the following file:

    /usr/lib/vmware-vrops/user/plugins/inbound/epiccare_adapter3/work/lastcollect.properties

  5. Configure Historic Data Collection. See: Configuring Historic Data Collection for a New Adapter Instance, above.
  6. Log in to vRealize Operations Manager and restart collection.
  7. From the Environment Overview tab, expand the Adapter Instances list, select the Care Systems Analytics for Epic adapter instance list. In the list detail, select the Care Systems Analytics for Epic adapter instance and click the Start Collection icon.

What to do next