---
title: 'Log streaming: LogDNA'
summary: null
url: >-
  https://www.fastly.com/documentation/guides/integrations/logging-endpoints/log-management-and-observability/log-streaming-logdna
---

Fastly's [Real-Time Log Streaming](https://www.fastly.com/documentation/guides/integrations/streaming-logs/about-fastlys-realtime-log-streaming-features) feature can be configured to send logs in a format that is readable by [LogDNA](https://www.logdna.com). LogDNA is a cloud-based log management system that aggregates system and application logs into a single location.

> **NOTE:** 
>
> Fastly does not provide direct support for third-party services. Read [Fastly's Terms of Service](https://www.fastly.com/terms) for more information.
>
>

## Prerequisites

Before adding LogDNA as a logging endpoint for Fastly services, you'll need to perform the following steps:

- [Sign up](https://www.logdna.com/sign-up) for a LogDNA account if you don't already have one. You can sign up for a free (but restricted plan) or [upgrade a LogDNA plan](https://www.logdna.com/pricing) to include more features.
- [Set up a new LogDNA syslog source](https://docs.logdna.com/docs/syslog) via the LogDNA web application by following their account-tailored log source instructions. Be sure to make note of the port number displayed at the end of the syslog URL when you complete set up. This is the port number you'll enter when setting up LogDNA as a logging endpoint for Fastly.

## Adding LogDNA as a logging endpoint

### Cdn Services

1.   Review the information in our guide to [setting up remote log streaming](https://www.fastly.com/documentation/guides/integrations/streaming-logs/setting-up-remote-log-streaming).

2. From the **Add endpoint** menu, select **LogDNA (via Syslog)**.

3. Fill out the **Add Syslog endpoint** fields as follows:

   -   In the **Name** field, enter a human-readable name for the endpoint.

   -   In the **Placement** area, select where the logging call should be placed in the generated VCL. Valid values are **Format Version Default** and **None**. Read our guide on [changing log placement](https://www.fastly.com/documentation/guides/integrations/streaming-logs/changing-log-placement) for more information.

   -   In the **Log format** field, optionally enter an Apache-style string or VCL variables to use for log formatting. Consult the [example format section](https://www.fastly.com/documentation/guides/integrations/logging-endpoints/log-management-and-observability/log-streaming-logdna#example-format) for details.

   - In the **Syslog address** field, enter `syslog-a.logdna.com`. In the port field after the colon, enter the LogDNA port number you noted during your LogDNA account setup.

   - _(Optional)_ In the **Token** field, enter a string prefix (line prefix) to send in front of each log line.

     > **IMPORTANT:** To send a token, be sure the [log line format](https://www.fastly.com/documentation/guides/integrations/streaming-logs/changing-log-line-formats) is set to a format other than **Blank**.

   - From the **TLS** menu, select **Yes** to enable encryption for the syslog endpoint. The TLS Hostname and TLS CA Certificate fields will both appear.

   - In the **TLS hostname** field, enter `syslog-a.logdna.com`. This is the hostname Fastly will use to verify the syslog server's certificate.

   - _(Optional)_ In the **TLS CA certificate** field, copy and paste the certification authority (CA) certificate used to verify that the origin server's certificate is valid. The certificate you upload must be in PEM format. Consider uploading the certificate if it's not signed by a well-known certification authority. This value is not required if your TLS certificate is signed by a well-known authority.

   - _(Optional)_ In the **TLS client certificate** field, copy and paste the TLS client certificate used to authenticate to the origin server. The TLS client certificate you upload must be in PEM format and must be accompanied by a client certificate. A TLS client certificate allows your server to authenticate that Fastly is performing the connection.

   - _(Optional)_ In the **TLS client key** field, copy and paste the TLS client key used to authenticate to the backend server. The TLS client key you upload must be in PEM format and must be accompanied by a TLS client certificate. A TLS client key allows your server to authenticate that Fastly is performing the connection.

   -   *(Optional)* From the **Processing region** menu, select a geographic region where logs are processed before being sent to the logging endpoint. Our guide on [regional log aggregation](https://www.fastly.com/documentation/guides/integrations/streaming-logs/setting-up-regional-log-aggregation) provides more information.

4. _(Optional)_ To change the log line format, click **Advanced options**. 

   In the **Select a log line format** area, select the log line format for your log messages. Our guide on [changing log line formats](https://www.fastly.com/documentation/guides/integrations/streaming-logs/changing-log-line-formats) provides more information.

    This must be compatible with your LogDNA configuration.

5.   Click **Create** to create the new logging endpoint.

6.   From the **Activate** menu, select **Activate on Production** to deploy your configuration changes.

Logs should begin appearing in your LogDNA account a few seconds after you've created the endpoint and deployed your service.

### Example format

Format log messages using [RFC 5424](https://datatracker.ietf.org/doc/html/rfc5424) or [RFC 3164](https://datatracker.ietf.org/doc/html/rfc3164) formatting for auto-parsing by Syslog. Our guide on [useful log formats](https://www.fastly.com/documentation/guides/integrations/streaming-logs/useful-log-formats/) provides more information. The following example uses [Common Log Format (CLF)](https://www.fastly.com/documentation/guides/integrations/streaming-logs/useful-log-formats/#common-log-format-clf):

```plaintext
<134>1 %{%Y-%m-%dT%TZ}t %{server.datacenter}V <logging endpoint name> - - [tag="fastly"] %h %l %u %t "%r" %>s %b
```

### Compute Services

1.   Review the information in our guide to [setting up remote log streaming for Compute](https://www.fastly.com/documentation/guides/integrations/streaming-logs/setting-up-remote-log-streaming-for-compute). Additionally, our developer documentation provides more [information about logging](https://www.fastly.com/documentation/guides/integrations/non-fastly-services/developer-guide-logging/) with Compute code written in our [supported languages](https://www.fastly.com/documentation/reference/compute/sdks/).

2. From the **Add endpoint** menu, select **LogDNA (via Syslog)**.

3. Fill out the **Add Syslog endpoint** fields as follows:

   -   In the **Name** field, enter the endpoint name you specified in your Compute code. For example, in our [Rust code example](https://www.fastly.com/documentation/guides/compute/developer-guides/rust/#logging), the name is `my_endpoint_name`.

   - In the **Syslog address** field, enter `syslog-a.logdna.com`. In the port field after the colon, enter the LogDNA port number you noted during your LogDNA account setup.

   - _(Optional)_ In the **Token** field, enter a string prefix (line prefix) to send in front of each log line.

     > **IMPORTANT:** To send a token, be sure the [log line format](https://www.fastly.com/documentation/guides/integrations/streaming-logs/changing-log-line-formats) is set to a format other than **Blank**.

   - From the **TLS** menu, select **Yes** to enable encryption for the Syslog endpoint. The TLS Hostname and TLS CA Certificate fields will both appear.

   - In the **TLS hostname** field, enter `syslog-a.logdna.com`. This is the hostname Fastly will use to verify the Syslog server's certificate.

   - _(Optional)_ In the **TLS CA certificate** field, copy and paste the certification authority (CA) certificate used to verify that the origin server's certificate is valid. The certificate you upload must be in PEM format. Consider uploading the certificate if it's not signed by a well-known certification authority. This value is not required if your TLS certificate is signed by a well-known authority.

   - _(Optional)_ In the **TLS client certificate** field, copy and paste the TLS client certificate used to authenticate to the origin server. The TLS client certificate you upload must be in PEM format and must be accompanied by a client certificate. A TLS client certificate allows your server to authenticate that Fastly is performing the connection.

   - _(Optional)_ In the **TLS client key** field, copy and paste the TLS client key used to authenticate to the backend server. The TLS client key you upload must be in PEM format and must be accompanied by a TLS client certificate. A TLS client key allows your server to authenticate that Fastly is performing the connection.

   -   *(Optional)* From the **Processing region** menu, select a geographic region where logs are processed before being sent to the logging endpoint. Our guide on [regional log aggregation](https://www.fastly.com/documentation/guides/integrations/streaming-logs/setting-up-regional-log-aggregation) provides more information.

4. _(Optional)_ To change the log line format, click **Advanced options**. 

   In the **Select a log line format** area, select the log line format for your log messages. Our guide on [changing log line formats](https://www.fastly.com/documentation/guides/integrations/streaming-logs/changing-log-line-formats) provides more information.

    This must be compatible with your LogDNA configuration.

5.   Click **Create** to create the new logging endpoint.

6.   From the **Activate** menu, select **Activate on Production** to deploy your configuration changes.

Logs should begin appearing in your LogDNA account a few seconds after you've created the endpoint and deployed your service.

### Recommended log format

Format log messages using [RFC 5424](https://datatracker.ietf.org/doc/html/rfc5424) or [RFC 3164](https://datatracker.ietf.org/doc/html/rfc3164) formatting for auto-parsing by Syslog. 

## Related content

- [API reference: Syslog log streaming](https://www.fastly.com/documentation/reference/api/logging/syslog/)
- [CLI reference: Syslog log streaming](https://www.fastly.com/documentation/reference/cli/logging/syslog/)
