This topic explains how to send syslog-formatted logs (RFC 5424) to LaunchDarkly’s 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.
Once configured, these logs appear in the Logs page of the LaunchDarkly user interface.
Before you configure the syslog log drain, you must:
To find your client-side ID:
You can send syslog logs formatted in RFC5424 over TLS to LaunchDarkly’s syslog endpoint.
Endpoint: syslog.observability.app.launchdarkly.com:34302
To test the connection, run the following command, replacing YOUR_CLIENT_SIDE_ID with your LaunchDarkly client-side ID:
In this example, the structured data fields in the RFC5424 message are:
test-service): The name of your application or service.YOUR_CLIENT_SIDE_ID): Set this to your LaunchDarkly client-side ID to associate logs with your project.YOUR_CLIENT_SIDE_ID): Set this to your LaunchDarkly client-side ID.hello this is a test): The log message body.If you deploy your applications on Render, you can configure a log stream to automatically forward your logs to LaunchDarkly.
To configure the Render log stream:
syslog.observability.app.launchdarkly.com:34302.To learn more about Render log streams, read Render’s log streams documentation.
After you configure the log drain, your syslog logs begin forwarding to LaunchDarkly.
To verify that your logs are being received:
It may take a few minutes for logs to appear after you first configure the log drain.
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.