AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Logstash devutils12/24/2023 If you make your plugin publicly available via RubyGems. Logstash and all its plugins are licensed under S.licenses and s.version are also important and will come into play when For instance, in Active Directory, the default container for User objects is cnUsers. S.name and s.summary should reflect your plugin’s name and behavior. These containers hold objects that have some relation to each other as defined by the namespace. It is appropriate to change these values to fit your plugin. S.add_development_dependency 'logstash-devutils' S.description = "This gem is a logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. S.summary = "This output does x, y, z in Logstash" The idea is to provide an informed upgrade path to users who are still using a now-removed setting. :obsolete - used to declare that a given setting has been removed and is no longer functioning.:deprecated - informational (also a Boolean true or false).Note that this mostly obviates the array type, though if you need lists of complex objects that will be more suitable. Will typecheck the list members, and convert scalars to one element lists. :list - whether or not this value should be a list of values.:required - whether or not this parameter is mandatory (a Boolean true or.:default - lets you specify a default value for a parameter.:number type as well where "1.2" becomes a float and "22" is an integer. Will become a valid boolean in the config. In that if I specify "true" for boolean (even though technically a string), it :number, :array, :hash, :path (a file-system path), uri, :codec (sinceġ.2.0), :bytes. :validate - allows you to enforce passing a particular data type to Logstashįor this configuration option, such as :string, :password, :boolean,.# Must be threadsafe if `concurrency :shared` is set # will only be executed in a single thread # Only the `#multi_receive/#multi_receive_encoded` methods need to actually be threadsafe, the other methods # concurrency but you will need to make appropriate uses of mutexes in `#multi_receive/#receive`. # You can set this to :shared if your output is threadsafe. only one thread will be active at a time making threadsafety much simpler. Access to the `#multi_receive/#multi_receive_encoded/#receive` method will be synchronized # When configured as :single a single instance of the Output will be shared among the # You should explicitly set it to either :single or :shared as :legacy will be removed in Logstash 6.0 # way concurrency worked before Logstash 2.4 By default it is :legacy, which was the standard # This sets the concurrency behavior of this plugin. # Add any asciidoc formatted documentation hereĬlass LogStash::Outputs::Example < LogStash::Outputs::Base
0 Comments
Read More
Leave a Reply. |