We should index on logs/error.txt.gz for e-r queries

Bug #1265906 reported by Matt Riedemann
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure

Bug Description

This isn't the first time I've needed to use an error message only found in logs/error.txt.gz to write an elastic-recheck query, but bug 1265904 is the latest. I'm not sure if there is already a reason why that file isn't indexed for logstash queries, but if we can we should index it so we can write queries against it.

Revision history for this message
Matt Riedemann (mriedem) wrote :

Bug 1265057 is another example:


"[ERROR] /opt/stack/new/devstack/exercises/horizon.sh:39 Horizon front page not functioning!"

Revision history for this message
Matt Riedemann (mriedem) wrote :

Indexing on logs/error.txt.gz would go here:


However, we probably need a new format to handle that defined here:


Since the error log doesn't have timestamps and all of the other log formats expect that.

Another alternative is changing the generator for the error.txt.gz log file, but I'm not sure where that happens.

Revision history for this message
Jeremy Stanley (fungi) wrote :

The error log checker is in the openstack/tempest project, if you decide it's worth tweaking there for easier indexing.

Changed in openstack-ci:
status: New → Triaged
importance: Undecided → Medium
milestone: none → icehouse
Revision history for this message
Clark Boylan (cboylan) wrote :

The basic minimum requirement for indexing logs is timestamps. There are other files we do not index because they lack timestamps. Add timestamps and we can index the file, but without that there isn't much we can do.

Sean Dague (sdague)
no longer affects: tempest
Revision history for this message
Clark Boylan (cboylan) wrote :

Marked wishlist as this isn't currently feasible with the log format we recieve.

Changed in openstack-ci:
importance: Medium → Wishlist
Jeremy Stanley (fungi)
Changed in openstack-ci:
milestone: icehouse → kilo
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.