Project

General

Profile

Actions
Copy link

Feature #8072

closed

paddles: logging needs a better format

Added by Zack Cerza about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
High
Assignee:
Zack Cerza
Category:
-
Target version:
sprint4
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:

Description

A sample of paddles' log output:

path         - /runs/teuthology-2014-04-10_22:35:02-upgrade:dumpling-x:stress-split-firefly-distro-basic-vps/jobs/184216/
status       - 200 OK
method       - PUT
controller   - JobController.index
params       - []
hooks        - ['TransactionHook', 'RequestViewerHook', 'CorsHook']

/errors/invalid/?error_message=job with job_id 184442 already exists
path         - /runs/teuthology-2014-04-10_23:00:35-fs-firefly-distro-basic-plana/jobs/
status       - 200 OK
method       - POST
controller   - JobsController.index
params       - []
hooks        - ['TransactionHook', 'RequestViewerHook', 'CorsHook']

path         - /errors/invalid/
status       - 400 Bad Request
method       - POST
controller   - ErrorsController.invalid
params       - [('error_message', 'job with job_id 184442 already exists')]
hooks        - ['TransactionHook', 'RequestViewerHook', 'CorsHook']

Notice the lack of timestamps. I'd also like the format to be more compact.

Actions
Copy link

Also available in: Atom PDF