---
title: "sumologic-syslog() destination options"
url: "https://axoflow.com/docs/axosyslog-core/4.28/chapter-destinations/destination-sumologic-intro/destination-sumologic-options/destination-sumologic-options-syslog/"
last_modified: "2023-06-27T21:08:08+02:00"
---

> For the complete documentation index, see [llms.txt](https://axoflow.com/docs/axosyslog-core/4.28/llms.txt).

# sumologic-syslog() destination options

The `sumologic-syslog()` destination supports all [network() destination options](https://axoflow.com/docs/axosyslog-core/4.28/chapter-destinations/configuring-destinations-network/reference-destination-network-chapter/index.md).

In addition, the `sumologic-syslog()` destination also has the following options.

## ca-dir()

|  |  |
| --- | --- |
| Accepted values: | Directory name |
| Default: | none |

*Description:* The name of a directory that contains a set of trusted CA certificates in PEM format. The CA certificate files have to be named after the 32-bit hash of the subject’s name. This naming can be created using the c_rehash utility in openssl. For an example, see [Configuring TLS server authentication on the AxoSyslog clients](https://axoflow.com/docs/axosyslog-core/4.28/chapter-encrypted-transport-tls/tls-serverauth/procedure-configuring-tls-client/index.md). The AxoSyslog application uses the CA certificates in this directory to validate the certificate of the peer.

This option can be used together with the optional `ca-file()` option.

## ca-file()

|  |  |
| --- | --- |
| Accepted values: | File name |
| Default: | empty |

*Description:* Optional. The name of a file that contains a set of trusted CA certificates in PEM format. The AxoSyslog application uses the CA certificates in this file to validate the certificate of the peer.

Example format in configuration:

```shell
ca-file("/etc/pki/tls/certs/ca-bundle.crt")
```

> **Note:**
> The `ca-file()` option can be used together with the `ca-dir()` option, and it is relevant when `peer-verify()` is set to other than `no` or `optional-untrusted`.

## deployment()

|  |  |
| --- | --- |
| Type: | string |
| Default: | empty string |

*Description:* Required. This option specifies your [Sumo Logic deployment](https://help.sumologic.com/APIs/General-API-Information/Sumo-Logic-Endpoints-and-Firewall-Security).

For details on the `deployment()` option in the `sumologic-http()` destination’s declaration, see [Declaration for the sumologic-http() destination](https://axoflow.com/docs/axosyslog-core/4.28/chapter-destinations/destination-sumologic-intro/index.md).

For details on the `deployment()` option in the `sumologic-syslog()` destination’s declaration, see [Declaration for the sumologic-syslog() destination](https://axoflow.com/docs/axosyslog-core/4.28/chapter-destinations/destination-sumologic-intro/index.md).

## port()

|  |  |
| --- | --- |
| Type: | number |
| Default: | 6514 |

*Description:* Optional. This option sets the port number of the Sumo Logic server to connect to.

## tag()

|  |  |
| --- | --- |
| Type: | string list |
| Default: | “tag” |

*Description:* Optional. This option specifies the list of tags to add as the tags fields of Sumo Logic messages. If not specified, AxoSyslog automatically adds the tags already assigned to the message. If you set the `tag()` option, only the tags you specify will be added to the messages.

## tls()

|  |  |
| --- | --- |
| Type: | tls options |
| Default: | n/a |

*Description:* This option sets various options related to TLS encryption, for example, key/certificate files and trusted CA locations. TLS can be used only with tcp-based transport protocols. For details, see [TLS options](https://axoflow.com/docs/axosyslog-core/4.28/chapter-encrypted-transport-tls/tlsoptions/index.md).

In version 4.0 and newer, using the `tls()` option is optional, and Sumo Logic servers are verified using the system certificate store by default. In earlier versions, this was a required option.

## token()

|  |  |
| --- | --- |
| Type: | string |
| Default: |  |

*Description:* Required option. The Cloud Syslog Cloud Token that you received from the Sumo Logic service while [configuring your cloud syslog source](https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/Cloud-Syslog-Source#configure-a-cloud%C2%A0syslog%C2%A0source).

Last modified June 27, 2023: [Update paths to follow-up moving the files (6585a5b1)](https://github.com/axoflow/axosyslog-core-docs/commit/6585a5b156244e39bb831bf4e8289529f30dea0f)