Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Structured logging on clients (opentracing compatible) #32

Open
Tracked by #31
, #233
...
BillCarsonFr opened this issue Oct 15, 2021 · 0 comments
Open
Tracked by #31
, #233
...

Structured logging on clients (opentracing compatible) #32

BillCarsonFr opened this issue Oct 15, 2021 · 0 comments
Assignees
@BillCarsonFr
Labels
T-Epic Issue is at Epic level Team: Crypto

Comments

@BillCarsonFr
Copy link
Member

BillCarsonFr commented Oct 15, 2021 •
edited by pmaier1
Loading

First step for: #31

Goal
Improve the logging in general
Switch to structured logging and a common output format for those logs (e.g. opentracing compatible)
Improve the experience when going through rageshakes, if our shakes are opentracing compatible we could use jaeger to inspect/search through them
@BillCarsonFr BillCarsonFr added T-Epic Issue is at Epic level Team: Crypto labels Oct 15, 2021
@BillCarsonFr BillCarsonFr self-assigned this Oct 15, 2021
@dkasak dkasak mentioned this issue Oct 15, 2021
Open
@BillCarsonFr BillCarsonFr mentioned this issue Apr 25, 2022
Open
@richvdh richvdh changed the title Structured logging on clients (open tracing compatible) Structured logging on clients (opentracing compatible) Nov 14, 2022
@richvdh richvdh mentioned this issue Nov 17, 2022
Closed
@pmaier1 pmaier1 changed the title Structured logging on clients (opentracing compatible) Structured logging on clients (opentracing compatible) Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BillCarsonFr BillCarsonFr

Labels
T-Epic Issue is at Epic level Team: Crypto
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BillCarsonFr