Commit Graph

13 Commits

Author SHA1 Message Date
Clark Boylan 88434e0ecb Retire os-loganalyze
This project has been unmaintained for a while. CI jobs don't currently
pass. Zuulv3's dashboard has largely replaced the need for this service
as well as it renders the logs for us instead.

If there is a need for this project elsewhere it can be resurrected and
maintained by others, but for now lets retire it and move on.

Depends-On: https://review.opendev.org/753398
Change-Id: I476b14c7cd9c49270f67897206ec7ad90643703b
2020-09-22 11:39:55 -07:00
Sean Dague 5b7ad194dd Remove swift support
The swift support was never moved into production for infra because of
an unsolved issue around index files, so the logs in swift approach
was ended. This takes out all the swift supporting code to drop the
complexity of the code base. As this is very intermittently maintained
tool, less code makes any future work easier to do.

Change-Id: Iabc4cffc35633fd808556ebb68a8bdd5a5d1fde0
2017-04-05 12:53:05 -04:00
Joshua Hesketh 8af49a756a Add support for non-text files
A first pass at adding support for non-text files.

This passes the content-type headers from swift to determine
how to serve up the file.

Change-Id: I905a31b68308c6a79ef863b94cebdaa14914b221
2015-04-13 12:17:10 +10:00
Sean Dague 6cfb364917 add support for source=swift
While we are running both filesystem and swift in parallel, it
would be good to be able to bypass the filesystem to test the
difference between swift and volume performance.

Do this with the addition of a source= cgi parameter. Currently
source=swift is the only thing that will change behavior. Internally
we default it to all.

Refactoring of the cgi param parsing is done to make it cleaner
code and not copy/paste the cgi param parsing a 3rd time.

Change-Id: Ic653bad9a0f74fb5714ff7ccfc7da8d790dcff8b
2014-07-16 16:49:51 +02:00
Sean Dague 2e5a2e8f29 introduce limit parameter
limit parameter allows you to specify a max number of lines that
you want, and will not go above that. It's added to deal with
run away failure conditions in logs which make their use in things
like Elastic Search really problematic, as a run away log can
kill logstash workers.

Change-Id: I25cfa10012060214046da8787eba8832e9eb802a
2014-07-08 12:53:13 -04:00
Sean Dague b1ae90e831 update README for accuracy
* the docs url never existed, remove it
 * add reference to the log line highlighting just implemented

Change-Id: I3714c459c02ea934e4cef529085e2d3db40b5ee0
2014-03-17 15:46:36 -04:00
Sean Dague cf06cc765c provide a -e run target to run server locally
this makes it much easier to see things in action, but running
the whole stack locally based on the sample files we provide in
the tree.

Change-Id: Ia27f81a87b116f5b8d6efad75fb6ed33868964ef
2014-03-17 15:46:29 -04:00
Darragh O'Reilly 7ffac14837 Provide a script that starts a simple WSGI server
This provides an alternative to using screens in devstack
for reading logs. It works out-of-box, so there is no need
to install and configure something like Apache.

Change-Id: I8811d16cbcb45baaaa4a44b923b813a40714ffa2
2013-12-17 14:15:33 +00:00
DennyZhang 4e91c30b83 fix typo
Change-Id: I4604e4c9931c44d0d9832b219c758b5f597b4aa4
2013-10-31 14:51:58 -05:00
Sean Dague 10157951c1 added support for skipping sev processing on logs
we really only support severity processing on some kinds of logs,
but we could support timestamps on many more of them. Be explicit
about what we support severity on so that we don't make logs go
away if we ask for them at DEBUG level and they don't have it.

Change-Id: I7460ccfdb4354137988257a9aed319b8dc7297a6
2013-10-13 18:51:32 -04:00
Sean Dague 3282034fe1 updating README to reflect reality
Change-Id: Ice9cfb6d5988ce06487cce037d2f65a7a3c1c809
2013-10-12 07:18:30 -04:00
Sean Dague cd34027dad make the readme not dumb 2013-10-11 11:42:06 -04:00
Sean Dague cf7925640a initial cookiecutter import 2013-10-11 10:03:03 -04:00