For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
      • AWS CloudWatch Metrics
      • AWS FireLens
      • Azure Monitor
      • Datadog Agent ingestion
      • Fluent Bit
      • Syslog log drain
      • Vercel
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Prerequisites
  • Send syslog logs directly
  • Configure Render log streams
  • Verify that logs are being received
  • Filtering logs
ObservabilityObservability integrations

Syslog log drain

Was this page helpful?
Previous

Vercel

Next
Built with
Observability is not available in LaunchDarkly's European Union (EU) instance
To learn more, read LaunchDarkly in the European Union (EU).

Overview

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.

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. In the LaunchDarkly UI, click the project dropdown 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 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:

$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

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, you can configure a log stream to automatically forward your logs to LaunchDarkly.

To configure the Render log stream:

  1. In the Render dashboard, click your account dropdown in the top right corner and select Settings.
  2. Click the Log Streams tab on the left.
  3. Click Add Log Stream.
  4. For the endpoint, enter syslog.observability.app.launchdarkly.com:34302.
  5. For the token, enter your LaunchDarkly client-side ID.
  6. Click Save.

To learn more about Render log streams, read Render’s log streams documentation.

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.