<commit_before>---
title: Service-Specific Instructions for Streaming Application Logs
owner: PCF Metrics
---

<strong><%= modified_date %></strong>

This topic provides instructions for configuring some third-party log management
services.

Once you have configured a service, refer to the [Third-Party Log Management Services](./log-management.html) topic for instructions on binding your application to the service.

## <a id='papertrail'></a>Papertrail ##

From your Papertrail account:

1. Click **Add System**.

    <%= image_tag("../images/third-party-logs/papertrail-02.png") %>

1. Click the **Other** link.

    <%= image_tag("../images/third-party-logs/papertrail-03.png") %>

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

    <%= image_tag("../images/third-party-logs/papertrail-04.png") %>

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

    <%= image_tag("../images/third-party-logs/papertrail-05.png") %>

1. Create the log drain service in Cloud Foundry.

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

1. Bind the service to an app. Restage or push the app using either the `cf restage APPLICATION-NAME` or `cf push APPLICATION-NAME` command. After a short delay, logs begin to flow automatically.

1. Once Papertrail starts receiving log entries, the view automatically updates
to the logs viewing page.

    <%= image_tag("../images/third-party-logs/papertrail-11.png") %>

## <a id='splunk'></a>Splunk ##

See [Streaming Application Logs to Splunk](integrate-splunk.html) for details.

## <a id='splunkstorm'></a>Splunk Storm ##

From your Splunk Storm account:

1. Click **Add project**.

    <%= image_tag("../images/third-party-logs/splunkstorm-02.png") %>

1. Enter the project details.

    <%= image_tag("../images/third-party-logs/splunkstorm-03.png") %>

1. Create a new **input** for **Network data**.

    <%= image_tag("../images/third-party-logs/splunkstorm-04.png") %>

1. Manually enter the external IP addresses your Cloud Foundry administrator
assigns to outbound traffic.
If you are using Pivotal Web Services, refer to the [Externally Visible IP Addresses](http://docs.run.pivotal.io/marketplace/external-ips.html) topic.

    <%= image_tag("../images/third-party-logs/splunkstorm-05.png") %>

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

    <%= image_tag("../images/third-party-logs/splunkstorm-06.png") %>

1. Create the log drain service in Cloud Foundry using the displayed TCP host and port.

    `$ cf cups my-logs -l syslog://HOST:PORT`

1. Bind the service to an app. Restage or push the app using either the `cf restage APPLICATION-NAME` or `cf push APPLICATION-NAME` command. After a short delay, logs begin to flow automatically.

1. Wait for some events to appear, then click **Data Summary**.

    <%= image_tag("../images/third-party-logs/splunkstorm-09.png") %>

1. Click the **loggregator** link to view all incoming log entries from Cloud Foundry.

    <%= image_tag("../images/third-party-logs/splunkstorm-10.png") %>

## <a id='sumologic'></a>SumoLogic ##

<p class="note"><strong>Note</strong>: SumoLogic uses HTTPS for communication.  HTTPS is supported in Cloud Foundry v158 and above.</p>

From your SumoLogic account:

1. Click the **Add Collector** link.

    <%= image_tag("../images/third-party-logs/sumologic-02.png") %>

1. Choose **Hosted Collector** and fill in the details.

    <%= image_tag("../images/third-party-logs/sumologic-03a.png") %>

    <%= image_tag("../images/third-party-logs/sumologic-03b.png") %>

1. In the new collector's row of the collectors view, click the **Add Source**
link.

    <%= image_tag("../images/third-party-logs/sumologic-04.png") %>

1. Select **HTTP** source and fill in the details.

    <%= image_tag("../images/third-party-logs/sumologic-05.png") %>

1. Once the source is created, a URL should be displayed.
You can also view the URL by clicking the **Show URL** link beside the created
source.

    <%= image_tag("../images/third-party-logs/sumologic-06a.png") %>

1. Create the log drain service in Cloud Foundry using the displayed URL.

    `$ cf cups my-logs -l HTTP-SOURCE-URL`

1. Bind the service to an app. Restage or push the app using either the `cf restage APPLICATION-NAME` or `cf push APPLICATION-NAME` command. After a short delay, logs begin to flow automatically.

1. In the SumoLogic dashboard, click **Manage**, then click **Status** to see a
view of log messages received over time.

    <%= image_tag("../images/third-party-logs/sumologic-09.png") %>

1. In the SumoLogic dashboard, click on **Search**.
Place the cursor in the search box, then press **Enter** to submit an empty
search query.

    <%= image_tag("../images/third-party-logs/sumologic-10.png") %>

## <a id='logentries'></a>Logentries is Not Supported ##

Cloud Foundry distributes log messages over multiple servers in order to handle
load. Currently, we do not recommend using Logentries as it does not support multiple syslog sources.

## <a id='logsene'></a>Sematext Logsene ##

<p class="note"><strong>Note</strong>: Logsene uses HTTPS for communication. HTTPS is supported in Cloud Foundry v158 and above.</p>

From your Sematext account:

1. Click the [Create App / Logsene App](https://apps.sematext.com/logsene-reports/registerApplication.do) menu item. Enter a name and click to the "Add Application" button to create the Logsene App. Logsene displays the instructions to create the log drain service in the section "Cloud Foundry". The command includes the URL with the given Logsene App-Token. 

1. Create the log drain service in Cloud Foundry using the displayed URL.

    `$ cf cups logsene-log-drain -l https://logsene-cf-receiver.sematext.com/YOUR_LOGSENE_TOKEN`

1. Bind the log drain to an app. You could optionally bind multiple apps to one log drain.
	`$cf bind-service YOUR-CF-APP-NAME logsene-log-drain`

1. Restage or push the app using either the `cf restage YOUR-CF-APP-NAME` or `cf push YOUR-CF-APP-NAME` command. After a short delay, logs begin to flow automatically and appear in the [Logsene UI](https://apps.sematext.com/users-web/services.do#logsene).

<commit_msg>removed comment about instructions displayed in Logsene<commit_after>---
title: Service-Specific Instructions for Streaming Application Logs
owner: PCF Metrics
---

<strong><%= modified_date %></strong>

This topic provides instructions for configuring some third-party log management
services.

Once you have configured a service, refer to the [Third-Party Log Management Services](./log-management.html) topic for instructions on binding your application to the service.

## <a id='papertrail'></a>Papertrail ##

From your Papertrail account:

1. Click **Add System**.

    <%= image_tag("../images/third-party-logs/papertrail-02.png") %>

1. Click the **Other** link.

    <%= image_tag("../images/third-party-logs/papertrail-03.png") %>

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

    <%= image_tag("../images/third-party-logs/papertrail-04.png") %>

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

    <%= image_tag("../images/third-party-logs/papertrail-05.png") %>

1. Create the log drain service in Cloud Foundry.

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

1. Bind the service to an app. Restage or push the app using either the `cf restage APPLICATION-NAME` or `cf push APPLICATION-NAME` command. After a short delay, logs begin to flow automatically.

1. Once Papertrail starts receiving log entries, the view automatically updates
to the logs viewing page.

    <%= image_tag("../images/third-party-logs/papertrail-11.png") %>

## <a id='splunk'></a>Splunk ##

See [Streaming Application Logs to Splunk](integrate-splunk.html) for details.

## <a id='splunkstorm'></a>Splunk Storm ##

From your Splunk Storm account:

1. Click **Add project**.

    <%= image_tag("../images/third-party-logs/splunkstorm-02.png") %>

1. Enter the project details.

    <%= image_tag("../images/third-party-logs/splunkstorm-03.png") %>

1. Create a new **input** for **Network data**.

    <%= image_tag("../images/third-party-logs/splunkstorm-04.png") %>

1. Manually enter the external IP addresses your Cloud Foundry administrator
assigns to outbound traffic.
If you are using Pivotal Web Services, refer to the [Externally Visible IP Addresses](http://docs.run.pivotal.io/marketplace/external-ips.html) topic.

    <%= image_tag("../images/third-party-logs/splunkstorm-05.png") %>

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

    <%= image_tag("../images/third-party-logs/splunkstorm-06.png") %>

1. Create the log drain service in Cloud Foundry using the displayed TCP host and port.

    `$ cf cups my-logs -l syslog://HOST:PORT`

1. Bind the service to an app. Restage or push the app using either the `cf restage APPLICATION-NAME` or `cf push APPLICATION-NAME` command. After a short delay, logs begin to flow automatically.

1. Wait for some events to appear, then click **Data Summary**.

    <%= image_tag("../images/third-party-logs/splunkstorm-09.png") %>

1. Click the **loggregator** link to view all incoming log entries from Cloud Foundry.

    <%= image_tag("../images/third-party-logs/splunkstorm-10.png") %>

## <a id='sumologic'></a>SumoLogic ##

<p class="note"><strong>Note</strong>: SumoLogic uses HTTPS for communication.  HTTPS is supported in Cloud Foundry v158 and above.</p>

From your SumoLogic account:

1. Click the **Add Collector** link.

    <%= image_tag("../images/third-party-logs/sumologic-02.png") %>

1. Choose **Hosted Collector** and fill in the details.

    <%= image_tag("../images/third-party-logs/sumologic-03a.png") %>

    <%= image_tag("../images/third-party-logs/sumologic-03b.png") %>

1. In the new collector's row of the collectors view, click the **Add Source**
link.

    <%= image_tag("../images/third-party-logs/sumologic-04.png") %>

1. Select **HTTP** source and fill in the details.

    <%= image_tag("../images/third-party-logs/sumologic-05.png") %>

1. Once the source is created, a URL should be displayed.
You can also view the URL by clicking the **Show URL** link beside the created
source.

    <%= image_tag("../images/third-party-logs/sumologic-06a.png") %>

1. Create the log drain service in Cloud Foundry using the displayed URL.

    `$ cf cups my-logs -l HTTP-SOURCE-URL`

1. Bind the service to an app. Restage or push the app using either the `cf restage APPLICATION-NAME` or `cf push APPLICATION-NAME` command. After a short delay, logs begin to flow automatically.

1. In the SumoLogic dashboard, click **Manage**, then click **Status** to see a
view of log messages received over time.

    <%= image_tag("../images/third-party-logs/sumologic-09.png") %>

1. In the SumoLogic dashboard, click on **Search**.
Place the cursor in the search box, then press **Enter** to submit an empty
search query.

    <%= image_tag("../images/third-party-logs/sumologic-10.png") %>

## <a id='logentries'></a>Logentries is Not Supported ##

Cloud Foundry distributes log messages over multiple servers in order to handle
load. Currently, we do not recommend using Logentries as it does not support multiple syslog sources.

## <a id='logsene'></a>Logsene ##

<p class="note"><strong>Note</strong>: Logsene uses HTTPS for communication. HTTPS is supported in Cloud Foundry v158 and above.</p>

From your Sematext account:

1. Click the [Create App / Logsene App](https://apps.sematext.com/logsene-reports/registerApplication.do) menu item. Enter a name and click to the "Add Application" button to create the Logsene App. 

1. Create the log drain service in Cloud Foundry using the displayed URL.

    `$ cf cups logsene-log-drain -l https://logsene-cf-receiver.sematext.com/YOUR_LOGSENE_TOKEN`

1. Bind the log drain to an app. You could optionally bind multiple apps to one log drain.
	`$cf bind-service YOUR-CF-APP-NAME logsene-log-drain`

1. Restage or push the app using either the `cf restage YOUR-CF-APP-NAME` or `cf push YOUR-CF-APP-NAME` command. After a short delay, logs begin to flow automatically and appear in the [Logsene UI](https://apps.sematext.com/users-web/services.do#logsene).


{'fraction_non_alphanumeric': 0.13026035696741445, 'fraction_numerical': 0.012280989028983134, 'mean_word_length': 3.866533864541833, 'pattern_counts': {'":': 0, '<': 89, '<?xml version=': 0, '>': 89, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5101561', 'n_tokens_mistral': 3959, 'n_tokens_neox': 3714, 'n_words': 1344}