Bug 1707635 - update documentation how to ingest specific queues with new names (#7118)

Bug 1679162 had split the parsing of logs for failed tasks into multiple dimensions:
- monitored by code sheriffs or not
- raw or JSON data

This added 4 new queues:
- log_parser_fail_raw_sheriffed
- log_parser_fail_json_sheriffed
- log_parser_fail_raw_unsheriffed
- log_parser_fail_json_unsheriffed

The sheriffed ones handle the autoland and mozilla-* trees watched by code
sheriffs, the unsheriffed ones all other trees (e.g. 'try').
This commit is contained in:
Sebastian Hengst 2021-04-26 19:32:09 +02:00 коммит произвёл GitHub
Родитель 5bc38f8e8d
Коммит 8114e5f129
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 2 добавлений и 2 удалений

Просмотреть файл

@ -56,10 +56,10 @@ docker-compose run backend celery -A treeherder worker --concurrency 1
You will see a list of activated queues. If you wanted to narrow that down, then note You will see a list of activated queues. If you wanted to narrow that down, then note
which queues you'd like to run and add them to a comma-separated list. For instance, to which queues you'd like to run and add them to a comma-separated list. For instance, to
only do Log Parsing: only do Log Parsing for sheriffed trees (autoland, mozilla-*):
```bash ```bash
celery -A treeherder worker -Q log_parser,log_parser_fail --concurrency 1 docker-compose run backend celery -A treeherder worker -Q log_parser,log_parser_fail_raw_sheriffed,log_parser_fail_json_sheriffed --concurrency 1
``` ```
## Posting Data ## Posting Data