Elastic
Start free trial Contact Sales
Loading

Meetup input plugin

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

For other versions, see the Versioned plugin docs.

Installation

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

Getting help

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

Periodically query meetup.com regarding updates on events for the given Meetup key.

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

Setting Input type Required
eventstatus string No
groupid string No
interval number Yes
meetupkey string Yes
urlname string No
venueid string No
text string No

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

  • Value type is string.
  • Default value is "upcoming,past".

Event Status can be one of "upcoming", "past", or "upcoming,past". Default is "upcoming,past".

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

The Group ID, multiple may be specified seperated by commas. Must have one of urlname, venueid, groupid, text.

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

Interval to run the command. Value is in minutes.

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

Meetup Key, aka personal token.

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

URLName - the URL name ie ElasticSearch-Oklahoma-City. Must have one of urlname, venue_id, group_id, text.

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

The venue ID Must have one of urlname, venue_id, group_id, text.

text

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

A text string to search meetup events by. Must have one of urlname, venue_id, group_id, text.

These 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
  • Value type is hash
  • Default value is {}

Add a field to an event

  • 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.

  • 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 meetup inputs. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

input {
  meetup {
    id => "my_plugin_id"
  }
}
Note

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

  • 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.

  • 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.