[−][src]Module emmett::inputs
Inputs define the sources of data flow.
Structs
| AzureEventHubs | This plugin consumes events from Azure Event Hubs, a highly scalable data streaming platform and event ingestion service. Event producers send events to the Azure Event Hub, and this plugin consumes those events for use with Logstash. |
| Beats | This input plugin enables Logstash to receive events from the Elastic Beats framework. |
| Cloudwatch | |
| CouchDbChanges | This CouchDB input allows you to automatically stream events from the CouchDB _changes URI. Moreover, any "future" changes will automatically be streamed as well making it easy to synchronize your CouchDB data with any target destination |
| DeadLetterQueue | Logstash input to read events from Logstash’s dead letter queue. |
| Elasticsearch | Read from an Elasticsearch cluster, based on search query results. This is useful for replaying test logs, reindexing, etc. You can periodically schedule ingestion using a cron syntax (see schedule setting) or run the query one time to load data into Logstash. |
| Exec | Periodically run a shell command and capture the whole output as an event. |
| File | Stream events from files, normally by tailing them in a manner similar to tail -0F but optionally reading them from the beginning. Normally, logging will add a newline to the end of each line written. By default, each event is assumed to be one line and a line is taken to be the text before a newline character. If you would like to join multiple log lines into one event, you’ll want to use the multiline codec. The plugin loops between discovering new files and processing each discovered file. Discovered files have a lifecycle, they start off in the "watched" or "ignored" state. Other states in the lifecycle are: "active", "closed" and "unwatched" By default, a window of 4095 files is used to limit the number of file handles in use. The processing phase has a number of stages: |
| Ganglia | Read ganglia packets from the network via UDP. |
| Gelf | This input will read GELF messages as events over the network, making it a good choice if you already use Graylog2 today. |
| Generator | Generate random log events. The general intention of this is to test performance of plugins. An event is generated first |
| Github | Read events from github webhooks. |
| GoogleCloudStorage | Extracts events from files in a Google Cloud Storage bucket. |
| GooglePubsub | The main motivation behind the development of this plugin was to ingest Stackdriver Logging messages via the Exported Logs feature of Stackdriver Logging. |
| Graphite | Receive graphite metrics. This plugin understands the text-based graphite carbon protocol. |
| Heartbeat | Generate heartbeat messages. The general intention of this is to test the performance and availability of Logstash. |
| Http | Using this input you can receive single or multiline events over http(s). Applications can send an HTTP request to the endpoint started by this input and Logstash will convert it into an event for subsequent processing. Users can pass plain text, JSON, or any formatted data and use a corresponding codec with this input. For Content-Type application/json the json codec is used, but for all other data formats, plain codec is used. |
| HttpPoller | This Logstash input plugin allows you to call an HTTP API, decode the output of it into event(s), and send them on their merry way. |
| Imap | Read mails from IMAP server. Periodically scan an IMAP folder (INBOX by default) and move any read messages to the trash. |
| InputBlock | A container of all Input plugins for a Pipeline. |
| Irc | Read events from an IRC Server. |
| Jdbc | This plugin was created as a way to ingest data in any database with a JDBC interface into Logstash. You can periodically schedule ingestion using a cron syntax (see schedule setting) or run the query one time to load data into Logstash. Each row in the resultset becomes a single event. Columns in the resultset are converted into fields in the event. |
| Jms | Read events from a Jms Broker. Supports both Jms Queues and Topics. |
| Jmx | This input plugin permits to retrieve metrics from remote Java applications using JMX. Every polling_frequency, it scans a folder containing json configuration files describing JVMs to monitor with metrics to retrieve. Then a pool of threads will retrieve metrics and create events. |
| Kafka | This input will read events from a Kafka topic. |
| Kinesis | You can use this plugin to receive events through AWS Kinesis |
| Lumberjack | Receive events using the Lumberjack protocol. |
| Meetup | Periodically query meetup.com regarding updates on events for the given Meetup key. |
| Pipe | Stream events from a long running command pipe. By default, each event is assumed to be one line. If you want to join lines, you’ll want to use the multiline codec. |
| PuppetFacter | Connects to a puppet server and requests facts. |
| RabbitMq | Pull events from a RabbitMQ queue. |
| Redis | This input will read events from a Redis instance; it supports both Redis channels and lists. |
| Relp | Read RELP events over a TCP socket. |
| Rss | |
| S3 | Stream events from files from a S3 bucket. Each line from each file generates an event. Files ending in .gz are handled as gzip’ed files. Files that are archived to AWS Glacier will be skipped. |
| Salesforce | |
| Snmp | |
| SnmpTrap | |
| Sqlite | |
| Sqs | Pull events from an Amazon Web Services Simple Queue Service (SQS) queue. |
| Stdin | Read events from standard input. By default, each event is assumed to be one line. If you want to join lines, you’ll want to use the multiline codec. |
| Stomp | Creates events received with the STOMP protocol. |
| Syslog | Read syslog messages as events over the network. |
| Tcp | Read events over a TCP socket. Like stdin and file inputs, each event is assumed to be one line of text. Can either accept connections from clients or connect to a server, depending on mode |
Ingest events from the Twitter Streaming API. | |
| Udp | Read messages as events over the network via udp. The only required configuration item is port, which specifies the udp port logstash will listen on for event streams. |
| Unix | Read events over a UNIX socket. Like stdin and file inputs, each event is assumed to be one line of text. Can either accept connections from clients or connect to a server, depending on mode. |
| Varnishlog | Read from varnish cache’s shared memory log. |
| Websocket | Read events over the websocket protocol. |
| Wmi | Collect data from WMI query. |
| Xmpp | This input allows you to receive events over XMPP/Jabber. This plugin can be used for accepting events from humans or applications XMPP, or you can use it for PubSub or general message passing for logstash to logstash. |
Enums
| Input | An Input plugin |