Documentation forSolarWinds Observability SaaS

Send logs using syslog (Papertrail)

Each syslog message carries its own hostname, program name, and severity, which fill the System, Program, and Severity columns in the Logs Explorer.

Choosing an ingestion method

Method Endpoint Authentication When to use
Syslog over TLS (recommended) syslog.collector.<REGION>.cloud.solarwinds.com:6514 Ingestion token in RFC 5424 structured data Servers, applications, and shippers that can send RFC 5424 over TLS
Syslog over HTTPS

https://logs.collector.<REGION>.cloud.solarwinds.com/v1/logs

and /v1/logs/bulk

Authorization: Bearer <TOKEN> header Only port 443 is open outbound, or you want to send batches with one token per request

Replace <REGION> with the data center your organization uses: na-01, eu-01, or ap-01. You can find this in the URL you use to sign in (for example, my.na-01.cloud.solarwinds.com). See Data centers and endpoint URIs.

Before you begin

  1. Create or select an ingestion token.

    To get a destination and token in Papertrail, add a new log destination. The ingestion token is generated along with the destination. Use the collector endpoints for your account's region:

    • Syslog (TLS): syslog.collector.<REGION>.cloud.solarwinds.com:6514

    Replace <REGION> with the data center your organization uses: na-01, eu-01, or ap-01.

  2. Allow outbound connections to syslog.collector.<REGION>.cloud.solarwinds.com on TCP port 6514 and to logs.collector.<REGION>.cloud.solarwinds.com on TCP port 443 (if using syslog over HTTPS).

  3. Use TLS. The syslog endpoint only accepts TLS connections. Plaintext TCP and UDP are not accepted.

  4. Keep TLS certificate verification turned on.

Message format

The syslog endpoint expects RFC 5424 messages:

<PRI>1 TIMESTAMP HOSTNAME APP-NAME PROCID MSGID [STRUCTURED-DATA] MSG

For example:

<14>1 2026-10-13T10:00:00Z web-01 checkout 4242 - [solarwinds@41058 token="<TOKEN>"] Order 1234 processed
Field Example Shown as
PRI <14> (facility user, severity info) Severity (PRI = facility x 8 + severity)
TIMESTAMP 2026-10-13T10:00:00Z N/A
HOSTNAME web-01 System
APP-NAME checkout Program
PROCID, MSGID 4242, -

Searchable syslog attributes.

Search with syslog.procId:4242 and syslog.msgid:order-placed. Use - when a value is not available.

STRUCTURED-DATA [solarwinds@41058 token="..."]

Authentication (see below).

Other private elements (name@number) become searchable attributes.

MSG Order 1234 processed Message

The first message on a connection must start with the <PRI> value and carry the token.

A single syslog message must be smaller than 1,000,000 bytes. A larger message is not ingested and ends the connection, requiring the sender to reconnect. Over HTTPS, the limits are 1 MB per message and 5 MB per request.

RFC 3164 (BSD syslog) has no structured-data field and cannot carry the token. Convert it to RFC 5424 with a relay such as rsyslog or syslog-ng.

Authenticate with an ingestion token

The token is sent inside an RFC 5424 structured-data element that uses the SolarWinds private enterprise number 41058. Two formats are accepted:

Recommended format

[solarwinds@41058 token="<TOKEN>"]

The collector looks for the literal string [solarwinds@41058 token=" and takes everything up to the next double quote as the token. Anything that does not match that literal exactly is not recognized. Follow these rules:

  • The SD-ID is solarwinds@41058 in lowercase.

  • token is the first parameter, separated from the SD-ID by a single space. Further parameters may follow it.

  • The value is enclosed in double quotes. Single quotes are not accepted.

  • The SolarWinds element should be first in the structured data.

  • Other structured-data elements become searchable attributes if their SD-ID is private (name@number, for example [exampleSDID@32473 iut="3"]) and the element has at least one parameter. Search them with syslog.sd.id:exampleSDID, syslog.sd.pen:32473, or by parameter, as in syslog.sd.iut:3.

This format complies with RFC 5424, which limits an SD-ID to 32 characters. Logging libraries that model structured data as "ID plus parameters," such as Log4j2, Python rfc5424-logging-handler, and syslog-ng, can produce it directly.

Legacy format

[<TOKEN>@41058]

In this format, the token itself is the SD-ID. It is still supported, so existing configurations continue working. However, ingestion tokens are 71 characters, so this format exceeds the RFC 5424 32 character SD-ID limit, and libraries that enforce the limit, such as Log4j2 RFC5424Layout or the Python rfc5424-logging-handler, reject it. Use the recommended format for new setups. If a message contains both formats, the recommended format takes precedence, regardless of which element comes first.

How authentication works on a connection

  1. The collector caches the first token it finds on a connection and uses it for every later message on that connection. Messages that arrive before the first token are dropped, and later messages do not need to carry the token.

  2. The token is not checked when it is cached. If the first message carries an incorrect token, all messages on that connection are rejected. Fix the token and reconnect.

  3. To switch to a different token, open a new connection. A token sent later on the same connection is ignored.

Framing and multiline messages

The syslog endpoint supports both TCP framing methods defined in RFC 6587 and detects the method from the first byte of the connection.

  Newline-delimited (non-transparent) Octet-counted
Frame SYSLOG-MSG LF MSG-LEN SP SYSLOG-MSG
Detected when the frame starts with Any byte other than a digit (in practice <) A digit
End of message First line feed (\n) After MSG-LEN bytes
Newlines inside the message End the message - multiline events are split Preserved - multiline events stay intact

MSG-LEN is the message size in UTF-8 bytes (not characters), excluding the space after the number. In the example below it is 58. The example carries no token, so it cannot be used as the first frame on a connection.

58 <14>1 2026-10-13T10:00:00Z web-01 checkout - - - Hello SWO

Recommendations

  • Use octet-counted framing for stack traces and other multiline events. With newline-delimited framing, each continuation line is stored as a separate event without the original syslog header. Such events show the sender's IP address as the System and have no Program.

  • If you cannot change the framing method, replace the line feeds in the message before you send it. For example, you can use a literal \n. The event then stays whole and searchable, but its line breaks are no longer real line breaks.

  • Use one framing method per connection.

Quick test

Send a test message to confirm connectivity and authentication. Each example opens its own connection because the framing method is detected per connection. Replace <REGION> and <TOKEN>.

The collector does not acknowledge individual messages, so a command that completes without an error does not prove the message was ingested. Always confirm in the Logs Explorer.

Newline-delimited framing

The message ends with a line feed.

Windows PowerShell:

$h = "syslog.collector.<REGION>.cloud.solarwinds.com"; $t = (Get-Date).ToUniversalTime().ToString("yyyy-MM-dd'T'HH:mm:ss'Z'")
$c = [Net.Sockets.TcpClient]::new($h, 6514); $s = [Net.Security.SslStream]::new($c.GetStream()); $s.AuthenticateAsClient($h)
$b = [Text.Encoding]::UTF8.GetBytes("<14>1 $t test-host test-app - - [solarwinds@41058 token=`"<TOKEN>`"] Test message from PowerShell`n")
$s.Write($b, 0, $b.Length); $s.Flush(); $c.Close()

Linux or macOS:

echo "<14>1 $(date -u +%Y-%m-%dT%H:%M:%SZ) test-host test-app - - [solarwinds@41058 token=\"<TOKEN>\"] Test message from Linux" | openssl s_client -quiet -no_ign_eof -connect syslog.collector.<REGION>.cloud.solarwinds.com:6514

In the Logs Explorer, search for Test message. The System column shows test-host and the Program column shows test-app.

Octet-counted framing

The message is prefixed with its length in bytes and a space. The example message contains a line break to show that multiline content stays in one event.

Windows PowerShell:

$h = "syslog.collector.<REGION>.cloud.solarwinds.com"; $t = (Get-Date).ToUniversalTime().ToString("yyyy-MM-dd'T'HH:mm:ss'Z'")
$c = [Net.Sockets.TcpClient]::new($h, 6514); $s = [Net.Security.SslStream]::new($c.GetStream()); $s.AuthenticateAsClient($h)
$m = "<14>1 $t test-host test-app - - [solarwinds@41058 token=`"<TOKEN>`"] Octet-counted test from PowerShell`n  second line"
$b = [Text.Encoding]::UTF8.GetBytes("$([Text.Encoding]::UTF8.GetByteCount($m)) $m")
$s.Write($b, 0, $b.Length); $s.Flush(); $c.Close()

Linux or macOS:

m="<14>1 $(date -u +%Y-%m-%dT%H:%M:%SZ) test-host test-app - - [solarwinds@41058 token=\"<TOKEN>\"] Octet-counted test from Linux"$'\n  second line'
printf '%s %s' "${#m}" "$m" | openssl s_client -quiet -no_ign_eof -connect syslog.collector.<REGION>.cloud.solarwinds.com:6514

In the Logs Explorer, search for Octet-counted test. The message appears as one event that includes second line.

Syslog over HTTPS

You can send RFC 5424 messages to the HTTPS logs collector. This is useful when only port 443 is open outbound, when you go through an HTTP proxy, or when you want to authenticate an entire batch once in a header. Messages are parsed as syslog, so hostname, program, and severity are taken from each message's syslog header. The token in structured data is not needed, as authentication comes from the Authorization header.

Endpoint Content-Type Body Newlines inside a message
POST /v1/logs text/plain, application/octet-stream, or application/json One syslog message Preserved
POST /v1/logs/bulk text/plain, application/octet-stream, application/json, or application/x-ndjson One message per line Split. Each LF, CR, or CRLF ends a message.
POST /v1/logs/bulk application/syslog-frames Octet-counted frames (MSG-LEN SP SYSLOG-MSG), concatenated Preserved. Use this for multiline events.

Common rules

  • Authenticate with Authorization: Bearer <TOKEN>.

  • For higher volumes, batch messages with /v1/logs/bulk instead of sending one message per request. A message must be smaller than 1 MB and a whole request smaller than 5 MB.

  • System, Program, and Severity are taken from each message's syslog header.

Responses

Status Meaning
202 Accepted Request accepted
401 Missing or invalid token
413 A message is larger than 1 MB, the request is larger than 5 MB, or the length prefix of an octet-counted frame is not a valid number
415

Unsupported Content-Type for the endpoint

(For example, application/syslog-frames sent to /v1/logs)

A length prefix that is a valid number but larger than the data that follows is not reported as an error. The request is accepted, and the message is stored truncated. Compute frame lengths from the actual byte count.

Single message (Windows PowerShell):

$t = (Get-Date).ToUniversalTime().ToString("yyyy-MM-dd'T'HH:mm:ss'Z'")
curl.exe -X POST "https://logs.collector.<REGION>.cloud.solarwinds.com/v1/logs" -H "Authorization: Bearer <TOKEN>" -H "Content-Type: text/plain" --data-raw "<14>1 $t test-host test-app - - - Test message over HTTPS"

Batch with octet-counted framing, keeping a multiline stack trace intact (Windows PowerShell):

$t = (Get-Date).ToUniversalTime().ToString("yyyy-MM-dd'T'HH:mm:ss'Z'")
$m = "<14>1 $t web-01 checkout - - - Order 1234 processed", "<11>1 $t web-01 checkout - - - Payment failed`n  at Payment.charge()`n  at Order.submit()"
$body = ($m | ForEach-Object { "$([Text.Encoding]::UTF8.GetByteCount($_)) $_" }) -join ''
Invoke-RestMethod -Method Post -Uri "https://logs.collector.<REGION>.cloud.solarwinds.com/v1/logs/bulk" -Headers @{ Authorization = "Bearer <TOKEN>" } -ContentType "application/syslog-frames" -Body ([Text.Encoding]::UTF8.GetBytes($body))

The same batch with curl (Linux or macOS):

t=$(date -u +%Y-%m-%dT%H:%M:%SZ)
m1="<14>1 $t web-01 checkout - - - Order 1234 processed"
m2="<11>1 $t web-01 checkout - - - Payment failed"$'\n  at Payment.charge()\n  at Order.submit()'
printf '%s %s%s %s' "${#m1}" "$m1" "${#m2}" "$m2" | curl -X POST "https://logs.collector.<REGION>.cloud.solarwinds.com/v1/logs/bulk" \
  -H "Authorization: Bearer <TOKEN>" -H "Content-Type: application/syslog-frames" --data-binary @-

Troubleshooting

Symptom Likely cause What to do
No logs arrive TLS handshake fails or port 6514 is blocked Run openssl s_client -connect syslog.collector.<REGION>.cloud.solarwinds.com:6514 from the sender, or run the PowerShell test above on Windows, where openssl is usually not installed. Check firewall and proxy rules.
No logs arrive but TLS works Token not recognized Check that the exact literal [solarwinds@41058 token="..."] contains the lowercase SD-ID, token first, double quotes, no second space.
Logs stop or keep failing after you change the token The connection still uses the first token it received Restart the sender so it opens a new connection.
Stack traces split into many events Newline-delimited framing Switch to octet-counted framing (for example rsyslog TCP_Framing="octet-counted"), replace the line feeds in the message, or use /v1/logs/bulk with application/syslog-frames.
Library error about SD-ID length (Log4j2, Python, Fluent Bit) Legacy [<TOKEN>@41058] format exceeds 32 characters Use [solarwinds@41058 token="<TOKEN>"].
Connection closes after a quiet period Idle timeout Enable reconnect and queuing in the sender (for example rsyslog action.resumeRetryCount="-1").
Wrong System name The HOSTNAME header field is empty or -, or the event is a continuation line that carries no syslog header Set the hostname in your sender's configuration. For split stack traces, switch to octet-counted framing.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.