Comments (1)
@pickypg thanks for the report, this seems to be an issue with logstash itself.
using a simple input { generator { count => 1 } } output { stdout { workers => 2} }
config yields:
bin/logstash -f config
You are using a deprecated config setting "type" set in stdout. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. You can achieve this same behavior with the new conditionals, like: `if [type] == "sometype" { stdout { ... } }`. If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=>"type", :plugin=><LogStash::Outputs::Stdout --->, :level=>:warn}
Logstash startup completed
You are using a deprecated config setting "tags" set in stdout. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. You can achieve similar behavior with the new conditionals, like: `if "sometag" in [tags] { stdout { ... } }` If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=>"tags", :plugin=><LogStash::Outputs::Stdout --->, :level=>:warn}
You are using a deprecated config setting "exclude_tags" set in stdout. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. You can achieve similar behavior with the new conditionals, like: `if !("sometag" in [tags]) { stdout { ... } }` If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=>"exclude_tags", :plugin=><LogStash::Outputs::Stdout --->, :level=>:warn}
You are using a deprecated config setting "type" set in stdout. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. You can achieve this same behavior with the new conditionals, like: `if [type] == "sometype" { stdout { ... } }`. If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=>"type", :plugin=><LogStash::Outputs::Stdout --->, :level=>:warn}
You are using a deprecated config setting "tags" set in stdout. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. You can achieve similar behavior with the new conditionals, like: `if "sometag" in [tags] { stdout { ... } }` If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=>"tags", :plugin=><LogStash::Outputs::Stdout --->, :level=>:warn}
You are using a deprecated config setting "exclude_tags" set in stdout. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. You can achieve similar behavior with the new conditionals, like: `if !("sometag" in [tags]) { stdout { ... } }` If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=>"exclude_tags", :plugin=><LogStash::Outputs::Stdout --->, :level=>:warn}
Logstash shutdown completed
Exception: Exception
I'm going to reopen the initial issue and close this one.
from logstash-output-elasticsearch.
Related Issues (20)
- normalized SSL config not applied when LS core uses private-API build_client directly
- Unify the error behaviour for template installation and ilm
- Doc: Update docs to call out differences from standard offering
- Allow the creation of custom data streams HOT 1
- Reduce ES response size through use of filter_path HOT 3
- Use integration's metadata fields (id, index, pipeline) when present
- Use integration's metadata fields (_routing, _version, _version_type) when present
- New management of `version` and `version_type` corrupt datastreams processing
- Isolate datastream vs normal indexing decision into test fixture
- Plugin fails with permission denied error HOT 1
- Cannot bundle install due to gemspec deps HOT 1
- Doc: Update data streams info to explain implications of ECS settings
- Handling non UTF-8 data.
- Default values of `http_compression` and `compression_level` are incosistent HOT 2
- Determine if `data_streams => true` can be possible with ECS compatibility effectively disabled
- Doc: Expand `silence_errors_in_log` description to show possible values
- SSL settings changed and not documented HOT 1
- Too large payload responses (413) are not being properly handled
- [CI] integration tests fail with PKIX path validation failed
- [Doc] clarify the acceptable format of ssl_key
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from logstash-output-elasticsearch.