system-config/modules/openstack_project/files/logstash/logstash-worker3/jenkins-log-pusher.yaml
Clark Boylan 5bbe7824e0 Scale out logstash indexing to multiple hosts.
Logstash performs filtering in a single thread so it does not scale up
very well. Work around this by scaling Logstash out to multiple indexer
hosts.

Current plan is to have a small (2GB) kibana web front end host that
does nothing but talk to elasticsearch, three 4GB logstash indexers that
will run a single log-pusher.py + logstash indexer with some partition
of the logfiles assigned to each indexer, and finally the existing large
elasticsearch node.

Eventually properly load balancing log processing across the worker
nodes would be great, but the current partition method should work well
enough with little additional effort.

Change-Id: Ifc6396560934314ffd6a7c47eb2acff9e9c2a7af
Reviewed-on: https://review.openstack.org/30573
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Tested-by: Jenkins
2013-05-29 00:33:36 +00:00

43 lines
797 B
YAML

# Defaults
source-defaults:
source-url: http://logs.openstack.org
output-host: localhost
output-port: 9999
output-mode: tcp
retry-get: False
# List of zmq event inputs.
zmq-publishers:
- tcp://jenkins.openstack.org:8888
# List of files to source logs from.
source-files:
- name: logs/screen-g-api.txt
tags:
- screen
- oslofmt
- name: logs/screen-g-reg.txt
tags:
- screen
- oslofmt
- name: logs/screen-q-agt.txt
tags:
- screen
- oslofmt
- name: logs/screen-q-dhcp.txt
tags:
- screen
- oslofmt
- name: logs/screen-q-l3.txt
tags:
- screen
- oslofmt
- name: logs/screen-q-meta.txt
tags:
- screen
- oslofmt
- name: logs/screen-q-svc.txt
tags:
- screen
- oslofmt