Configure Metric Collection in a Consolidated Setup

In a consolidated setup, perform the following steps on your Operations Connector host to integrate VROPS metrics into OMi:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntVROps and open the vrops_metrics.conf file (the metric integration configuration file) in a plain text editor.

2. In the configuration file, replace the value in quotation marks in the line of the following option:

   vrops-hostname: The FQDN or IP address of your VROPS UI virtual machine.

3. Review the preconfigured values of basic configuration options and adjust them as needed. Add and configure advanced options if necessary. For descriptions of basic and advanced options, see Integration Configuration Options topic.

4. Save your changes.

5. Log on to the Operations Connector web interface and import the policy for VROPS metrics by navigating to the <OvDataDir>/installation/HPBsmIntVROps/policies directory and selecting the following files:

   • 77bc423c-7c54-4e55-a702-c7e261b443d5_data
     

   • 77bc423c-7c54-4e55-a702-c7e261b443d5_header.xml

   The type of the Operations Connector policy for VROPS metrics is REST Web Service Listener. Operations Connector validates it after importing.

6. Review the policy to make sure its settings are proper for yourOpsCx for VROPS configuration.

7. From the Operations Connector web interface, activate the imported policy.

8. Open a Command Prompt window (command shell).

9. If Operations Connector is hosted on a Linux system, change the current directory to cd /opt/OV/bin64.

10. Run the following commands to set the VROPS user name and password on the OpsCx for VROPS so that the Connector can get metrics data from VROPS machine.

    Only the VROPS user with administrative or REST API privileges can access the VROPS machine for collecting metrics. For information on creating user account with these privileges, see the section VROPS user roles and accounts in the topic Installation Prerequisites.

    genintcrypt --generate

    genintcrypt --set vrops_user

    genintcrypt --set vrops_password

    Specify the credentials of the user account with administrative or REST API privileges for vrops_user and vrops_password.

    The user name can be in any of the following formats:

    • username@domain
    • username@domain@auth_source

    Type the correct user name and password when prompted. The typed text is not visible in the command prompt window. If you make an error, do not attempt to correct the text, but rather run the command again.

11. To verify the entered credentials, run the following commands:

    genintcrypt --check vrops_user

    genintcrypt --check vrops_password

    A correct configuration is denoted by the following response of each command:

    genintcrypt:Value exists for ID '<ArgumentName>'

12. If Operations Connector is hosted on a Linux system, change the current directory to cd /opt/OV/bin

13. To register the corresponding component with Operations Agent, run the following command:

    For Windows:

    ovcreg -add \
"<OvDataDir>\installation\HPBsmIntVROps\ovc\HPBsmIntVROps_Metrics.xml"

    For Linux:

    ovcreg -add \
<OvDataDir>/installation/HPBsmIntVROps/ovc/HPBsmIntVROps_Metrics.xml

14. To start the metric collection service, run the following command:

    ovc -start vropsm

    Startup of the service initiates metric collection from VROPS and forwarding of the metrics to OMi.

Verify your connection settings by checking the contents of the directory for persistency data files on the Operations Connector host. The path of the directory is defined by the persistency-dir option in the metric integration configuration file. If the directory is empty or its contents do not appear to be updated, check the corresponding OpsCx for VROPS log file. For details, see Log Files topic.

If you deactivate the policy for VROPS metrics, metrics continue to be collected while the policy remains inactive after the deactivation. The processing and forwarding of accumulated metrics resumes when you reactivate the policy.

Related topics

Configuration Options

Product Log Files

Installation Prerequisites