Integrating with AppDynamics

The BMC Helix Intelligent Integrations AppDynamics connector collects events, metrics, and topology data from AppDynamics APM, DB and EUM.

You can view the collected data in various BMC Helix applications and derive actionable insights:

• BMC Helix Operations Management
  BMC Helix Operations Management displays health rule violations as events, even though AppDynamics separates events and health rule violations. 
• BMC Helix Discovery
• BMC Helix AIOps

As a tenant administrator, perform the following steps to configure a connection with AppDynamics, verify the connection, and view the collected event, metric, and topology data in various BMC Helix applications.

Plan for the connection

Review the following prerequisites to help you plan and configure a connection with AppDynamics:

• Choose the BMC Helix Intelligent Integrations deployment mode and review the corresponding port requirements. For information about various deployment modes and port requirements, see Deployment scenarios.
• Based on the deployment mode, either use BMC Helix Intelligent Integrations or deploy the BMC Helix Intelligent Integrations on-premises gateway. For more information, see Deploying the BMC Helix Intelligent Integrations on-premises gateway.

• The user account with which you plan to connect to AppDynamics has the following roles assigned:

  • Applications & Dashboards Viewer

  • Dashboards Viewer

  • DB Monitoring User

  • Server Monitoring user

  • Universal Agent User

  • Workflow Executor

To configure a connection with AppDynamics

1. In BMC Helix Intelligent Integrations, on the CONNECTORS  tab, click in the SOURCES panel.

2. Click AppDynamics APM, DB & EUM.
3. Specify the following details for the source connection:

   1. Specify a unique instance name.

      Important

      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 AppDynamics_Host_PROD, AppDynamics_Host_TEST, and so on.

   2. Specify the AppDynamics 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 AppDynamics 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 AppDynamics 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 (default value is 5).
   5. Specify the AppDynamics account name.
   6. Specify the user name and password. Ensure that the specified user has the roles assigned specified in the Before you begin section.
   7. 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).
4. Click VALIDATE AND CREATE.
   The specified connection details are validated and the corresponding source connection is created in the Source Connection list.

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

6. Ensure that the options for the datatypes for which you want to collect data are selected.

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

   Parameter Name	Data Type
   	AppDynamics Events (REST Pull)	AppDynamics Health Rule Violations (REST Pull)	AppDynamics Managed Metrics (REST Pull)	AppDynamics Topology (REST Pull)
   Collection Schedule Specify the data collection frequency (in minutes). Default: 5 minutes (events, health rule violations, metrics), 60 minutes (topology)  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. For more information about how this parameter affects data collection, see Data collection schedule.
   Data Collection Window Specify the historical time period (in minutes) from the current time for which the data should be collected from AppDynamics.  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.
   Applications Select All or a subset of application tags from the list. This list is updated automatically from AppDynamics  .
   Paths Select All or a subset of paths from the list. This list is updated automatically from AppDynamics  .
   Severity Select All or a subset of severities from the list.
   Severities Select All or a subset of severities from the list.
   Event Type Select one or more event types from the list.
   HRV Types Select All or a subset of health rule violations from the list. This list is updated automatically from AppDynamics .
   Affected Collection Types Select All or a subset of affected collection types from the list. This list is updated automatically from AppDynamics .
   Servers Select All or a subset of servers from the list.
   HRV Duplicate Window Specify the historical period from the current time for which data for the duplicate health rule violations should not be collected. If you set it to 0, data for the duplicate health rule violations is also collected.

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

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

   Parameter name and description
   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. Default: 250
   Max Batching Delay Specify the maximum time (in seconds) to wait before building a batch and processing. Default: 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. Default: 2 seconds Example: Base Retry Delay is set to 2 seconds. Retry is performed after 2, 4, 8, 16, ... seconds.
   Max Intra-Retry Delay Specify the maximum limit for the base retry delay.  Default: 60 seconds Example: Max Intra-Retry Delay is set to 60 seconds. Base Retry Delay is set to 2 seconds. Retries are performed 2, 4, 8, 16, 32, 64,... seconds later again.
   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.  Default: 5 minutes Example: Max Retry Duration is set to 8 hours. Base Retry Delay is set 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 be completed.

   
   
10. Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data types.
11. 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 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 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 that the topology stream is running. Topology data will be pushed according to the configured Collection Schedule interval.

To view events in BMC Helix Operations Management

1. In BMC Helix Operations Management, select Monitoring > Events.
2. Filter the events by the AppDynamicEvent (for AppDynamics events) or AppDynamicHRVEvent (for AppDynamics Health Rule Violations) classes.

Incoming events from AppDynamics 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 and suppression for reducing event noise.

For more information about events, see Monitoring and managing events

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 .

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

For information about records, see Managing your IT infrastructure .

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 .  

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

For information about Services, see Monitoring services. For information about Situations, see Monitoring situations.