logstash-codec-json
logstash-codec-json copied to clipboard
logstash-plugins
This codec is a privileged position to avoid the creation of huge events from arbitrarily large json documents. Although the string itself has been alocated, if this codec had a...
Hi, Facing problem (upgrading from 1.4.2 to 2.0 that occurs when field have brackets inside (valid JSON) example: { "dynamo_entry_tuple_in_list[0]_list[0]": "valid-value" } is converted to: { "dynamo_entry_tuple_in_list" : {"0_.list":{"1_":null,"0_":null}} }...
Exception Info: Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"Java::JavaLang::IllegalStateException", :message=>"Unable to configure plugins: java.lang.IllegalStateException: Setting value for 'codec' of type 'class org.jruby.gen.RubyObject20' incompatible with defined type of 'interface co.elastic.logstash.api.Codec'", :backtrace=>["org.logstash.config.ir.CompiledPipeline.(CompiledPipeline.java:119)", "org.logstash.execution.JavaBasePipelineExt.initialize(JavaBasePipelineExt.java:86)",...
before https://github.com/logstash-plugins/logstash-codec-json/pull/37 there were 2 error handlers: ```ruby rescue LogStash::Json::ParserError => e @logger.info("JSON parse failure. Falling back to plain-text", :error => e, :data => json) yield LogStash::Event.new("message" => json, "tags"...
We are using JSON codec with Fluent-Bit, EKS and Kinesis. Unfortunately due to lack of compression usage of Kinesis is very high. Would it be possible to add support for...
Trying to generalize the on-going work about mapping in the http output, it can be expected that an output require a specific JSON payload and cannot be satisfied by the...
Some clever ways of generating JSON are observed in nginx and apache httpd configs by using the log formatting function of these webservers to write json instead of plain text....
Description: The logstash 'json' plugin still requires a newline '\n' to terminate json logs being sent over a TCP input. (UDP appears to work fine) This is contradictory to the...
The codec should not accept this input: ``` { "hello": "world" }{ "goodbye": "moon" } ``` The above is two json objects that, alone, are valid, but combined, are not....
(This issue was originally filed by @german23 at https://github.com/elastic/logstash/issues/1857) --- Hi, i just encoutered a small bug regarding the json codec. The default charset for this is "UTF-8" but regarding...