:plugin: twitter
:type: input
:default_codec: plain
///////////////////////////////////////////
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}"]
=== Twitter input plugin
include::{include_path}/plugin_header.asciidoc[]
==== Description
Ingest events from the Twitter Streaming API.
Example:
[source,ruby]
input {
twitter {
consumer_key => '...'
consumer_secret => '...'
oauth_token => '...'
oauth_token_secret => '...'
keywords => [ 'logstash' ]
}
}
Sample event fields generated:
[source,ruby]
-----
{
"@timestamp" => 2019-09-23T16:41:53.000Z,
"message" => "I forgot how fun it is to write @logstash configs !!! Thank you @jordansissel and @elastic !!!"
"user" => "missnebun",
"in-reply-to" => nil,
"retweeted" => false,
"source" => "http://twitter.com/missnebun/status/1176174859833004037",
"user_mentions" => [
{ "screen_name"=>"logstash", "name"=>"logstash", "id"=>217155915 },
{ "screen_name"=>"jordansissel", "name"=>"@jordansissel", "id"=>15782607 },
{ "screen_name"=>"elastic", "name"=>"Elastic", "id"=>84512601 }],
"symbols" => [],
"hashtags" => [],
"client" => "Twitter for iPhone"
}
-----
[id="plugins-{type}s-{plugin}-ecs"]
==== Compatibility with the Elastic Common Schema (ECS)
Twitter streams are very specific and do not map easily to the {ecs-ref}[Elastic Common Schema (ECS)].
We recommend setting a <> when <> is enabled.
The plugin issues a warning in the log when a `target` isn't set.
[id="plugins-{type}s-{plugin}-options"]
==== Twitter Input Configuration Options
This plugin supports the following configuration options plus the <> described later.
[cols="<,<,<",options="header",]
|=======================================================================
|Setting |Input type|Required
| <> |<>|Yes
| <> |<>|Yes
| <> |<>|No
| <> |<>|No
| <> |<>|No
| <> |<>|No
| <> |<>|No
| <> |<>|No
| <> |<>|No
| <> |<>|Yes
| <> |<>|Yes
| <> |<>|No
| <> |<>|No
| <> |<>|No
| <> |<>|No
| <> |<>|No
| <> |<>|No
|=======================================================================
Also see <> for a list of options supported by all
input plugins.
[id="plugins-{type}s-{plugin}-consumer_key"]
===== `consumer_key`
* This is a required setting.
* Value type is <>
* There is no default value for this setting.
Your Twitter App's consumer key
Don't know what this is? You need to create an "application"
on Twitter, see this url:
[id="plugins-{type}s-{plugin}-consumer_secret"]
===== `consumer_secret`
* This is a required setting.
* Value type is <>
* There is no default value for this setting.
Your Twitter App's consumer secret
If you don't have one of these, you can create one by
registering a new application with Twitter:
[id="plugins-{type}s-{plugin}-ecs_compatibility"]
===== `ecs_compatibility`
* Value type is <>
* Supported values are:
** `disabled`: does not use ECS-compatible field names (fields might be set at the root of the event)
** `v1`, `v8`: avoids field names that might conflict with Elastic Common Schema (for example, Twitter specific properties)
* Default value depends on which version of Logstash is running:
** When Logstash provides a `pipeline.ecs_compatibility` setting, its value is used as the default
** Otherwise, the default value is `disabled`.
Controls this plugin's compatibility with the {ecs-ref}[Elastic Common Schema (ECS)].
[id="plugins-{type}s-{plugin}-follows"]
===== `follows`
* Value type is <>
* There is no default value for this setting.
A comma separated list of user IDs, indicating the users to
return statuses for in the Twitter stream.
See https://developer.twitter.com/en/docs/tweets/filter-realtime/guides/basic-stream-parameters
for more details.
[id="plugins-{type}s-{plugin}-full_tweet"]
===== `full_tweet`
* Value type is <>
* Default value is `false`
Record full tweet object as given to us by the Twitter Streaming API.
[id="plugins-{type}s-{plugin}-ignore_retweets"]
===== `ignore_retweets`
* Value type is <>
* Default value is `false`
Lets you ignore the retweets coming out of the Twitter API. Default => false
[id="plugins-{type}s-{plugin}-keywords"]
===== `keywords`
* Value type is <>
* There is no default value for this setting.
Any keywords to track in the Twitter stream. For multiple keywords, use
the syntax ["foo", "bar"]. There's a logical OR between each keyword
string listed and a logical AND between words separated by spaces per
keyword string.
See https://dev.twitter.com/streaming/overview/request-parameters#track
for more details.
The wildcard "*" option is not supported. To ingest a sample stream of
all tweets, the use_samples option is recommended.
[id="plugins-{type}s-{plugin}-languages"]
===== `languages`
* Value type is <>
* There is no default value for this setting.
A list of BCP 47 language identifiers corresponding to any of the languages listed
on Twitter’s advanced search page will only return tweets that have been detected
as being written in the specified languages.
[id="plugins-{type}s-{plugin}-locations"]
===== `locations`
* Value type is <>
* There is no default value for this setting.
A comma-separated list of longitude, latitude pairs specifying a set
of bounding boxes to filter tweets by.
See https://dev.twitter.com/streaming/overview/request-parameters#locations
for more details.
[id="plugins-{type}s-{plugin}-oauth_token"]
===== `oauth_token`
* This is a required setting.
* Value type is <>
* There is no default value for this setting.
Your oauth token.
To get this, login to Twitter with whatever account you want,
then visit
Click on your app (used with the consumer_key and consumer_secret settings)
Then at the bottom of the page, click 'Create my access token' which
will create an oauth token and secret bound to your account and that
application.
[id="plugins-{type}s-{plugin}-oauth_token_secret"]
===== `oauth_token_secret`
* This is a required setting.
* Value type is <>
* There is no default value for this setting.
Your oauth token secret.
To get this, login to Twitter with whatever account you want,
then visit
Click on your app (used with the consumer_key and consumer_secret settings)
Then at the bottom of the page, click 'Create my access token' which
will create an oauth token and secret bound to your account and that
application.
[id="plugins-{type}s-{plugin}-proxy_address"]
===== `proxy_address`
* Value type is <>
* Default value is `"127.0.0.1"`
Location of the proxy, by default the same machine as the one running this LS instance
[id="plugins-{type}s-{plugin}-proxy_port"]
===== `proxy_port`
* Value type is <>
* Default value is `3128`
Port where the proxy is listening, by default 3128 (squid)
[id="plugins-{type}s-{plugin}-rate_limit_reset_in"]
===== `rate_limit_reset_in`
* Value type is <>
* Default value is `300`
Duration in seconds to wait before retrying a connection when twitter responds with a 429 TooManyRequests
In some cases the 'x-rate-limit-reset' header is not set in the response and .rate_limit.reset_in
is nil. If this occurs then we use the integer specified here. The default is 5 minutes.
[id="plugins-{type}s-{plugin}-use_proxy"]
===== `use_proxy`
* Value type is <>
* Default value is `false`
When to use a proxy to handle the connections
[id="plugins-{type}s-{plugin}-use_samples"]
===== `use_samples`
* Value type is <>
* Default value is `false`
Returns a small random sample of all public statuses. The tweets returned
by the default access level are the same, so if two different clients connect
to this endpoint, they will see the same tweets. If set to true, the keywords,
follows, locations, and languages options will be ignored. Default => false
[id="plugins-{type}s-{plugin}-target"]
===== `target`
* Value type is <>
* There is no default value for this setting.
Without a `target`, events are created from tweets at the root level.
When the `target` is set to a field reference, the tweet data is placed in the target field instead.
This option can be useful to avoid populating unknown fields when a downstream schema such as ECS is enforced.
[id="plugins-{type}s-{plugin}-common-options"]
include::{include_path}/{type}.asciidoc[]
:default_codec!: