awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
gliderlabs avatar

gliderlabs/logspout

0
View on GitHub↗

Logspout

Logspout is a container log aggregator, forwarder, and routing engine designed to gather logs from Docker containers and route them to centralized external logging systems. It functions as a network-based utility that pipes container output to remote destinations such as syslog or TCP endpoints.

The system features a dynamic routing engine that allows the creation and updating of log routing configurations and destination filters in real time via an HTTP interface without restarting the service. It utilizes an adapter-based architecture, enabling the development of custom output modules and the creation of tailored container images to support proprietary destinations.

The platform provides capabilities for log source filtering based on container names, IDs, or labels, and supports multi-destination routing. It includes log processing utilities for multiline aggregation and template-based formatting to transform raw output into structured JSON or text. Data transmission is secured through transport-layer TLS encryption with support for mutual authentication and custom certificate authorities.

Additional observability is provided through real-time log streaming via WebSockets and chunked HTTP encoding, alongside stream timeout detection to prevent data loss.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Features

  • Docker Log Management - Collects logs from Docker containers and forwards them to remote destinations for centralized analysis.
  • Log Routing - Directs container standard output and error streams to external destinations using filters based on container names, IDs, and labels.
  • Log Aggregators - Streams container logs to remote syslog or TCP endpoints for centralized aggregation.
  • Multi-Destination Log Routers - Routes log streams from Docker containers to multiple remote destinations like syslog or TCP.
  • Docker Engine API Clients - Consumes real-time log streams directly from the Docker engine using its native API.
  • Docker Log Forwarders - Functions as a network-based utility piping Docker container output to external servers.
  • Pluggable Output Adapters - Implements an adapter-based architecture to decouple log collection from delivery to various remote protocols.
  • Multi-Destination Log Routings - Exports container logs to diverse external endpoints including syslog, TCP, UDP, and TLS transports.
  • Destination-Based Log Routing - Filters container logs by ID, name, or labels to forward matching data to specific network adapters and addresses.
  • Distributed Log Aggregation - Gathers distributed logs from multiple containers and routes them to a centralized logging system.
  • Log Routing Engines - Directs container logs to different destinations in real time using an HTTP interface and metadata filters.
  • Dynamic Stream Routing - Filters and routes container log streams to different destinations in real time via an HTTP API.
  • Dynamic Configuration Updates - Enables real-time updates of log routing rules and filters via a REST interface.
  • Runtime Configurations - Allows updating forwarding destinations and source filters while the service is active.
  • Dynamic Route Management - Provides an HTTP interface to modify log routing rules at runtime without requiring a service restart.
  • Mutual TLS Transports - Secures log transmission using mutual TLS authentication and custom certificate authority validation.
  • Log Transmission Security - Encrypts the transmission of container logs to remote servers using TLS and mutual authentication.
  • Custom Log Formatting - Transforms raw container output into structured formats like JSON for compatibility with monitoring tools.
  • Container Source Filters - Allows excluding or including specific containers in the log stream by matching names, environment variables, or metadata labels.
  • Custom Log Destinations - Allows developers to create custom output modules for routing logs to proprietary destinations.
  • Log Output Formatting - Transforms log messages into custom text or JSON formats using templates and metadata.
  • Multiline Log Grouping - Aggregates multiple log lines into single records to maintain the structure of stacked traces and formatted blocks.
  • Log Streaming - Provides real-time log streaming via WebSockets, JSON, or chunked HTTP encoding for debugging and subscriptions.
  • Log Output Templates - Transforms raw container output into structured JSON or text using metadata templates.
  • Monitoring and Logging - Log routing and aggregation for containerized environments.
4,688 stars·658 forks·Go·MIT·20 views

Star history

Star history chart for gliderlabs/logspoutStar history chart for gliderlabs/logspout

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

Frequently asked questions

What does gliderlabs/logspout do?

Logspout is a container log aggregator, forwarder, and routing engine designed to gather logs from Docker containers and route them to centralized external logging systems. It functions as a network-based utility that pipes container output to remote destinations such as syslog or TCP endpoints.

What are the main features of gliderlabs/logspout?

The main features of gliderlabs/logspout are: Docker Log Management, Log Routing, Log Aggregators, Multi-Destination Log Routers, Docker Engine API Clients, Docker Log Forwarders, Pluggable Output Adapters, Multi-Destination Log Routings.

Which projects share features with gliderlabs/logspout?

Projects with overlapping indexed features include: tstack/lnav — lnav is a terminal-based log viewer and analyzer designed for aggregating, filtering, and analyzing multiple log files… nlog/nlog — NLog is an open-source logging framework for .NET that functions as a structured logging library and log routing… klauscfhq/signale — Signale is a formatted console logging library for Node.js applications. It serves as a pluggable logging framework… fluent/fluentd — Fluentd is a unified logging layer and distributed event router that collects, parses, and routes log data from… kube-logging/logging-operator — The logging operator is a Kubernetes-native controller designed to automate the deployment, configuration, and… swiftybeaver/swiftybeaver — SwiftyBeaver is an extensible logging framework for Swift that routes log output to multiple destinations…

Projects sharing features with Logspout

These projects share indexed features with Logspout. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • tstack/lnavtstack avatar

    tstack/lnav

    9,630View on GitHub↗

    lnav is a terminal-based log viewer and analyzer designed for aggregating, filtering, and analyzing multiple log files in a single chronological view. It functions as a console application that can replace the system pager, providing syntax highlighting and document navigation for system or application logs. The project distinguishes itself by mapping unstructured log data to virtual SQLite tables, enabling the use of SQL and PRQL for structured data analysis, aggregations, and relational queries. It further differentiates its capability set through native integration for retrieving and taili

    C++command-line-toollesslog-analysis
    View on GitHub↗9,630
  • nlog/nlogNLog avatar

    NLog/NLog

    6,546View on GitHub↗

    NLog is an open-source logging framework for .NET that functions as a structured logging library and log routing engine. It captures log events with named parameters as searchable data rather than plain text and directs these messages to various output destinations based on severity and source. The framework is designed as an extensible platform, supporting custom targets, layout renderers, and filters that can be loaded from external assemblies or defined in code. It features a dynamic configuration system that allows logging targets, rules, and layouts to be updated via XML or programmatic

    C#aotaot-compatiblec-sharp
    View on GitHub↗6,546
  • klauscfhq/signaleklauscfhq avatar

    klauscfhq/signale

    9,176View on GitHub↗

    Signale is a formatted console logging library for Node.js applications. It serves as a pluggable logging framework and stream-based log router that allows users to record system events using customizable levels, colors, and output styles. The project distinguishes itself as an interactive console logger capable of overwriting previous messages to reduce terminal clutter during long-running tasks. It also functions as an application performance monitor, providing tools to measure and track execution time between specific code points to identify performance bottlenecks. The library covers a b

    JavaScript
    View on GitHub↗9,176
  • fluent/fluentdfluent avatar

    fluent/fluentd

    13,611View on GitHub↗

    Fluentd is a unified logging layer and distributed event router that collects, parses, and routes log data from diverse sources to various storage backends. It functions as a log forwarding agent and pipeline orchestrator, transforming raw unstructured log strings into formatted objects using structured log parsing. The project utilizes a plugin-based pipeline architecture to route data through independent input, filter, and output stages. It differentiates itself through tag-based event routing, which uses regular expression patterns to direct specific data streams to their intended destinat

    Ruby
    View on GitHub↗13,611
Compare all 30 related projects→