Integrating with Aternity

Riverbed Aternity provides a Digital Experience Management (DEM) platform that contextualizes data across every enterprise endpoint, application, and transaction to inform remediation, drive down costs, and improve productivity. 

After you configure an integration with Aternity, you can get the alert, metric, and topology data from Aternity in BMC Helix Operations Management and BMC Helix Discovery respectively, and process the data further in BMC Helix AIOps to derive actionable insightsAlthough Aternity separates alerts and events, you can see alerts as events in BMC Helix Operations Management

For example, the following figure shows the alerts received as events in BMC Helix Operations Management:



As a tenant administrator, perform the following steps to integrate with Aternity.

Before you begin

  1. Obtain the egress IP of your tenant by requesting BMC Support.
  2. Create a firewall rule to allow traffic from the egress IP to the Aternity host on the listening port. The default port is 443.

To integrate with Aternity

  1. Log on to BMC Helix Portal, and click Launch on BMC Helix Intelligent Integrations.

  2. On the CONNECTORS tab, click in the SOURCES panel.
  3. Click Riverbed Aternity.
  4. Specify the source connection details:
    1. Instance Name: Specify a unique instance name.

      Recommendation

      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 Aternity_Host_PROD, Aternity_Host_TEST, and so on.

    2. Host and Port: Specify the Aternity host name and port number. The default host is lms-odata.aternity.com, and the default port number is 443.
    3. HTTPS: Ensure that this check box is selected to indicate that you plan to use an https connection to the  Aternity host.

      Caution

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


    4. Max Connections: Specify the number of maximum concurrent REST API requests that should be executed during a data collection schedule. The default value is 5.

    5. User Name and Password: Specify the user name and password. Ensure that the specified user can access the Aternity REST API.
    6. Proxy: Click Proxy, and specify the following details:
      1. Uses Proxy: Select this check box if you plan to configure a proxy server.
      2. Proxy Host and Proxy Port: Specify the host name and port number of the proxy server. The default port number is 8888.
  5. Click VALIDATE AND CREATE.
    The specified connection details are validated and the source connection is created in the Source Connection list.
  6. Select the source connection that you created from the Source Connection 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. Clear the options for one or more data types for which you don't want to collect data. By default, all the options are selected.
    • Aternity Alerts
    • Aternity Metrics
    • Aternity Topology
  8. Configure the collectors for the selected data types by clicking the respective data type in the Collectors section. Specify the parameters for the selected data type, as explained in the following table:

    Parameter NameData Type
    Aternity AlertsAternity MetricsAternity Topology

    Collection Schedule
    Specify the data collection frequency in minutes.

    Applicable

    BMC recommendation: 5 minutes

    Applicable

    BMC recommendation: 5 minutes

    Applicable

    BMC recommendation: 60 minutes

    Data Collection Window

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

    Applicable

    BMC recommendation: 5 minutes

    Applicable

    BMC recommendation: 5 minutes

    Applicable

    BMC recommendation: 60 minutes

    Data Latency

    Specify the time (in minutes) for which the data time window should be placed far back on the timeline.

    ApplicableApplicableApplicable

    Devices

    Select All or a subset of devices from the list.

    This list of devices is updated automatically from Aternity

    Not Applicable

    Applicable

    Low Disk Space
    Low Memory Pagefaults
    Low Virtual Memory
    Memory Allocation Failure / Nonpaged
    Memory Allocation Failure / Paged
    Network Interface Long Queue
    Network Interface Saturation
    Overheat Related Shutdown
    Printing Error / Bad Security Descriptor
    Printing Error / Init Failed
    Printing Error / No Driver Found
    Printing Error / Package Regeneration Failed
    Printing Error / Port Init Error
    Printing Error / Print Failed
    Printing Error / Spooler Creation Failed
    Printing Error / Spooler Out of Resources
    Printing Error / Spooler Shutdown
    System Crash
    Unexpected Shutdown
    WiFi Disconnect
    Windows Update Failure

    Battery Wear
    Corrupted FS
    Faulty HD S.M.A.R.T status
    HD Bad Blocks
    HD Failure

    Not Applicable

    Applications

    Select all or a subset of applications from the list.

    This list of applications is updated automatically from Aternity. 

    Applicable

    ApplicableNot applicable

  9. Configure the distributors for the selected data types by clicking the respective data type in the Distributors section. Specify the parameters for the selected data type, as explained in the following table:

    Parameter NameDefault

    Max Batching Size

    Specify the maximum number of records to send in a single POST 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 to wait before building a batch and processing.

    3 seconds

    Base Retry Delay

    Specify the initial delay time (that means, for 2 seconds, the retries would proceed 2, 4, 8, 16, ... seconds later.)

    2 seconds

    Max Intra-Retry Delay

    Specify the hard limit for the above retry delay. For example, if set to 60 seconds, retries would be performed again 2, 4, 8, 16, 32, 32, 32... seconds later.

    60 seconds

    Max Retry Duration

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

    For example, if set to 8 hours, then requests would be made based on the above settings for 2+4+8+16+32+32+32... until 8 hours in total duration is reached, then no subsequent attempts are made to retry sending the data.

    The assumption here is that if there is an outage or other issue with the destination tool, then recovery will take less than "Max Retry Duration" to complete.

    5 minutes

  10. Click CREATE COLLECTORS to create the required collector streams for the selected data types.
  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 if you want to edit the integration details before creating the instance. After you save the stream, the instance 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 if you want to save the integration details and start receiving the data immediately.

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


To validate the integration

Perform the following actions to validate the integration:

  • Data streams: Ensure that the status of the data streams is up and running, indicated by moving blue and red arrows:


    • A moving dark blue arrow () indicates that event data is being streamed. 
    • A moving red arrow () indicates that metric data is being streamed. 
    • A moving light blue arrow () indicates that topology data is being streamed. 

  • Events: From BMC Helix Operations Management, go to Monitoring > Events to ensure that you can see the events in BMC Helix Operations Management.
    For more information, see  Event monitoring Open link .
  • Metrics: From BMC Helix Operations Management, go to Monitoring > Devices and perform the following steps to ensure that you can see the metrics in BMC Helix Operations Management:
    1. Click the links for the required device.
    2. On the Monitors tab, click the required monitor.
      You should see the metrics graph on the Performance Overview tab.
      For more information, see Viewing collected data Open link
  • Topology: From BMC Helix Discovery, go to Explore > Data, and then click <count> Import Records in the Miscellaneous section to ensure that you can see the CI records from the source (host) in BMC Helix Discovery. Use these records further to create a Business Service model for the source. For more information, see Creating a model Open link .

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

Comments