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.

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

Some errors seem to always be in json, even if using an interactive shell #368

Closed
ecordell opened this issue Apr 5, 2024 · 1 comment · Fixed by #405
Closed

Some errors seem to always be in json, even if using an interactive shell #368

ecordell opened this issue Apr 5, 2024 · 1 comment · Fixed by #405
Assignees
Labels
kind/bug Something is broken or regressed

Comments

@ecordell
Copy link
Contributor

ecordell commented Apr 5, 2024

Example:

$ zed --insecure --token=test --endpoint=localhost:50051 lookup-subjects
{"level":"error","error":"unknown command \"lookup-subjects\" for \"zed\"","time":"2024-04-05T14:03:14-04:00","message":"terminated with errors"}
@ecordell ecordell added the kind/bug Something is broken or regressed label Apr 8, 2024
@tstirrat15 tstirrat15 self-assigned this Aug 5, 2024
@tstirrat15
Copy link
Contributor

from Evan:

ah we use zerolog for logs normally, unless running as a server
so normally output commands would have logs like:

2:21PM INF configured logging async=false format=auto log_level=info provider=zerolog
2:21PM INF configured opentelemetry tracing endpoint= insecure=false provider=none sampleRatio=0.01 service=tiger v=0

where the latter is what we want it to look like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something is broken or regressed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants