Integrating with VMware vROps

vRealize Operations (vROps) is an IT operations management platform of VMware, to monitor and manage the performance, capacity, and health of IT infrastructures, using the AI/ML technology.

Configure an integration with VMware vROps, to view the alert, metric, and topology data from VMware vROps in the following products and derive actionable insights:

  • BMC Helix Operations Management
    BMC Helix Operations Management displays VMware vROps alerts as events.
  • BMC Helix Discovery
  • BMC Helix AIOps


As a tenant administrator, perform the following steps to integrate with VMware vROps, verify the integration, and view the collected data in various BMC products.

Planning for the connection

  • Depending on the location (SaaS, on-premises) of the third-party product, choose one or more BMC Helix Intelligent Integrations deployment modes and review the corresponding port requirements. For information about various deployment modes and port requirements, see Deployment scenarios.
  • Based on the deployment modes, use the BMC Helix Intelligent Integrations SaaS deployment or the BMC Helix Intelligent Integrations on-premises gateway or both. For more information about the gateway, see Deploying the BMC Helix Intelligent Integrations on-premises gateway.

  • The on-premises gateway must be able to reach the third-party product on the required port (default is 443).
  • (Applicable for BMC Helix Intelligent Integrations for version 24.1.02) If you want to collect topology data from third-party by using BMC Helix Intelligent Integrations, BMC Helix Discovery must already contain the third-party entities. When entities will be collected by BMC Helix Intelligent Integrations later after configuring the connection, the existing entities in BMC Helix Discovery are updated with external_id and any other additional attributes.

In the preceding list, third-party product refers to VMware vROps.

Supported versions

This connector supports version 8.5.0 of VMware vROps for data collection.

Configuring the connection with VMware vROps

  1. Access BMC Helix Intelligent Integrations:

    • BMC Helix Intelligent Integrations SaaS – Log on to BMC Helix Portal, and click Launch on BMC Helix Intelligent Integrations.
    • BMC Helix Intelligent Integrationson-premises gateway – Use the following URL to access BMC Helix Intelligent Integrations:
      https://<hostName>:<portNumber>/swpui
  2. On the CONNECTORS  tab, click in the SOURCES panel.

  3. Click VMware vROps .
  4. Specify the following details for the source connection:
    1. Specify a unique instance name. 

      Best practice

      We recommend that you specify the instance name in the following format: 

      <sourceType>_<sourceControllerServerName>_<InstanceQualifier>

      The instance qualifier helps you to distinguish the multiple instances configured from the same source server. For example, you can name your instances as vROps_Host_PROD, vROps_Host_TEST, and so on.

    2. Specify the VMware vROps host name and port number (default value is 443).
    3. Ensure that the HTTPS check box is selected to indicate that you plan to use an https connection to the VMware vROps host.

      Warning

      We recommend that you do not select the Allow Unsigned Certificate option in a production environment.  You might want to select this option to allow unsigned certificates in a test environment. See the VMware vROps    documentation to learn how to install SSL certificates.


    4. Specify the number of maximum concurrent REST API requests that should be executed during a collection schedule (de fault value is 5).
    5. Specify the user name and password. Ensure that the specified user can access the VMware vROps REST API.
    6. Specify the time, in seconds, after which no attempt should be made to establish a connection (default value is 30).
    7. Click Proxy and specify if you want to configure a proxy server. If yes, specify the host name and port number (default value is 8888).
  5. Click VALIDATE AND CREATE.
    The specified connection details are validated and the corresponding source connection is created in the Source Connection list.
  6. Select the source connection that you created from the list if it is not selected already.

    Important

    The destination host connection is created and configured automatically for each tenant when the source connection is created.

  7. Ensure that the options for the datatypes for which you want to collect data are selected.
  8. Click a data type and specify the configuration parameters in the Collectors section as described in the following table:

    Parameter NameData Type

    vROPS Managed Alerts

    vROPS Managed MetricsvROPS Managed Topology

    Specify the data collection frequency by using one of the following methods:

    • Constantly by specifying the schedule in minutes, hours, or day using the Duration option
      Default: 5 minutes

      Example:
      Collection Schedule
      is set to 5 mins.
      Current time is 00:30.

      If you run the collector just after 00:30, data is collected every 5 mins, first at 00:30 and next at 00:35, and so on.  

    • Periodically by specifying the schedule through a cron expression using the Cron schedule option 

      A cron expression is a string consisting of five subexpressions (fields) that describe individual details of the schedule.  These fields, separated by blank spaces, can contain any of the allowed values with various combinations of the allowed characters for that field.
      Default: */5 * * * * (evaluates to 5 minutes)

      Format:
      Minutes Hours (24-hour format) Day of Month Month Day of Week

      Example:
      If you specify 10 15 3 7 * , data is collected at 15:10 hours every third day in the month of July.

    For more information about how this parameter affects data collection,  see Data collection schedule.

    (tick)


    (tick)


    (tick)


    Specify the historical time period (in minutes) from the current time for which the data should be collected.

    Default: 5 minutes

    Example:

    Collection Schedule is set to 5 mins.
    Data Collection Window is set to 5 mins.
    Current time is 00:30.

    If you run the collector just after 00:30, data is collected first at 00:30 for the interval, 00:25 - 00:30, and next at 00:35 for the interval, 00:30 - 00:35, and so on.

    For more information about how this parameter affects data collection,  see Data collection window.

    (tick)


    (tick)


    (tick)


    Specify the time (in minutes) by which the data time window should be shifted back on the timeline.

    This parameter is useful in delayed data availability situations.

    Default: 0 minutes

    Example:

    Collection Schedule is set to 5 mins.
    Data Collection Window is set to 10 mins.
    Data Latency is set to 2 mins.
    Current time is 00:30.

    If you run the collector just after 00:30, data is collected first at 00:30 for the interval, 00:18 to 00:28 and next at 00:35 for the interval, 0:23 to 00:33, and so on.

    For more information about how this parameter affects data collection, see Data latency.

    (tick)


    (tick)


    (tick)


    Extract data for Adapter Kinds

    Ensure that VMWARE is selected.

    Supported adapter kind: VMWARE

    (tick)

    (tick)

    (tick)

    Resource Kinds

    • To collect alert and topology data, select at least one option from this list.
    • To collect metrics data, click to add a slot. Select the Resource Kinds.
      You need to select only one resource kind in each slot to collect metrics filtered by resource names that match a specified regular expression (regex). By default, the HostSystem option remains selected. You can change it by selecting other option from the list.
      You can add multiple slots with different combinations of resource kind and regex

    The following resource kinds are supported:

    • HostSystem
    • VirtualMachine
    • ClusterComputeResource 
    • Datacenter 
    • Datastore 

    • VMwareAdapter Instance 

    For information about collected metrics for host systems and virtual machines, see the following sections in the vRealize Operations documentation Open link :

    • Host System Metrics
    • Virtual Machine Metrics
    • Calculated Metrics

    (tick)

    (tick)

    (tick)

    Resource Name Regex

    Specify the regular expression for the resource name. Metrics are collected for the resources whose names match the regular expression.

    Examples:

    • To collect metrics for the resource names starting with aus, specify the regex as aus-.* 
    • To collect metrics for the resource names ending with aus , specify the regex as .*aus$
    • To collect metrics for all resources, specify the regex as .*

    Important : You can specify multiple regular expressions for the same resource kind. However, ensure that regular expressions are not conflicting. For example, do not enter, center-* and [^center].*. The former expression collects metrics for the resource names whose names start with center. The later collects metrics for the resource names whose names do not start with center .

    (error)

    (tick)

    (error)

    Include Resource Properties

    Select this option if you want to collect the resource properties data (granular level attributes data), which is required for topology creation in BMC Helix Discovery.

    Important: Data collection might take longer for the first time if you select this option.

    (tick)

    (tick)

    (tick)

    Batch Parallelism

    Specify the number of threads that you want to be executed in parallel to collect data.

    (error)

    (tick)

    (error)

    Criticality

    Specify the criticality for the alert data, for example, Critical, Warning, and Information.

    Data for all criticality levels is collected if you don't specify any criticality.   

    (tick)

    (error) (error)

    Alert Type

    Specify the type of the alert data you want to collect, for example, Administrative and Network alerts.

    The connector collects all alerts if you don't specify any alert type. This list is updated automatically from VMware vROps .

    (tick)

    (error) (error)

    Alert Sub Type

    Specify the sub-type for the selected Alert Type to collect alerts based on the specified type and sub-type, for example, Availability and Compliance.

    The connector collects all alerts if you do not specify any alert sub-type. 

    This list is updated automatically from VMware vROps .

    (tick)

    (error) (error)

  9. Click CREATE COLLECTORS to create the required collector streams for the selected data types.
  10. Click a data type and specify the configuration parameters in the Distributors section as described in the following table:

    Parameter NameDefault

    Max Batching Size

    Specify the maximum number of data items to send in a single POST request to the destination API. The batch size depends on the destination’s ability to buffer the incoming data.

    250

    Max Batching Delay

    Specify the maximum time (in seconds) to wait before building a batch and processing.

    3 seconds

    Base Retry Delay

    Specify the initial time (in seconds) for which to wait before retrying to build a batch and processing. The waiting time increases in the following sequence: n1, n2, n3, and so on, where n indicates the number of seconds.

    For example, if you set the value to 2 seconds, retry is performed after 2, 4, 8, 16, ... seconds.

    2 seconds

    Max Intra-Retry Delay

    Specify the maximum limit for the base retry delay. For example, if you set the value of this parameter to 60 seconds and the value of the Base Retry Delay parameter to 2 seconds, retries would be performed 2, 4, 8, 16, 32, 64, 64,...seconds later again.

    60 seconds

    Max Retry Duration

    Specify the total time for retrying a delivery. For REST destinations, a delivery is a batch of data items in one POST request. 

    For example, if you set the value of this parameter to 8 hours, and the value of the Base Retry Delay parameter to 2 seconds, requests are sent for 2+4+8+16+32+64+132... until 8 hours in total duration is reached. After that, no subsequent attempts are made to retry the delivery.

    The assumption here is that if there is an outage or other issue with the destination tool, recovery should take less than the value of the Max Retry Duration parameter to complete.

    5 minutes

    Attributes To Be Dropped When Updating Events

    Specify the event attributes that you do not want to get updated in BMC Helix Operations Managementwhen updating the event data. 

    All event attributes are collected from the source to BMC Helix Intelligent Integrations , but whatever attributes you specify here are not sent to BMC Helix Operations Management, while updating the event data.  

    For example, if you do not want event's severity, source address, source category, and sub-category to be updated in BMC Helix Operations Management, you need to specify those attributes as severity,source_address,source_category,source_subcategory, in a comma-separated format.


  11. Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data types.
  12. Click one of the following buttons:
    • SAVE STREAM : Click this button if you want to edit the integration details before creating the instance. After you save the stream, the connector that you just created is listed in the SOURCES panel. Move the slider to the right to start the data stream.
    • SAVE AND START STREAM : Click this button if you want to save the integration details and start receiving data immediately.

    Important

    For a data stream, the Run Latency (max/avg), Items (Avg per Run), and Last Run Status columns on the Streams page might show No Runs as the status during the data collection process. After the completion of the process, these columns are updated with an appropriate status.


    For more information about data streams, see Starting or stopping data streams .


Verifying the connection

In BMC Helix Intelligent Integrations , on the SOURCES panel, confirm that the data streams for the integration you created are running. Data streaming is indicated by moving colored arrows.

  • A moving dark blue arrow () indicates that the event stream is running. Event data will be pushed according to the configured Collection Schedule interval.
  • A moving red arrow () indicates that the metric stream is running. Metric data will be pushed according to the configured Collection Schedule interval.
  • A moving light blue arrow () indicates the topology stream is running. Topology data will be pushed according to the configured Collection Schedule interval.

Viewing data in BMC Helix applications

Important

If the event or metric data is ingested by using BMC Helix Intelligent Integrations, and the topology data is ingested through some other means, all the use cases in BMC Helix AIOps might not work as expected because the external IDs generated by BMC Helix Intelligent Integrations and BMC Helix Discovery differ. In addition, host name might differ in both the products. 

To view events in BMC Helix Operations Management

  1. In BMC Helix Operations Management, select Monitoring > Events.
  2. Filter the events by the VropsAlert class.

Incoming events from VMware vROps  are processed in BMC Helix Operations Management through a set of deduplication rules to determine whether the incoming event is a duplicate event or a new event. For more information, see Event deduplication, suppression, and closure for reducing event noise.

For information about events, see Monitoring and managing events. Open link .

To view metrics in BMC Helix Operations Management

  1. In BMC Helix Operations Management, select Monitoring > Devices.
  2. Click the links for the required device.
  3. On the Monitors tab, click the required monitor.
    The Performance Overview tab shows the metrics graph . For information about metrics, see Viewing collected data Open link

To view the topology data in BMC Helix Discovery

In BMC Helix Discovery, select Explore > Data, and click <count> Import Records in the Miscellaneous section. The Import Record List page shows the CI records received from VMware vROps . For information about records, see Managing your IT infrastructure Open link .

To view services and situations in BMC Helix AIOps

Before you view services and situations in BMC Helix AIOps, create a Business Service model in BMC Helix Discovery. For information about creating models, see Managing models. Open link   

In BMC Helix AIOps, on the Overview page, view the services and situations for the event and topology data received from VMware vROps .

Mapping between VMware vROps and BMC Helix Operations Management

The following table shows the mapping between VMware vROps and BMC Helix Operations Management:

Event attributeVMware vROps Status/ StateBMC Helix Operations Management
Status/ state

ACTIVE/ OPEN

Open

ACTIVE/ ASSIGNED

Assigned

ACTIVE/ SUSPENDED

Acknowledged

ACTIVE/ SUPPRESSED

Closed

ACTIVE/ Any state except listed above

Open

UPDATED, NEW/ Any state 

Open

CANCELLED/ Any state

Closed
Severity

Critical

Critical

Immediate

Major

Warning

Warning

Info

Information

None, Auto

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

Comments