> ## Documentation Index
> Fetch the complete documentation index at: https://launchdarkly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Syslog log drain

export const host_2 = "syslog.observability.app.eu.launchdarkly.com"

export const host_1 = "syslog.observability.app.launchdarkly.com"

export const host_0 = "syslog.observability.app.launchdarkly.com"

<View title="Developer">
  <View title="Federal docs">
    <Danger>
      **Observability is not available in federal environments**

      To learn more, read <a href="/docs/home/infrastructure/federal">LaunchDarkly in federal environments</a>.
    </Danger>
  </View>

  This topic explains how to send syslog-formatted logs ([RFC 5424](https://www.rfc-editor.org/rfc/rfc5424)) to LaunchDarkly observability features using a syslog log drain. You can send logs directly from any system that supports syslog output, or configure a log stream from hosting platforms like Render.

  After you configure them, these logs appear in the [Logs](/docs/home/observability/logs) page of the LaunchDarkly user interface.

  ## Prerequisites

  Before you configure the syslog log drain, you must:

  * Have LaunchDarkly observability enabled for your project
  * Know your LaunchDarkly client-side ID

  To find your client-side ID:

  1. Click the project dropdown in the LaunchDarkly UI to open the project menu.
  2. Select **Project settings**.
  3. Click **Environments**.
  4. Find the environment you want to use and copy the **Client-side ID** value.

  ## Send syslog logs directly

  You can send syslog logs formatted in RFC5424 over TLS to the LaunchDarkly syslog endpoint.

  **Endpoint:** <code>{host_0}:34302</code>

  To test the connection, run the following command, replacing `YOUR_CLIENT_SIDE_ID` with your LaunchDarkly client-side ID:

  <CodeGroup>
    ```bash title="Send a test message" lines wrap theme={null}
    echo "<0>1 2021-03-31T16:00:00-08:00 test-service YOUR_CLIENT_SIDE_ID 74440 YOUR_CLIENT_SIDE_ID - hello this is a test" | ncat --ssl syslog.observability.app.launchdarkly.com 34302
    ```
  </CodeGroup>

  In this example, the structured data fields in the RFC5424 message are:

  * **APP-NAME** (`test-service`): The name of your application or service.
  * **PROCID** (`YOUR_CLIENT_SIDE_ID`): Set this to your LaunchDarkly client-side ID to associate logs with your project.
  * **MSGID** (`YOUR_CLIENT_SIDE_ID`): Set this to your LaunchDarkly client-side ID.
  * **MSG** (`hello this is a test`): The log message body.

  ## Configure Render log streams

  If you deploy your applications on [Render](https://render.com), you can configure a log stream to automatically forward your logs to LaunchDarkly.

  To configure the Render log stream:

  1. Click your account dropdown and select **Settings** on the Render **Settings** page.
  2. Click the **Log Streams** tab.
  3. Click **Add Log Stream**.
  4. Enter <code>{host_0}:34302</code> in the endpoint field.
  5. Enter your LaunchDarkly client-side ID in the token field.
  6. Click **Save**.

  To learn more about Render log streams, read [Render's log streams documentation](https://render.com/docs/log-streams).

  ## Verify that logs are being received

  After you configure the log drain, your syslog logs begin forwarding to LaunchDarkly.

  To verify that your logs are being received:

  1. Open the **Telemetry** section and navigate to the **Logs** list.
  2. Choose or search for logs from your syslog-configured services.

  It may take a few minutes for logs to appear after you first configure the log drain.

  ## Filtering logs

  You can configure ingestion filters to control which logs are stored in LaunchDarkly. This is useful for excluding noisy logs or limiting ingestion to stay within your observability quotas.

  To learn more, read [Filters](/docs/home/observability/settings#filters).
</View>

<View title="Federal docs">
  <View title="Federal docs">
    <Danger>
      **Observability is not available in federal environments**

      To learn more, read <a href="/docs/home/infrastructure/federal">LaunchDarkly in federal environments</a>.
    </Danger>
  </View>

  This topic explains how to send syslog-formatted logs ([RFC 5424](https://www.rfc-editor.org/rfc/rfc5424)) to LaunchDarkly observability features using a syslog log drain. You can send logs directly from any system that supports syslog output, or configure a log stream from hosting platforms like Render.

  After you configure them, these logs appear in the [Logs](/docs/home/observability/logs) page of the LaunchDarkly user interface.

  ## Prerequisites

  Before you configure the syslog log drain, you must:

  * Have LaunchDarkly observability enabled for your project
  * Know your LaunchDarkly client-side ID

  To find your client-side ID:

  1. Click the project dropdown in the LaunchDarkly UI to open the project menu.
  2. Select **Project settings**.
  3. Click **Environments**.
  4. Find the environment you want to use and copy the **Client-side ID** value.

  ## Send syslog logs directly

  You can send syslog logs formatted in RFC5424 over TLS to the LaunchDarkly syslog endpoint.

  **Endpoint:** <code>{host_1}:34302</code>

  To test the connection, run the following command, replacing `YOUR_CLIENT_SIDE_ID` with your LaunchDarkly client-side ID:

  <CodeGroup>
    ```bash title="Send a test message" lines wrap theme={null}
    echo "<0>1 2021-03-31T16:00:00-08:00 test-service YOUR_CLIENT_SIDE_ID 74440 YOUR_CLIENT_SIDE_ID - hello this is a test" | ncat --ssl syslog.observability.app.launchdarkly.com 34302
    ```
  </CodeGroup>

  In this example, the structured data fields in the RFC5424 message are:

  * **APP-NAME** (`test-service`): The name of your application or service.
  * **PROCID** (`YOUR_CLIENT_SIDE_ID`): Set this to your LaunchDarkly client-side ID to associate logs with your project.
  * **MSGID** (`YOUR_CLIENT_SIDE_ID`): Set this to your LaunchDarkly client-side ID.
  * **MSG** (`hello this is a test`): The log message body.

  ## Configure Render log streams

  If you deploy your applications on [Render](https://render.com), you can configure a log stream to automatically forward your logs to LaunchDarkly.

  To configure the Render log stream:

  1. Click your account dropdown and select **Settings** on the Render **Settings** page.
  2. Click the **Log Streams** tab.
  3. Click **Add Log Stream**.
  4. Enter <code>{host_1}:34302</code> in the endpoint field.
  5. Enter your LaunchDarkly client-side ID in the token field.
  6. Click **Save**.

  To learn more about Render log streams, read [Render's log streams documentation](https://render.com/docs/log-streams).

  ## Verify that logs are being received

  After you configure the log drain, your syslog logs begin forwarding to LaunchDarkly.

  To verify that your logs are being received:

  1. Open the **Telemetry** section and navigate to the **Logs** list.
  2. Choose or search for logs from your syslog-configured services.

  It may take a few minutes for logs to appear after you first configure the log drain.

  ## Filtering logs

  You can configure ingestion filters to control which logs are stored in LaunchDarkly. This is useful for excluding noisy logs or limiting ingestion to stay within your observability quotas.

  To learn more, read [Filters](/docs/home/observability/settings#filters).
</View>

<View title="EU docs">
  <View title="Federal docs">
    <Danger>
      **Observability is not available in federal environments**

      To learn more, read <a href="/docs/home/infrastructure/federal">LaunchDarkly in federal environments</a>.
    </Danger>
  </View>

  This topic explains how to send syslog-formatted logs ([RFC 5424](https://www.rfc-editor.org/rfc/rfc5424)) to LaunchDarkly observability features using a syslog log drain. You can send logs directly from any system that supports syslog output, or configure a log stream from hosting platforms like Render.

  After you configure them, these logs appear in the [Logs](/docs/home/observability/logs) page of the LaunchDarkly user interface.

  ## Prerequisites

  Before you configure the syslog log drain, you must:

  * Have LaunchDarkly observability enabled for your project
  * Know your LaunchDarkly client-side ID

  To find your client-side ID:

  1. Click the project dropdown in the LaunchDarkly UI to open the project menu.
  2. Select **Project settings**.
  3. Click **Environments**.
  4. Find the environment you want to use and copy the **Client-side ID** value.

  ## Send syslog logs directly

  You can send syslog logs formatted in RFC5424 over TLS to the LaunchDarkly syslog endpoint.

  **Endpoint:** <code>{host_2}:34302</code>

  To test the connection, run the following command, replacing `YOUR_CLIENT_SIDE_ID` with your LaunchDarkly client-side ID:

  <CodeGroup>
    ```bash title="Send a test message" lines wrap theme={null}
    echo "<0>1 2021-03-31T16:00:00-08:00 test-service YOUR_CLIENT_SIDE_ID 74440 YOUR_CLIENT_SIDE_ID - hello this is a test" | ncat --ssl syslog.observability.app.eu.launchdarkly.com 34302
    ```
  </CodeGroup>

  In this example, the structured data fields in the RFC5424 message are:

  * **APP-NAME** (`test-service`): The name of your application or service.
  * **PROCID** (`YOUR_CLIENT_SIDE_ID`): Set this to your LaunchDarkly client-side ID to associate logs with your project.
  * **MSGID** (`YOUR_CLIENT_SIDE_ID`): Set this to your LaunchDarkly client-side ID.
  * **MSG** (`hello this is a test`): The log message body.

  ## Configure Render log streams

  If you deploy your applications on [Render](https://render.com), you can configure a log stream to automatically forward your logs to LaunchDarkly.

  To configure the Render log stream:

  1. Click your account dropdown and select **Settings** on the Render **Settings** page.
  2. Click the **Log Streams** tab.
  3. Click **Add Log Stream**.
  4. Enter <code>{host_2}:34302</code> in the endpoint field.
  5. Enter your LaunchDarkly client-side ID in the token field.
  6. Click **Save**.

  To learn more about Render log streams, read [Render's log streams documentation](https://render.com/docs/log-streams).

  ## Verify that logs are being received

  After you configure the log drain, your syslog logs begin forwarding to LaunchDarkly.

  To verify that your logs are being received:

  1. Open the **Telemetry** section and navigate to the **Logs** list.
  2. Choose or search for logs from your syslog-configured services.

  It may take a few minutes for logs to appear after you first configure the log drain.

  ## Filtering logs

  You can configure ingestion filters to control which logs are stored in LaunchDarkly. This is useful for excluding noisy logs or limiting ingestion to stay within your observability quotas.

  To learn more, read [Filters](/docs/home/observability/settings#filters).
</View>