reyesj2 eca2a4a9c8 Logstash consumer threads should match topic partition count ...

- Default is set to 3. If there are too many consumer threads it may lead to idle logstash worker threads and could require decreasing this value to saturate workers

Signed-off-by: reyesj2 <94730068+reyesj2@users.noreply.github.com>

2024-05-08 16:17:09 -04:00

..

etc

logstash jinja for ui

2023-05-04 13:07:07 -04:00

pipelines/config

Logstash consumer threads should match topic partition count

2024-05-08 16:17:09 -04:00

tools/sbin

remove so-logstash-get-unparsed, use so-redis-count instead

2023-07-07 09:52:21 -04:00

config.sls

Remove references to kafkanode

2024-04-11 15:32:00 -04:00

defaults.yaml

Reconfigure logstash Kafka input

2024-05-01 13:01:29 -04:00

disabled.sls

enable/disable logstash in ui

2023-05-10 11:16:03 -04:00

enabled.sls

Remove references to kafkanode

2024-04-11 15:32:00 -04:00

init.sls

disable logstash and redis if kafka enabled

2024-04-10 14:13:27 -04:00

map.jinja

create ES_LOGSTASH_NODES which removes heavynodes

2023-06-22 09:46:42 -04:00

soc_logstash.yaml

annotation updates for custom settings

2024-04-30 15:14:56 -04:00

sostatus.sls

enable/disable logstash in ui

2023-05-10 11:16:03 -04:00