puppet_facter

edit

This is a community-maintained plugin! It does not ship with Logstash by default, but it is easy to install by running bin/logstash-plugin install logstash-input-puppet_facter.

Connects to a puppet server and requests facts

 

Synopsis

edit

This plugin supports the following configuration options:

Required configuration options:

puppet_facter {
}

Available configuration options:

Setting Input type Required Default value

add_field

hash

No

{}

codec

codec

No

"plain"

environment

string

No

"production"

host

string

No

"0.0.0.0"

interval

number

No

600

port

number

No

8140

private_key

a valid filesystem path

No

public_key

a valid filesystem path

No

ssl

boolean

No

true

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.

environment

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

host

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

interval

edit
  • Value type is number
  • Default value is 600

port

edit
  • Value type is number
  • Default value is 8140

private_key

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

public_key

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

ssl

edit
  • Value type is boolean
  • Default value is true

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.