Skip to main content

Cribl Stream TCP Syslog Debug Logs Appear Only on Connection Events

  • Nov 19, 2026 8:48 PM UTC
  • 0 replies
  • 1 view

Jessica Bracken

Symptom

After changing a TCP Syslog source's logging level from info to debug and committing and deploying the configuration, expected debug details might not appear during normal operation. Worker logs might show only opened connection, starting input, and closed connection; these messages do not include the remote source IP/name or why the connection closed.

Environment

  • Cribl Stream distributed deployment
  • TCP Syslog source using non-TLS TCP

Resolution

  1. Select the affected Worker Group.
  2. Navigate to Worker Group/Fleet Settings > System > Logging > Levels.
  3. Locate the logging channel associated with the source's TCP sub-input.
  4. Set the channel's Level to debug.
  5. Click Save.
  6. Click Commit & Deploy.
  7. Wait for a TCP connection to open or close to see the corresponding debug messages; these events are infrequent during normal operation.

Note: The logging-level change takes effect through the normal commit/deploy path and does not require a worker restart.

Cause

This can be caused by the way Cribl Stream logs TCP Syslog input activity:

  • A Syslog source has separate logging channels for the parent source and its TCP and UDP sub-inputs. The TCP sub-input can be at debug but emits debug messages only for connection open/close events, which are infrequent during normal operation.

Additional Information

For logging-channel navigation and settings, see Monitor Health and Metrics.