#Flume pro license code archive#
#Flume pro license code free#

native - any required native libraries, such as.libext - the plugin’s dependency jar(s).Creating the custom plugin directoryĮach plugin (subdirectory) within plugins.d can have up to three sub-directories: NOTE: The plugin directory can also be defined when executing the flume-ng command with the -plugins-path parameter. At startup time, the flume-ng start script looks in the plugins.d directory for plugins that conform to the below format and includes them in proper paths when starting up java. The plugins.d directory is located at $FLUME_HOME/plugins.d. This allows for easier management of plugin packaging issues as well as simpler debugging and troubleshooting of several classes of issues, especially library dependency conflicts. While it has always been possible to include custom Flume components by adding their jars to the FLUME_CLASSPATH variable in the flume-env.sh file, Flume now supports a special directory called plugins.d which automatically picks up plugins that are packaged in a specific format. While Flume ships with many out-of-the-box sources, channels, sinks, serializers, and the like, many implementations exist which ship separately from Flume. Installing third-party libraries for Apache Flumeįlume has a fully plugin-based architecture. NOTE: The latest instructions on this can be found here. Before this source library can be found by Apache Flume it must be added to the Flume plugins directory. This project uses Apache Maven to build so simply running mvn package should be enough to get a library jar. See Using HTTP cookies below for an example.Įxamples Get Single Echo Response from Įxport PLUGINS_DIRECTORY= $(pwd )/plugins.d 2 A cookie.* name/value will only be included if the subparameter key is listed in cookies.1 sslEnabled must be set to true for wss:// protocol usage.The keys are not the cookie name, but just define the property key containing the name & value for the cookie. Typically this is used for authentication or subscribing to a message channel.Ĭomma-delimited list of keys in cookie array. List of valid values can be found for Java 8 at: Java Cryptography Architecture Standard Algorithm Name Documentation for JDK 8#KeyStoreĪfter a successful connection, the websocket client will send this message to the remote endpoint. Java KeyStore type used to hold trusted certificates. If enabled there is a risk of a man-in-the-middle attack and should be used for development purposed only. Duration is in seconds.ĭetermine if client should trust ALL TLS certificate authorities including self-signed certificates. On an unexpected websocket closure, determine how quickly the client should poll attempting to reestablish connection. URL endpoint for websocket to establish connection.Ĭonfigure if TLS/SSL encryption should be used on the socket. Automatically reconnects after a customizable delay.Ĭonfigurable nf Source Properties Property.Provides a capability to send a message to a websocket data channel on connection.Connects to plain text ws:// or secure wss:// endpoints.This library was built to provide the following features: Pursuit to build cool things with less effort. Unfortunately at the time I couldn't find a plugin library that does everything I wanted so I built this one myself.

The capabilities of Flume make it a perfect receiver for websocket messages. It uses a simple extensible data model that allows for online analytic application. It is robust and fault tolerant with tunable reliability mechanisms and many failover and recovery mechanisms. It has a simple and flexible architecture based on streaming data flows. Overviewįlume is a distributed, reliable, and available service for efficiently collecting, aggregating, and moving large amounts of log data.

#Flume pro license code free#

If something is broken or you'd like to see a feature, feel free to leave an issue and I'll take a look.

#Flume pro license code archive#

Hi there! I've mostly put this up to archive work which can possibly be reused by others.