We now have consistent os-collect-config log formats for both
fedora and ubuntu tripleo ci jobs(from systemd journal and syslog
respectively), see I27ea3d465670277ef1ddf3d1b3b9d52df4162807 and
Ib8c1fc39d56b2b9c6d8e9b64a868def619aa2f1f. Tagging them as syslog
will ensure they are handled by the logstash syslog grok filter,
they currently don't match anything which results in messages
being indexed with a value of "%{logmessage}".
Change-Id: Iec5ffcb08e5b45fb01db25e14c943f000ca97a83
Closes-Bug: #1350121
Dependant on I787c08506d9a4d12081b5b5b16d752d5147f8e72 to collect the
javelin logs.
Since javelin2 uses tempest code to do the testing it generates useful
logs. As javelin2 grows to cover more we will most likely run into
issues that need debugging.
Add these logs to logstash to help us do analysis on javelin
results.
Change-Id: Ic3b2e33177bdc65fe294ddddd581a93de6c1cb60
After the successful implementation of
https://blueprints.launchpad.net/keystone/+spec/unified-logging-in-keystone
keystone uses oslo logging instead of its own. Update logstash settings
to reflect this.
We currently don't have any keystone logs in logstash, this should fix
that.
Change-Id: I7acfa35bfd112a15d2ec3aa7338fb28b37a827cb
The gate surely runs into libvirt bugs on a regular basis, but we don't
capture those logs in logstash, so we can't write elastic-recheck
queries against them.
For example, I believe the underlying cause of this issue is libvirt:
https://bugs.launchpad.net/tempest/+bug/1276778/comments/10
Change-Id: Ie2f03b19249967e78319a4016921f91ef0498540
We need to start doing this before we change grenade to not default
to spitting out everything to the console.
Change-Id: I58d32c27e78d2d6eb791f2d29c3aa886a5218c68
Add the os-collect-config logs to logstash to be indexed. Depends on
another commit in tripleo-ci to remove the random string from the log
name Ie84492ab981b06421d486579fc269ef6b3ad1815.
Change-Id: I2fe3aa4ec3c469d59a6dee8dd54f08d0bbf7b792
We need to index the tempest log so we can fingerprint errors using
multiple parts of the same traceback which doesn't work with the
console.html log.
Closes-Bug: #1323713
Change-Id: I34b2d67e12199ef0145d7a8d25d5385f944c78ed
Now that we have a grenade neutron job that we are trying to stabilize
and gate on, we should collect the neutron logs in grenade so we can use
logstash and elastic-recheck with grenade neutron jobs.
Change-Id: I54c4079b1be00d5201d4fb84dd975576551728fe
We are seeing a race failure in check-tempest-dsvm-postgres-full jobs
where the error message shows up in the screen-n-api-meta log but we can
only get at it from screen-n-api logs (or console). We should index on
the screen-n-api-meta log so we can better filter the query.
Related-Bug: #921858
Change-Id: I1701ac83b2643d819245a7cdbbfb56cc4af12f5b
There are 3 logs for neutron services we are regularly running in
the gate which we aren't indexing. Ensure they are all indexed so
we can actually use them in elastic recheck. They are all pretty
small so shouldn't impact ES load.
Change-Id: I082094574ceb6197e30708f9e05ba4b7fdc6f8af
this adds horizon_error to the indexed log files, which is very
useful in determining how horizon fails, as we get very specific
stack traces.
Change-Id: Ifb323e327dbc2931100a4552d029d91209c4bbba
We are currently using a lot of wildcard searches in elasticsearch which
are slow. Provide better field data so that we can replace those
wildcard searches with filters. In particular add a short uuid field and
make the filename tag field the basename of the filepath so that grenade
and non grenade files all end up with the same tags.
Change-Id: If558017fceae96bcf197e611ab5cac1cfe7ae9bf
We need a much higher level of output on libvirt logs to get to the
bottom of Bug 1254872. However, at that level of output, we crush
elastic search. So turn off indexing this log in the gate until we
get to the bottom of the bug and can return it to a more reasonable
logging level.
Change-Id: I9fec939883e50b421bc0530205e8b0bd7eab2350
Related-Bug: #1254872
index the sublog files so that we can use them in elastic search,
and so that we can start removing content from console.html.
Depends-On: Iede34b970d090f855c701b69c1f5167a08ab9c52
Which brings us time stamping to the sublogs
Change-Id: I4b4484065fda168f4d5efc73e95736226fb36ed0
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
Add them to all the places it's safe to do so for now. Don't actually
spin up any nodes for them yet.
Change-Id: I59e97be7e5b094af3153bc7d5dce0cff57996f55
Add jenkins01 and jenkins02, both of which will have unit test and
devstack slaves. Leave jenkins.o.o alone; over time it will be
reduced so that it alone has special jobs and privileged slaves
attached to it.
Note that currently all of the jobs will be defined on all nodes,
including jobs on timers. I think the long-term fix for that is to
have zuul schedule timed jobs.
Change-Id: I10bbd5555e5194b1031700975d5b3ae6b458b8b3
Change-Id: I7ba628bb5d7f160f67327310048973483b78b05a
Reviewed-on: https://review.openstack.org/34156
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
This change reorgs the logstash log pushing so that there is a central
gearman server that listens to Jenkins ZMQ events which are then
converted to per log file gearman jobs which are processed by gearman
workers. The central gearman server will live on logstash.o.o and the
existing logstash-worker hosts will be converted to gearman log pusher
workers.
This commit includes relavent documentation changes.
Change-Id: I45f7185c2479c54b090d223408dff268e1e8d7db
Reviewed-on: https://review.openstack.org/32455
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
