Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. InfluxDB
  3. logagent

logagent

Apache-2.0JavaScript3.3.1

A lightweight, extensible log shipper with built-in parsing, buffering, and support for Elasticsearch and other destinations.

Visit WebsiteGitHubGitHub
391 stars78 forks0 contributors

What is logagent?

Logagent is an open-source, lightweight log shipper that collects, parses, and forwards log data to destinations like Elasticsearch and Sematext Logs. It combines the roles of log forwarding and processing into a single tool, addressing the need for efficient log management without the high resource consumption of traditional solutions. It is designed to handle structured and unstructured logs with extensible plugins and secure transport.

Target Audience

DevOps engineers, SREs, and developers who need a resource-efficient log shipper for environments like edge devices, containers, or servers where memory and CPU usage are critical.

Value Proposition

Developers choose Logagent for its low memory footprint and CPU overhead compared to JVM-based alternatives like Logstash, while still offering features like built-in parsing, buffering, and extensibility. It provides a streamlined, all-in-one solution that reduces operational complexity.

Overview

Extensible log shipper with input/output plugins, buffering, parsing, data masking, and small memory/CPU footprint

Use Cases

Best For

  • Shipping logs from edge devices with limited resources
  • Parsing and structuring unstructured log data on the fly
  • Self-hosting a lightweight log management pipeline
  • Replacing Logstash in environments where JVM overhead is prohibitive
  • Buffering logs locally to prevent data loss during network issues
  • Integrating logs with Elasticsearch or Sematext Logs efficiently

Not Ideal For

  • Projects requiring complex, multi-stage log transformations with heavy custom processing beyond built-in parsing
  • Teams deeply integrated with cloud-specific log services like AWS CloudWatch or Google Cloud Logging without custom plugins
  • Environments where graphical configuration interfaces are preferred over YAML file editing
  • High-throughput log ingestion scenarios where maximum performance outweighs resource efficiency priorities

Pros & Cons

Pros

Minimal Resource Usage

Optimized for low memory and CPU footprint, explicitly designed for edge devices and resource-constrained environments as highlighted in the README.

Built-in Log Parsing

Comes with out-of-the-box parsing to structure unstructured logs, reducing reliance on additional tools for common log formats.

Plugin Extensibility

Supports extensible input and output plugins, allowing customization for various log sources and destinations beyond the defaults.

Data Loss Prevention

Includes on-disk buffering to handle network interruptions, ensuring log durability during transmission failures as noted in the features.

Cons

Node.js Runtime Dependency

Requires Node.js installation, which can add complexity and maintenance overhead in environments not already using Node or with strict dependency controls.

Limited Native Integrations

Primarily focused on Elasticsearch and Sematext Logs, with fewer built-in outputs for other popular log management systems compared to tools like Fluentd or Logstash.

Configuration Overhead

Relies on YAML configuration files without a GUI, which may be less intuitive for users accustomed to visual tools or seeking quicker setup.

Open Source Alternative To

logagent is an open-source alternative to the following products:

Filebeat
Filebeat

Filebeat is a lightweight shipper for forwarding and centralizing log data, part of the Elastic Stack, that monitors log files or locations and sends them to Elasticsearch or Logstash.

Logstash
Logstash

Logstash is an open-source data processing pipeline that ingests data from multiple sources, transforms it, and sends it to a destination like Elasticsearch for storage and analysis.

Frequently Asked Questions

Quick Stats

Stars391
Forks78
Contributors0
Open Issues38
Last commit1 year ago
CreatedSince 2015

Tags

#devops#elk-stack#observability#logs#lightweight#monitoring#logging#nodejs#log-collector#docker#elk#log-management#javascript#node-js#log-parsing#elasticsearch

Built With

N
Node.js
D
Docker

Links & Resources

Website

Included in

InfluxDB817
Auto-fetched 5 hours ago

Related Projects

cAdvisorcAdvisor

Analyzes resource usage and performance characteristics of running containers.

Stars19,131
Forks2,464
Last commit2 days ago
gatlinggatling

Modern Load Testing as Code

Stars6,902
Forks1,209
Last commit5 days ago
HekaHeka

DEPRECATED: Data collection and processing made easy.

Stars3,402
Forks519
Last commit2 years ago
heapsterheapster

[EOL] Compute Resource Usage Analysis and Monitoring of Container Clusters

Stars2,639
Forks1,231
Last commit7 years ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub