Integrating with Cloud Foundry

VMware Tanzu Application Service for VMs Cloud Foundry is an opinionated application platform designed to bring efficiency, security, and speed to custom development organizations. Cloud Foundry makes it faster and easier to build, test, deploy, and scale applications, providing a choice of the underlying infrastructure, developer frameworks, and application services.

Configure an integration with Cloud Foundry to view topology data from Cloud Foundry in the following products and derive actionable insights: 

  • Topology in BMC Helix Discovery
  • Services in BMC Helix AIOps

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.

Plan for the connection

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

To integrate with Cloud Foundry

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

  2. Click the Cloud Foundry tile.
  3. Specify the following source connection details:
    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, 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.
  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 the topology data type and specify the configuration parameters in the Collectors section as described in the following table:

    Parameter name and description

    Collection Schedule

    Specify the data collection frequency, in minutes. 

    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.

    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. 

    Default: 60 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.

    Data Latency

    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.

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

          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 topology data stream for the integration you created is running. Data streaming is indicated by moving colored arrows.

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

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

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

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

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

Comments