Example searches: “http://api.example.com”, “Get datafeeds”, “Create a behavioral analytics collection”, “Get CAT help”, “index”
Additional properties are allowed.
Description of the pipeline. This description is not used by Elasticsearch or Logstash.
A date and time, either as a string whose format can depend on the context (defaulting to ISO 8601), or a number of milliseconds since the Epoch. Elasticsearch accepts both as input, but will generally output a string representation.
Time unit for milliseconds
User who last updated the pipeline.
Configuration for the pipeline.
The number of workers that will, in parallel, execute the filter and output stages of the pipeline.
The maximum number of events an individual worker thread will collect from inputs before attempting to execute its filters and outputs.
When creating pipeline event batches, how long in milliseconds to wait for each event before dispatching an undersized batch to pipeline workers.
The internal queuing model to use for event buffering.
The total capacity of the queue (queue.type: persisted) in number of bytes.
queue.type: persisted
The total capacity of the queue (queue.type: persisted) in terms of units of bytes.
The maximum number of written events before forcing a checkpoint when persistent queues are enabled (queue.type: persisted).
curl \ -X GET http://api.example.com/_logstash/pipeline