- Notifications
You must be signed in to change notification settings - Fork78
Extensible log shipper with input/output plugins, buffering, parsing, data masking, and small memory/CPU footprint
License
sematext/logagent-js
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
Logagent is a modern, open-source, light-weight log shipper. It is like Filebeat and Logstash in one, without the JVM memory footprint. It comes with out of the box and extensible log parsing, on-disk buffering, secure transport, and bulk indexing to Elasticsearch,Sematext Logs, and other destinations. Its low memory footprint and low CPU overhead make it suitable for deploying on edge nodes and devices, while its ability to parse and structure logs makes it a great Logstash alternative.
Details about the the Logagent Docker image are described in theDocker Hub Readme
1) Install Node.js
Official Node.jsdownloads and instructions. E.g. for Debian/Ubuntu:
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -sudo apt-get install -y nodejsInstall Logagent with npmsudo npm i -g @sematext/logagent2) Run logagent command line tool
logagent --help3) Example: Index your log files in Elasticsearch
logagent -e http://localhost:9200 -i logs -g ‘/var/log/**/*.log’4) Optional: Install service & config
Install service for Logagent using systemd, upstart, launchdTo quickly create a config file for indexing into Elasticsearch without having to edit it run something like this:
sudo logagent-setup -u http://localhost:9200 -i INDEX_NAME -g '/var/log/**/*.log'# Logsene US: use -u https://logsene-receiver.sematext.com and your Logsene App Token as index name.# Logsene EU: use -u https://logsene-receiver.eu.sematext.com and your Logsene App Token as index name.Configuration
To configure different inputs, different event processing, or different outputs (e.g. your own Elasticsearch) edit /etc/sematext/logagent.conf, e.g.:
output: logsene: module: elasticsearch url: http://elasticsearch-server:9200 index: logsThen restart the service with sudo service logagent restart.Troubleshooting & LogsLogagent’s own logs:
- Upstart:
/var/log/upstart/logagent.log - Systemd:
journalctl -u logagent - Launchd:
/Library/Logs/logagent.log
Location of service scripts:
- Upstart:
/etc/init/logagent.conf - Systemd:
/etc/systemd/system/logagent.service - Launchd:
/Library/LaunchDaemons/com.sematext.logagent.plist
Start/stop service:
- Upstart:
service logagent stop/start - Systemd:
systemctl stop/start logagent - Launchd:
launchctl start/stop com.sematext.logagent
- Full documentation
- Logagent main page
- Logagent on Github
- Forum:https://groups.google.com/forum/#!forum/logagent
- Twitter:@sematext
- Blog:sematext.com/blog
- Update to the last node version
- From root folder node type: node ./bin/logagent -h
- To test from root folder type: node test
About
Extensible log shipper with input/output plugins, buffering, parsing, data masking, and small memory/CPU footprint
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Packages0
Uh oh!
There was an error while loading.Please reload this page.

