Irc input plugin

edit
  • Plugin version: v3.0.7
  • Released on: 2018-04-06
  • Changelog

For other versions, see the Versioned plugin docs.

Installation

edit

For plugins not bundled by default, it is easy to install by running bin/logstash-plugin install logstash-input-irc. See Working with plugins for more details.

Getting Help

edit

For questions about the plugin, open a topic in the Discuss forums. For bugs or feature requests, open an issue in Github. For the list of Elastic supported plugins, please consult the Elastic Support Matrix.

Description

edit

Read events from an IRC Server.

Irc Input Configuration Options

edit

This plugin supports the following configuration options plus the Common Options described later.

Also see Common Options for a list of options supported by all input plugins.

 

catch_all

edit
  • Value type is boolean
  • Default value is false

Catch all IRC channel/user events not just channel messages

channels

edit
  • This is a required setting.
  • Value type is array
  • There is no default value for this setting.

Channels to join and read messages from.

These should be full channel names including the # symbol, such as "#logstash".

For passworded channels, add a space and the channel password, such as "#logstash password".

get_stats

edit
  • Value type is boolean
  • Default value is false

Gather and send user counts for channels - this requires catch_all and will force it

host

edit
  • This is a required setting.
  • Value type is string
  • There is no default value for this setting.

Host of the IRC Server to connect to.

nick

edit
  • Value type is string
  • Default value is "logstash"

IRC Nickname

password

edit
  • Value type is password
  • There is no default value for this setting.

IRC Server password

port

edit
  • Value type is number
  • Default value is 6667

Port for the IRC Server

real

edit
  • Value type is string
  • Default value is "logstash"

IRC Real name

secure

edit
  • Value type is boolean
  • Default value is false

Set this to true to enable SSL.

stats_interval

edit
  • Value type is number
  • Default value is 5

How often in minutes to get the user count stats

user

edit
  • Value type is string
  • Default value is "logstash"

IRC Username

Common Options

edit

The following configuration options are supported by all input plugins:

Setting Input type Required

add_field

hash

No

codec

codec

No

enable_metric

boolean

No

id

string

No

tags

array

No

type

string

No

Details

edit

 

add_field

edit
  • Value type is hash
  • Default value is {}

Add a field to an event

codec

edit
  • Value type is codec
  • Default value is "plain"

The codec used for input data. Input codecs are a convenient method for decoding your data before it enters the input, without needing a separate filter in your Logstash pipeline.

enable_metric

edit
  • Value type is boolean
  • Default value is true

Disable or enable metric logging for this specific plugin instance by default we record all the metrics we can, but you can disable metrics collection for a specific plugin.

  • Value type is string
  • There is no default value for this setting.

Add a unique ID to the plugin configuration. If no ID is specified, Logstash will generate one. It is strongly recommended to set this ID in your configuration. This is particularly useful when you have two or more plugins of the same type, for example, if you have 2 irc inputs. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

input {
  irc {
    id => "my_plugin_id"
  }
}

Variable substitution in the id field only supports environment variables and does not support the use of values from the secret store.

tags

edit
  • Value type is array
  • There is no default value for this setting.

Add any number of arbitrary tags to your event.

This can help with processing later.

type

edit
  • Value type is string
  • There is no default value for this setting.

Add a type field to all events handled by this input.

Types are used mainly for filter activation.

The type is stored as part of the event itself, so you can also use the type to search for it in Kibana.

If you try to set a type on an event that already has one (for example when you send an event from a shipper to an indexer) then a new input will not override the existing type. A type set at the shipper stays with that event for its life even when sent to another Logstash server.