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

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoAcerca deCómo clasificamosPrensaServidor MCP
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
gliderlabs avatar

gliderlabs/logspout

0
View on GitHub↗
4,694 estrellas·663 forks·Go·MIT·6 vistas

Logspout

Logspout es un agregador, reenviador y motor de enrutamiento de logs para contenedores, diseñado para recopilar registros de contenedores Docker y enviarlos a sistemas de registro centralizados externos. Funciona como una utilidad basada en red que redirige la salida de los contenedores a destinos remotos como syslog o endpoints TCP.

El sistema cuenta con un motor de enrutamiento dinámico que permite crear y actualizar configuraciones de enrutamiento de logs y filtros de destino en tiempo real a través de una interfaz HTTP, sin necesidad de reiniciar el servicio. Utiliza una arquitectura basada en adaptadores, lo que permite el desarrollo de módulos de salida personalizados y la creación de imágenes de contenedor adaptadas para soportar destinos propietarios.

La plataforma ofrece capacidades de filtrado de fuentes de logs basadas en nombres, IDs o etiquetas de contenedores, y admite el enrutamiento a múltiples destinos. Incluye utilidades de procesamiento de logs para la agregación multilínea y el formateo basado en plantillas para transformar la salida cruda en JSON estructurado o texto. La transmisión de datos está asegurada mediante cifrado TLS en la capa de transporte, con soporte para autenticación mutua y autoridades de certificación personalizadas.

La observabilidad adicional se proporciona mediante la transmisión de logs en tiempo real a través de WebSockets y codificación HTTP fragmentada, junto con la detección de tiempos de espera de flujo para evitar la pérdida de datos.

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.

Historial de estrellas

Gráfico del historial de estrellas de gliderlabs/logspoutGráfico del historial de estrellas de gliderlabs/logspout

Búsqueda con IA

Explora más repositorios increíbles

Describe lo que necesitas en lenguaje sencillo: la IA clasifica miles de proyectos open-source curados por relevancia.

Start searching with AI

Preguntas frecuentes

¿Qué hace gliderlabs/logspout?

Logspout es un agregador, reenviador y motor de enrutamiento de logs para contenedores, diseñado para recopilar registros de contenedores Docker y enviarlos a sistemas de registro centralizados externos. Funciona como una utilidad basada en red que redirige la salida de los contenedores a destinos remotos como syslog o endpoints TCP.

¿Cuáles son las características principales de gliderlabs/logspout?

Las características principales de gliderlabs/logspout son: 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.

¿Qué alternativas de código abierto existen para gliderlabs/logspout?

Las alternativas de código abierto para gliderlabs/logspout incluyen: 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…

Alternativas open-source a Logspout

Proyectos open-source similares, clasificados según cuántas características comparten con Logspout.
  • tstack/lnavAvatar de tstack

    tstack/lnav

    9,630Ver en 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
    Ver en GitHub↗9,630
  • nlog/nlogAvatar de NLog

    NLog/NLog

    6,542Ver en 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
    Ver en GitHub↗6,542
  • klauscfhq/signaleAvatar de klauscfhq

    klauscfhq/signale

    9,176Ver en 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
    Ver en GitHub↗9,176
  • fluent/fluentdAvatar de fluent

    fluent/fluentd

    13,554Ver en 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
    Ver en GitHub↗13,554
  • Ver las 30 alternativas a Logspout→