The logscraper tool can be running as a one-shot log scrape or as periodical check, if some new log jobs are available.

The tool have help function, that is showing available options for it. It is available by typing:

logscraper --help

Fetch and push last Zuul CI job logs into gearman.

optional arguments:
  -h, --help            show this help message and exit
  --zuul-api-url ZUUL_API_URL
                        URL(s) for Zuul API. Parameter can be set multiple
  --job-name JOB_NAME   CI job name(s). Parameter can be set multiple times.
                        If not set it would scrape every latest builds.
  --gearman-server GEARMAN_SERVER
                        Gearman host addresss
  --gearman-port GEARMAN_PORT
                        Gearman listen port. Defaults to 4730.
  --follow              Keep polling zuul builds
  --insecure            Skip validating SSL cert
  --checkpoint-file CHECKPOINT_FILE
                        File that will keep information about last uuid
                        timestamp for a job.
  --logstash-url LOGSTASH_URL
                        When provided, script will check connection to
                        Logstash service before sending to log processing
                        system. For example: logstash.local:9999
  --workers WORKERS     Worker processes for logscraper
  --max-skipped MAX_SKIPPED
                        How many job results should be checked until last uuid
                        written in checkpoint file is founded
  --debug               Print more information
  --download            Download logs and do not send to gearman service
  --directory DIRECTORY
                        Directory, where the logs will be stored. Defaults to:

Basic usage

Base on the use case, we can run logscraper.


  • periodical check if there are some new logs for openstack tenant:

logscraper --gearman-server somehost --zuul-api-url https://zuul.opendev.org/api/tenant/openstack --checkpoint-file /tmp/results-checkpoint --follow
  • one shot on getting logs from zuul tenant:

logscraper --gearman-server localhost --zuul-api-url https://zuul.opendev.org/api/tenant/zuul --checkpoint-file /tmp/zuul-result-timestamp
  • periodically scrape logs from tenants: openstack, zuul and local

logscraper --gearman-server localhost --zuul-api-url https://zuul.opendev.org/api/tenant/openstack --zuul-api-url https://zuul.opendev.org/api/tenant/zuul --zuul-api-url https://zuul.opendev.org/api/tenant/local --checkpoint-file /tmp/someresults --follow
  • scrape logs from two defined job names: tripleo-ci-centos-8-containers-multinode and openstack-tox-linters for tenants: openstack and local:

logscraper --gearman-server localhost --job-name tripleo-ci-centos-8-containers-multinode --job-name openstack-tox-linters --zuul-api-url https://zuul.opendev.org/api/tenant/openstack --zuul-api-url https://zuul.opendev.org/api/tenant/local
  • download logs to /mnt/logscraper. NOTE: if you are using container service, this directory needs to be mounted!

logscraper --zuul-api-url https://zuul.opendev.org/api/tenant/openstack --directory /mnt/logscraper --download

Containerize tool

Instead of using pip tool, you can build your own container image that contains logscraper tool, for example:

docker build -t logscraper -f Dockerfile

Then you can execute commands that are described above.

NOTE: if you want to use parameter –checkpoint-file, you need to mount a volume to the container, for example:

docker run -v $(pwd):/checkpoint-dir:z -d logscraper logscraper --gearman-server somehost --zuul-api-url https://zuul.opendev.org/api/tenant/openstack --checkpoint-file /checkpoint-dir/checkpoint --follow

In this example, logscraper will download log files to the /mnt/logscraper directory:

docker run -v $(pwd):/checkpoint-dir:z -v /mnt/logscraper:/mnt/logscraper:z -d logscraper logscraper --zuul-api-url https://zuul.opendev.org/api/tenant/openstack --checkpoint-file /checkpoint-dir/checkpoint --directory /mnt/logscraper --download --follow