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.

Editing and deleting integrations

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

BMC Helix Operations Management
BMC Helix Operations Managementdisplays alerts as events, even though Aternity separates events and alerts.
BMC Helix Discovery
BMC Helix AIOps

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

Before you begin

Have the egress IP of your tenant. Request the egress IP from BMC Software if you don't already have it.
Ensure that you have a firewall rule to allow traffic from the egress IP to the Aternity host on the listening port (default value is 443).

To integrate with Aternity

In BMC Helix Intelligent Integrations, on the CONNECTORS tab, click in the SOURCES panel .
Click Riverbed Aternity .
Specify the following details for the source connection:
1. 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. Specify the Aternity host name (default is lms-odata.aternity.com) and port number (default is 443).
3. Ensure that the HTTPS check box is selected to indicate that you plan to use an https connection to the Aternity host.
  Warning
  
  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. Specify the number of maximum concurrent REST API requests that should be executed during a data collection schedule (d efault value is 5).
5. Specify the user name and password. Ensure that the specified user can access the Aternity REST API.
6. Click Proxy and specify whether you want to configure a proxy server.
  If yes, specify the host name and port number (default value is 8888).
Click VALIDATE AND CREATE.
The specified connection details are validated and the source connection is created in the Source Connection list.
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.
Clear the options for which you don't want to collect data.

Click a data type and specify the configuration parameters in the Collectors section as described in the following table:

Parameter Name	Data Type
Parameter Name	Aternity Alerts	Aternity Metrics	Aternity Topology
Collection Schedule Specify the data collection frequency (in minutes). For example, if you set this parameter to 5 mins, the collector runs every 5 mins. For more information about this parameter, see Data collection schedule.	Applicable BMC recommendation: 5 minutes	Applicable BMC recommendation: 5 minutes	Applicable BMC recommendation: 60 minutes
Data Collection Window Data Collection Window Specify the historical time period (in minutes) from the current time for which the data should be collected from Aternity. For example, if you set Collection Schedule parameter to 5 mins (considering 00:32 as the current time) and the Data Collection Window parameter to 5 mins, data is extracted from 00:27 to 00:32. For more information about this parameter, see Data collection window.	Applicable BMC recommendation: 5 minutes	Applicable BMC recommendation: 5 minutes	Applicable BMC recommendation: 60 minutes
Data Latency Specify the time (in minutes) by which the data time window should be shifted far back on the timeline. This parameter is useful in slow, late data availability situations. For example, if you set the Collection Schedule parameter to 5 mins, the Data Collection Window parameter to 5 mins, and the Data Latency parameter to 2 mins, data is extracted from 00:23 to 00:28, when run from just after 00:30. For more information about this parameter, see Data latency.	Applicable	Applicable	Applicable
Devices Select All or a subset of devices from the list. This list of devices is updated automatically from Aternity .	Not Applicable	Applicable	Not Applicable
Applications Select All or a subset of applications from the list. This list of applications is updated automatically from Aternity .	Applicable	Applicable	Not applicable

Click CREATE COLLECTORS to create the required collector streams for the selected data types.

Click a data type and specify the configuration parameters in the Distributors section as described in the following table:

Parameter Name	Default
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: n¹, n², n³, 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

Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data types.
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 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 this button if you want to save the integration details and start receiving data immediately.

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

To verify the integration

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 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.

To view events in BMC Helix Operations Management

In BMC Helix Operations Management, select Monitoring > Events to view the events received from Aternity .

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

To view metrics in BMC Helix Operations Management

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

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 Aternity. 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 Creating a model Open link .

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