Raw or Plaintext Inputs

Select this check box to enable the input on all Graylog nodes, or keep it unchecked to enable the input on a specific node.

The hostname or IP address of the message broker (e.g. RabbitMQ server).

The logical namespace within the broker used to separate applications or tenants.

The maximum number of messages a consumer can receive before acknowledging them.

The name of the queue from which messages will be consumed.

The exchange to which the input should bind in order to receive messages.

The key used by the exchange to route messages into the specified queue.

Defines how many consumers or queues should be created for message processing.

Enables message rate limiting to control ingestion speed and prevent system overload.

The port number used by the message broker.

The username for authenticating against the message broker, if required.

The password associated with the broker username for authentication.

Declares the queue in passive mode, ensuring it exists without modifying or creating it.

Binds the input to a specific exchange in the broker to receive messages from it.

Interval (in seconds) for client–broker heartbeat checks to detect lost connections.

Enable secure TLS for encrypted message transport (requires certificates). Select if this input should use TLS.

Determines whether invalid/unprocessable messages are placed back into the queue.

Time interval (in seconds) to wait before retrying a broker connection after failure.

Allows you to override the source field for all incoming messages.

Select this check box to enable the input on all Graylog nodes, or keep it unchecked to enable the input on a specific node.

Select this option to use the old ZooKeeper-based consumer API.

Minimum byte size a message batch should reach before fetching.

Enter the maximum time (in milliseconds) to wait before fetching.

Enter the number of threads to process. This setting is based on the number of partitions available for the topic.

Enables message rate limiting to control ingestion speed and prevent system overload.

Choose the appropriate selection from the drop-down menu if there is no initial offset in Kafka or if an offset is out of range.

The name of the consumer group the Kafka input belongs to.

This setting is used to determine the language of the message.

Select this option if the full field name should be used.

Select this check box to enable the input on all Graylog nodes, or keep it unchecked to enable the input on a specific node.

Enter a port to use in conjunction with the IP address.

This setting controls how many concurrent threads are used to process incoming data. Increasing the number of threads can enhance data processing speed, resulting in improved throughput. The ideal number of threads to configure depends on the available CPU cores on your Graylog server. A common starting point is to align the number of worker threads with the number of CPU cores. However, it is crucial to strike a balance with other server demands.

The certificate private key file that is stored on a Graylog system. The value of this field is a path (/path/to/file) that Graylog should have access to.

Select this option if this input should use TLS.

The private key password.

If you want to require authentication, set this value to optional or required.

The path where client (source) certificates are located on a Graylog system. The value of this field is a path (/path/to/file) that Graylog should have access to.

Enable this option if you want the input to support TCP keep-alive packets to prevent idle connections.

This option is typically left unchecked. Newline characters are the default message delimiter used when this box is left unchecked.

The maximum message size of the message. The default value should suffice but can be modified depending on message length. Each input type usually has specifications that note the maximum length of a message.