Comments (4)
This will generate a lot of warning messages for potentially no good reason. Since the elasticsearch output plugin now does automatic retries in the event of a send fail, I can see no good reason to get a warning every time this happens. Our current goals for Logstash 2.0 also involve a dead-letter queue, with separate notifications if things refuse to resend after n tries.
I'm not sure we need this feature in light of these things.
from logstash-output-elasticsearch.
Thanks, Aaron. Do you mean that the "warning" should be dropped? When is the "2.0" expected? Shouldn't we perhaps have that feature implemented in the meantime? I can't use the "1.5" plug-in generation unless the log level could be set to "error", for example.
Regards, Andrei
from logstash-output-elasticsearch.
Yes. I am implying that there should be no warning for retries because the current version of the plugin automatically retries on 429 and 503 messages.
Logstash 2.0 is a separate matter from retries and logging.
from logstash-output-elasticsearch.
Closing this. We've rehashed this with regards to retries several times over.
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.