Have the log-gearman-client (aka jenkins-log-client) initialize
the statsd parameters when starting the geard server. Also, make
sure that the python statsd package is installed on the host.
Change-Id: I04fe1a7609f08bc710891b6a3b92d0f4d156d86c
Add grenade new/ and old/ logs to logstash. To do this without tripling
HTTP GETs for every finished job add a job filter to the log gearman
client that when present only attempts to grab files if the job name
matches the job filter.
Change-Id: Ia33722bf71d482f2fd6b655b28090a10bf46af54
Please see corresponding review for zmq-event-publisher:
https://review.openstack.org/#/c/67495/
This will help track down jenkins host/slave issues
Change-Id: I660252dc79f074b52587298120b4d6ceeedaf9a3
Since some bugs are branch specific we want to write logstash queries
that use the branch, so log ZUUL_BRANCH as build_branch in logstash.
From zuul's launchers doc:
ZUUL_BRANCH: The target branch for the change that triggered this build
Change-Id: Ic408afb235be5716231c663616c17a98ef6f8870
zmq publisher already has the computer/node name information
per commit:
openstack-infra/zmq-event-publisher 36ca349
we just need to pull it out of the event and pass it along as
a new field
Change-Id: Iddefdf74ddf170eaafcd82c5e1f5b0389651cf89
Separate the jenkins log client and worker bits into a new module
called log_processor with ::client and ::worker classes.
Instantiate two workers on each logstash worker node.
Change-Id: I7cfec410983c25633e6b555f22a85e9435884cfb
