Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

IBM Bluemix Platform

 

The JSA DSM for the IBM Bluemix Platform collects events logs from your Bluemix Platform.

The following table identifies the specifications for the Bluemix Platform DSM:

Table 1: Bluemix Platform DSM Specifications

Specification

Value

Manufacturer

IBM

DSM name

Bluemix Platform

RPM file name

DSM-IBMBluemixPlatform-7.x-xxxxxxx.noarch.rpm

Supported versions

N/A

Protocol

Syslog, TLS Syslog

Recorded event types

All System (Cloud Foundry) events, some application events

Automatically discovered?

Yes

Includes identity?

No

Includes custom properties?

No

More information

IBM website for Bluemix (IBM website for Bluemix)

To integrate Bluemix Platform with JSA, complete the following steps:

You must perform the installation, third-party configuration, and JSA configuration procedures in the order. Installation must always be first, but you can invert the order of the other two procedures, In some cases, no action is required for the third-party configuration and you can omit the procedure.

  1. If automatic updates are not enabled, download and install the most recent version of the Bluemix Platform DSM RPM on your JSA console:

  2. Configure your Bluemix Platform device to send syslog events to JSA.

  3. If JSA does not automatically detect the log source, add a Bluemix Platform log source on the JSA Console.

Configuring Bluemix Platform to Communicate with JSA

To collect Bluemix Platform events, you must configure your third-party instance to send events to JSA.

You must have an app running in Bluemix so that you can create log drains.

  1. From the Cloud Foundry command-line interface, type the following command to create a drain:

    Alteratively, use the following command:

    1513 is the port that is used to communicate with JSA.

  2. Bind the service instance with the following command:

Integrating Bluemix Platform with JSA

In most installations, there is only the RPM. For installations where there are multiple RPMs required, (for example a PROTOCOL RPM and a DSMCommon RPM), ensure that the installation sequence reflects RPM dependency.

  1. If required, download and install the latest TLS Syslog RPM on your JSA console. You can install a protocol by using the procedure to manually install a DSM. If automatic updates are configured to install protocol updates, this procedure is not necessary.
  2. Download and install the latest DSMCommon RPM on your JSA console. If automatic updates are configured to install DSM updates, this procedure is not necessary.
  3. Download and install the latest Bluemix Platform RPM on your JSA console. If automatic updates are configured to install DSM updates, this procedure is not necessary.

You must configure a Bluemix log source in JSA by using Syslog or Syslog TLS.

Configuring a Bluemix Log Source to Use Syslog

You can configure a Bluemix log source in JSA.

  1. Log in to JSA to use Syslog.
  2. On the Admin tab, click Data Sources >Log Sources >Add.
  3. From the Log Source Type list, select Bluemix Platform.
  4. From the Protocol Configuration list, select Syslog.
  5. In the Log Source Identifier field, enter the IP address of the Bluemix Loggregator.Note

    It might be necessary to include the IP address and the port, as the Log Source Identifier. For example, 1.1.1.1:1234.

  6. Configure the remaining fields in the Log Sources window as required and click Save.
  7. On the Admin tab toolbar, click Deploy Changes.

Configuring a Bluemix Log Source with TLS Syslog

You can configure a Bluemix log source in JSA to use TLS Syslog.

  1. Log in to JSA.
  2. On the Admin tab, click Data Sources >Log Sources >Add.
  3. From the Log Source Type list, select Bluemix Platform.
  4. From the Protocol Configuration list, select TLS Syslog.
  5. In the Log Source Identifier field, enter the IP address of the Bluemix Loggregator.
  6. In the TLS Listen Port field, enter a port number.
  7. From the Authentication Mode list, select TLS .
  8. From the Certificate Type list, select Provide Certificate.
  9. In the Provided Server Certificate Path field, enter the absolute path to the server certificate, for example:

    syslog-tls.cert

  10. In the Provided Private Key Path field, enter the absolute path the private key.

    The private key must be a DER-encoded PKCS8 key.

  11. Configure the remaining fields in the Log Sources window as required and click Save.
  12. On the Admin tab toolbar, click Deploy Changes.

Related Documentation