Integrating with VMware Tanzu Application Service for VMs Cloud Foundry

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

Supported versions

This connector supports the following versions of Cloud Foundry for data collection:

• 2.10
• 2.13

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

In the preceding list, third-party product refers to Cloud Foundry . 

Configuring the connection with Cloud Foundry

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 Cloud Foundry .
4. Specify the following source connection details:

   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, CF_Host_PROD, CF_Host_TEST, and so on.

      
      

   2. Specify the Cloud Foundry  host name and port number (default value is 443).
   3. Specify the user name and password. Ensure that the specified user can access the Cloud Foundry  REST API.

   4. Select the HTTPS check box if you plan to use an https connection to the Cloud Foundry host.

      Caution

      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 Dynatrace  documentation to learn how to install SSL certificates.

   5. Specify the number of maximum concurrent REST API requests that should be executed during a collection schedule (d efault value is 5).
   6. Specify the Client ID.
   7. Specify the Client password.
   8. Specify a valid API key. For more information, see the Cloud Foundry documentation.
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 when you create a connection for a source. 

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

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
   

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

   Parameter name	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 secondsExample: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 secondsExample: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,... seconds later.
   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 minutesExample: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.
   Attributes To Be Dropped When Updating Events	Specify the event attributes that you do not want to be updated in BMC Helix Operations Managementwhen events are updated. For example, if you do not want an event's severity, source address, source category, and subcategory to be updated in BMC Helix Operations Management , you need to specify those attributes in a comma-separated format: severity,source_address,source_category,source_subcategory .Important:You can obtain the event attribute names in BMC Helix Operations Management, by exporting any event data in JSON, BAROC, XML, or CSV format . The exported file contains all attributes of the event data, and from there you can identify the attributes to be dropped.

10. Click CREATE DISTRIBUTORS to create the required distributor streams for the topology data type.

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 topology data stream.
    • SAVE AND START STREAM : Click this button if you want to save the integration details and start receiving topology data immediately.

    ImportantFor 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 integration

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

A moving light blue arrow () indicates that the topology stream is running. Topology data will be pushed according to the configured Collection Schedule interval.

Viewing data in BMC Helix applications

To view topology 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 Cloud Foundry . For information about records, see Managing your IT infrastructure .

To view services in BMC Helix AIOps

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

In BMC Helix AIOps, on the Overview page to view the services for the topology data received from Cloud Foundry  . For more information about services, see Monitoring key performance indicators and entities.