Busabase
Busabase is an open-source (MIT) database and workspace for AI agents — data, docs, skills, and apps in one place. Run it locally, self-host it inside your network, or use Busabase Cloud, and turn age
翻訳待ち
Logstash (part of the Elastic Stack) integrates data from any source, in any format with this flexible, open source collection, parsing, and enrichment pipeline. Download for free.
翻訳待ち
データJava · RubyGitHub @elasticオンライン所有者未確認
Have you tried it? One tap is enough. No sign-in needed.
Logstash - transport and process your logs, events, or other data
翻訳待ち
Loading the full README.
Read the full README ↗Logstash is part of the Elastic Stack along with Beats, Elasticsearch and Kibana. Logstash is a server-side data processing pipeline that ingests data from a multitude of sources simultaneously, transforms it, and then sends it to your favorite "stash." (Ours is Elasticsearch, naturally.). Logstash has over 200 plugins, and you can write your own very easily as well.
For more info, see https://www.elastic.co/products/logstash
You can find the documentation and getting started guides for Logstash on the elastic.co site
For information about building the documentation, see the README in https://github.com/elastic/docs
You can download officially released Logstash binaries, as well as debian/rpm packages for the supported platforms, from downloads page.
Logstash plugins are hosted in separate repositories under the logstash-plugins github organization. Each plugin is a self-contained Ruby gem which gets published to RubyGems.org.
Logstash is known for its extensibility. There are hundreds of plugins for Logstash and you can write your own very easily! For more info on developing and testing these plugins, please see the working with plugins section
Please open new issues and pull requests for plugins under its own repository
For example, if you have to report an issue/enhancement for the Elasticsearch output, please do so here.
Logstash core will continue to exist under this repository and all related issues and pull requests can be submitted here.
JAVA_HOME environment variable to the path to your JDK installation directory. For example set JAVA_HOME=<JDK_PATH>versions.yml (currently 10.0.7.0); no separate JRuby installation is required.rake and bundler tool using gem install rake and gem install bundler respectively.If you prefer to use rvm (ruby version manager) to manage Ruby versions on your machine, follow these directions. In the Logstash folder:
gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
\curl -sSL https://get.rvm.io | bash -s stable --ruby=$(cat .ruby-version)
Before you proceed, please check your ruby version by:
$ ruby -v
The printed version should be the same as in the .ruby-version file.
The Logstash project includes the source code for all of Logstash, including the Elastic-Licensed X-Pack features and functions; to run Logstash from source using only the OSS-licensed code, export the OSS environment variable with a value of true:
export OSS=true
export LOGSTASH_SOURCE=1
export LOGSTASH_PATH=/YOUR/LOGSTASH/DIRECTORY
gradle (recommended)1./gradlew installDevelopmentGems
./gradlew installDefaultGems
To verify your environment, run the following to start Logstash and send your first event:
bin/logstash -e 'input { stdin { } } output { stdout {} }'
This should start Logstash with stdin input waiting for you to enter an event
hello world
2016-11-11T01:22:14.405+0000 0.0.0.0 hello world
Advanced: Drip Launcher
Drip is a tool that solves the slow JVM startup problem while developing Logstash. The drip script is intended to be a drop-in replacement for the java command. We recommend using drip during development, in particular for running tests. Using drip, the first invocation of a command will not be faster but the subsequent commands will be swift.
To tell logstash to use drip, set the environment variable JAVACMD=`which drip`.
Example (but see the Testing section below before running rspec for the first time):
JAVACMD=`which drip` bin/rspec
Caveats
Drip does not work with STDIN. You cannot use drip for running configs which use the stdin plugin.
To build the Logstash Reference (open source content only) on your local machine, clone the following repos:
logstash - contains main docs about core features
logstash-docs - contains generated plugin docs
docs - contains doc build files
Make sure you have the same branch checked out in logstash and logstash-docs.
Check out master in the docs repo.
Run the doc build script from within the docs repo. For example:
./build_docs.pl --doc ../logstash/docs/index.asciidoc --chunk=1 -open
Most of the unit tests in Logstash are written using rspec for the Ruby parts. For the Java parts, we use junit. For testing you can use the test rake tasks and the bin/rspec command, see instructions below:
1- To run the core tests you can use the Gradle task:
./gradlew test
or use the rspec tool to run all tests or run a specific test:
This is the beginning of the README. Read the rest at the original. Read the full README ↗