logstash-codec-protobuf 1.3.0-java

data/docs/index.asciidoc

@@ -0,0 +1,241 @@
+:plugin: protobuf
+:type: codec
+
+///////////////////////////////////////////
+START - GENERATED VARIABLES, DO NOT EDIT!
+///////////////////////////////////////////
+:version: %VERSION%
+:release_date: %RELEASE_DATE%
+:changelog_url: %CHANGELOG_URL%
+:include_path: ../../../../logstash/docs/include
+///////////////////////////////////////////
+END - GENERATED VARIABLES, DO NOT EDIT!
+///////////////////////////////////////////
+
+[id="plugins-{type}s-{plugin}"]
+
+=== Protobuf codec plugin
+
+include::{include_path}/plugin_header.asciidoc[]
+
+==== Description
+
+This codec converts protobuf encoded messages into logstash events and vice versa. It supports the protobuf versions 2 and 3.
+
+The plugin requires the protobuf definitions to be compiled to ruby files. +
+For protobuf 2 use the https://github.com/codekitchen/ruby-protocol-buffers[ruby-protoc compiler]. +
+For protobuf 3 use the https://developers.google.com/protocol-buffers/docs/reference/ruby-generated[official google protobuf compiler].
+
+The following shows a usage example (protobuf v2) for decoding events from a kafka stream:
+[source,ruby]
+kafka
+{
+  topic_id => "..."
+  key_deserializer_class => "org.apache.kafka.common.serialization.ByteArrayDeserializer"
+  value_deserializer_class => "org.apache.kafka.common.serialization.ByteArrayDeserializer"
+  codec => protobuf
+  {
+    class_name => "Animals::Mammals::Unicorn"
+    class_file => '/path/to/pb_definitions/some_folder/Unicorn.pb.rb'
+    protobuf_root_directory => "/path/to/pb_definitions/"
+  }
+}
+
+Decoder usage example for protobuf v3:
+[source,ruby]
+kafka
+{
+  topic_id => "..."
+  key_deserializer_class => "org.apache.kafka.common.serialization.ByteArrayDeserializer"
+  value_deserializer_class => "org.apache.kafka.common.serialization.ByteArrayDeserializer"
+  codec => protobuf
+  {
+    class_name => "Animals.Mammals.Unicorn"
+    class_file => '/path/to/pb_definitions/some_folder/Unicorn_pb.rb'
+    protobuf_root_directory => "/path/to/pb_definitions/"
+    protobuf_version => 3
+  }
+}
+
+
+The codec can be used in input and output plugins. +
+When using the codec in the kafka input plugin please set the deserializer classes as shown above. +
+When using the codec in an output plugin:
+
+* make sure to include all the desired fields in the protobuf definition, including timestamp.
+  Remove fields that are not part of the protobuf definition from the event by using the mutate filter. Encoding will fail if the event has fields which are not in the protobuf definition.
+* the `@` symbol is currently not supported in field names when loading the protobuf definitions for encoding. Make sure to call the timestamp field `timestamp`
+  instead of `@timestamp` in the protobuf file. Logstash event fields will be stripped of the leading `@` before conversion.
+* fields with a nil value will automatically be removed from the event. Empty fields will not be removed.
+* it is recommended to set the config option `pb3_encoder_autoconvert_types` to true. Otherwise any type mismatch between your data and the protobuf definition will cause an event to be lost. The auto typeconversion does not alter your data. It just tries to convert obviously identical data into the expected datatype, such as converting integers to floats where floats are expected, or "true" / "false" strings into booleans where booleans are expected.
+* When writing to Kafka: set the serializer class: `value_serializer => "org.apache.kafka.common.serialization.ByteArraySerializer"`
+
+Encoder usage example (protobufg v3):
+
+[source,ruby]
+kafka
+  {
+    codec => protobuf
+    {
+      class_name => "Animals.Mammals.Unicorn"
+      class_file => '/path/to/pb_definitions/some_folder/Unicorn_pb.rb'
+      protobuf_root_directory => "/path/to/pb_definitions/"
+      protobuf_version => 3
+    }
+    value_serializer => "org.apache.kafka.common.serialization.ByteArraySerializer"
+  }
+}
+
+
+[id="plugins-{type}s-{plugin}-options"]
+==== Protobuf Codec Configuration Options
+
+[cols="<,<,<",options="header",]
+|=======================================================================
+|Setting |Input type|Required
+| <<plugins-{type}s-{plugin}-class_name>> |<<string,string>>|Yes
+| <<plugins-{type}s-{plugin}-class_file>> |<<string,string>>|No
+| <<plugins-{type}s-{plugin}-protobuf_root_directory>> |<<string,string>>|No
+| <<plugins-{type}s-{plugin}-include_path>> |<<array,array>>|No
+| <<plugins-{type}s-{plugin}-protobuf_version>> |<<number,number>>|Yes
+| <<plugins-{type}s-{plugin}-stop_on_error>> |<<boolean,boolean>>|No
+| <<plugins-{type}s-{plugin}-pb3_encoder_autoconvert_types>> |<<boolean,boolean>>|No
+|=======================================================================
+
+&nbsp;
+
+[id="plugins-{type}s-{plugin}-class_name"]
+===== `class_name`
+
+  * This is a required setting.
+  * Value type is <<string,string>>
+  * There is no default value for this setting.
+
+Fully qualified name of the class to decode.
+Please note that the module delimiter is different depending on the protobuf version. For protobuf v2, use double colons:
+[source,ruby]
+class_name => "Animals::Mammals::Unicorn"
+
+For protobuf v3, use single dots:
+[source,ruby]
+class_name => "Animals.Mammals.Unicorn"
+
+For protobuf v3, you can copy the class name from the Descriptorpool registrations at the bottom of the generated protobuf ruby file. It contains lines like this:
+[source,ruby]
+Animals.Mammals.Unicorn = Google::Protobuf::DescriptorPool.generated_pool.lookup("Animals.Mammals.Unicorn").msgclass
+
+If your class references other definitions: you only have to add the name of the main class here.
+
+[id="plugins-{type}s-{plugin}-class_file"]
+===== `class_file`
+
+  * Value type is <<string,string>>
+  * There is no default value for this setting.
+
+Absolute path to the directory that contains all compiled protobuf files. If the protobuf definitions are spread across multiple folders, this needs to point to the folder containing all those folders.
+
+[id="plugins-{type}s-{plugin}-protobuf_root_directory"]
+===== `protobuf_root_directory`
+
+  * Value type is <<string,string>>
+  * There is no default value for this setting.
+
+Absolute path to the root directory that contains all referenced/used dependencies of the main class (`class_name`) or any of its dependencies. Must be used in combination with the `class_file` setting, and can not be used in combination with the legacy loading mechanism `include_path`.
+
+Example:
+
+[source]
+ pb3
+   ├── header
+   │   └── header_pb.rb
+   ├── messageA_pb.rb
+
+In this case `messageA_pb.rb` has an embedded message from `header/header_pb.rb`.
+If `class_file` is set to `messageA_pb.rb`, and `class_name` to `MessageA`, `protobuf_root_directory` must be set to `/path/to/pb3`, which includes both definitions.
+
+
+[id="plugins-{type}s-{plugin}-include_path"]
+===== `include_path`
+
+  * Value type is <<array,array>>
+  * There is no default value for this setting.
+
+Legacy protobuf definition loading mechanism for backwards compatibility:
+List of absolute pathes to files with protobuf definitions.
+When using more than one file, make sure to arrange the files in reverse order of dependency so that each class is loaded before it is
+refered to by another.
+
+Example: a class _Unicorn_ referencing another protobuf class _Wings_
+[source,ruby]
+module Animal
+  module Mammal
+    class Unicorn
+      set_fully_qualified_name "Animal.Mammal.Unicorn"
+      optional ::Bodypart::Wings, :wings, 1
+      optional :string, :name, 2
+      ...
+
+would be configured as
+[source,ruby]
+include_path => ['/path/to/pb_definitions/wings.pb.rb','/path/to/pb_definitions/unicorn.pb.rb']
+
+Please note that protobuf v2 files have the ending `.pb.rb` whereas files compiled for protobuf v3 end in `_pb.rb`.
+
+Cannot be used together with `protobuf_root_directory` or `class_file`.
+
+[id="plugins-{type}s-{plugin}-protobuf_version"]
+===== `protobuf_version`
+
+  * Value type is <<number,number>>
+  * Default value is 2
+
+Protocol buffers version. Valid settings are 2, 3.
+
+[id="plugins-{type}s-{plugin}-stop_on_error"]
+===== `stop_on_error`
+
+  * Value type is <<boolean,boolean>>
+  * Default value is false
+
+Stop entire pipeline when encountering a non decodable message.
+
+[id="plugins-{type}s-{plugin}-pb3_encoder_autoconvert_types"]
+===== `pb3_encoder_autoconvert_types`
+
+  * Value type is <<boolean,boolean>>
+  * Default value is true
+
+Convert data types to match the protobuf definition (if possible).
+The protobuf encoder library is very strict with regards to data types. Example: an event has an integer field but the protobuf definition expects a float. This would lead to an exception and the event would be lost.
+
+This feature tries to convert the datatypes to the expectations of the protobuf definitions, without modifying the data whatsoever. Examples of conversions it might attempt:
+
+  `"true" :: string => true :: boolean`
+
+  `17 :: int => 17.0 :: float`
+
+  `12345 :: number => "12345" :: string`
+
+Available only for protobuf version 3.
+
+[id="plugins-{type}s-{plugin}-pb3_set_oneof_metainfo"]
+===== `pb3_set_oneof_metainfo`
+
+  * Value type is <<boolean,boolean>>
+  * Default value is false
+
+Add meta information to `[@metadata][pb_oneof]` about which classes were chosen
+for https://developers.google.com/protocol-buffers/docs/proto3#oneof[oneof]
+fields. A new field of name `[@metadata][pb_oneof][FOO]` will be added, where
+`FOO` is the name of the `oneof` field.
+
+Example values: for the protobuf definition
+[source,ruby]
+    oneof :horse_type do
+      optional :unicorn, :message, 2, "UnicornType"
+      optional :pegasus, :message, 3, "PegasusType"
+    end
+
+the field `[@metadata][pb_oneof][horse_type]` will be set to either `pegasus` or `unicorn`.
+Available only for protobuf version 3.
+

data/google-protobuf-lib-update.md

@@ -0,0 +1,57 @@
+# Custom google protobuf library version
+
+At the time of this writing, the codec uses the [protoc library version 3.22.2](https://rubygems.org/gems/google-protobuf/versions/3.22.2-java).
+If you want to use a different protobuf library version then please follow these instructions on how to manually build the google-protobuf.gem.
+
+0.  Get the protobuf sources:
+```
+git clone https://github.com/protocolbuffers/protobuf.git;
+cd protobuf;
+git checkout $VERSION_YOU_WANT_TO_BUILD
+```
+
+1. Check your compiler version. It needs to be at least the version that you want to build for.
+`protoc --version`
+
+If your compiler is too old, build it from the repo:
+
+```
+git submodule update --init --recursive
+./autogen.sh
+./configure
+make
+make check
+sudo make install
+```
+
+(instructions taken from their [src/README.md](https://github.com/protocolbuffers/protobuf/blob/master/src/README.md) - check for updates in there!)
+
+2. Build the gem:
+`cd ruby; rake build && gem build *.gemspec`
+
+(Instructions taken from https://github.com/protocolbuffers/protobuf/issues/1594#issuecomment-258029377)
+
+3. Change the dependency in the protobuf codec:
+
+Step 3.a: clone this repo.
+`git clone git@github.com:logstash-plugins/logstash-codec-protobuf.git`
+
+Step 3.b: edit the dependency in [the gemspec](https://github.com/logstash-plugins/logstash-codec-protobuf/blob/master/logstash-codec-protobuf.gemspec#L23) to the version that you built in step 2.
+
+Step 3.c: set the [codec version in the gemspec](https://github.com/logstash-plugins/logstash-codec-protobuf/blob/master/logstash-codec-protobuf.gemspec#L4) to a number that is not available on rubygems.
+
+Step 3.d: build the codec. `rake build && gem build logstash-codec-protobuf.gemspec`
+
+
+4. Install both gems in your Logstash (in this order):
+```
+logstash-plugin install --no-verify google-protobuf-$PROTOBUF_GEM_VERSION-java.gem
+logstash-plugin install logstash-codec-protobuf-$PROTOBUF_INPUT_PLUGIN_VERSION.gem
+```
+
+# Notes
+
+We experimented with both the `>= ` and the `~>` operators in the dependency specification, such as
+` s.add_runtime_dependency 'google-protobuf', '>= 3.5.0.pre`
+but it would always lead to the ruby version of the protobuf gem to be pulled. Hints / PRs for pinning this to the Java/Jruby version would be appreciated and would render the steps in section 3 and parts of step 4 unnecessary.
+