Streaming app logs to third-party services

Here are instructions for configuring some third-party log management services for your Cloud Foundry apps.

Once you have configured a service, refer to the Third-Party Log Management Services topic for instructions on binding your app to the service.

Logit.io

From your Logit.io dashboard:

1. Identify the Logit ELK stack you want to use.

2. Click Logstash Configuration.

3. Note your Logstash Endpoint.

4. Note your TCP-SSL, TCP, or UDP Port (not the syslog port).

5. Create the log drain service in Cloud Foundry.

   $ cf cups logit-ssl-drain -l syslog-tls://ENDPOINT:PORT
   

   or

   $ cf cups logit-drain -l syslog://ENDPOINT:PORT
   

6. Bind the service to an app.

   $ cf bind-service YOUR-CF-APP-NAME logit-ssl-drain
   

   or

   $ cf bind-service YOUR-CF-APP-NAME logit-drain
   

7. Restage or push the app using one of the following commands:

   $ cf restage YOUR-CF-APP-NAME

   $ cf push YOUR-CF-APP-NAME

   After a short delay, logs begin to appear in Kibana.

Papertrail

From your Papertrail account:

1. Click Add System. The Dashboard appears.

2. Click the Other link. The Setup Systems screen appears.

3. Select I use Cloud Foundry, enter a name, and click Save.

   

4. Record the URL with port that is displayed after creating the system.

   

5. Create the log drain service in Cloud Foundry.

   $ cf cups my-logs -l syslog-tls://logs.papertrailapp.com:PORT
   

6. Bind the service to an app.

   $ cf bind-service APPLICATION-NAME my-logs
   

7. Restage the app.

   $ cf restage APPLICATION-NAME
   

   After a short delay, logs begin to flow.

8. When Papertrail starts receiving log entries, the view changes to show the logs viewing page.

   

Splunk

See Streaming App Logs to Splunk for details.

Splunk Storm

From your Splunk Storm account:

1. Click Add project.

   

2. Enter the project details.

   

3. Create a new input for Network data.

   

4. Manually enter the external IP addresses your Cloud Foundry administrator assigns to outbound traffic.

   

5. Note the host and port provided for TCP input.

   

6. Using the cf CLI, create the log drain service in Cloud Foundry using the TCP host and port you recorded. Then you bind the service to an app and restage the app using the syntax shown here. After a short delay, the logs begin to flow.

   $ cf cups my-logs -l syslog://HOST:PORT
   $ cf bind-service APPLICATION-NAME my-logs
   $ cf restage APPLICATION-NAME
   

7. When events begin to appear, click Data Summary. The Data Summary button appears in the What to Search section.

   

8. In the Data Summary table, click the loggregator link to view all incoming log entries from Cloud Foundry.

   

SumoLogic

SumoLogic uses HTTPS for communication. HTTPS is supported in Cloud Foundry v158 and later.

From your SumoLogic account:

1. Beside Manage Collectors and Sources, click the Add Collector link.

   

2. Under Add Collector, select Hosted Collector and fill in the details.

   1. In Name, enter Cloud Foundry.
   2. In Description, enter the purpose of the new collector.
   3. In Category, you can enter the source category, if you want. The collector sets the source category to this value unless it is overwritten by the source metadata.

   

   

3. In the Manage Collectors and Sources table, in the row for the new collector, click the Add Source link.

   

4. Under Select a type of Source, select HTTP and fill in the details. An HTTPS URL is provided.

   1. In Name, leave CloudFoundry.
   2. In Description, enter a description of the source.
   3. In Source Host, enter the host name for the system from which the log files are being collected.
   4. In Source Category, enter the log category metadata. You can use this later in queries.

   

5. When the source has been created, a URL is displayed. You can also view the URL by clicking the Show URL link beside the newly created source in the Manage Collectors and Sources table. Record the URL for the next step.

   

6. Using the cf CLI, create the log drain service in Cloud Foundry using the source URL you just recorded. Then you bind the service to an app and restage the app using the syntax shown here. After a short delay, the logs will begin to flow.

   $ cf cups my-logs -l HTTPS-SOURCE-URL
   $ cf bind-service APPLICATION-NAME my-logs
   $ cf restage APPLICATION-NAME
   

7. In the SumoLogic dashboard, click Manage, then click Status to see a view of the log messages received.

   

8. Click Search. Place the cursor in the search box, then press Enter to submit an empty search query.

   

Logsene

Logsene uses HTTPS for communication. HTTPS is supported in Cloud Foundry v158 and later.

From your Sematext account:

1. Click the Create App / Logsene App menu item. Enter a name and click Add Application to create the Logsene App.

2. Using the cf CLI, create the log drain service in Cloud Foundry using the source URL displayed. Then you bind the service to an app and restage the app using the commands shown here. After a short delay, the logs begin to flow. The logs appear in the Logsene UI.

   $ cf cups logsene-log-drain -l https://logsene-cf-receiver.sematext.com/YOUR_LOGSENE_TOKEN
   $ cf restage APPLICATION-NAME
   $ cf bind-service YOUR-CF-APP-NAME logsene-log-drain
   

Logentries is not supported

Using Logentries is not recommended because it does not support multiple syslog sources. Cloud Foundry distributes log messages over multiple servers to handle the load.