-
Notifications
You must be signed in to change notification settings - Fork 254
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
Structured logging doesn't seem to work #540
Comments
I'm guessing the |
If that is the case @Thomasdezeeuw, do you know which of the other loggers mentioned in the README does support structured logging? I was under the impression that this was fully handled in this crate and no additional changed were needed by individual loggers. |
I have my own implementation: https://github.com/Thomasdezeeuw/std-logger. It supports logfmt and JSON (specifically the JSON format used by GCP).
Key-value logging is experimental, though I think we're pretty close to a stable release. That said, I think individual implementations still need to separately log the key-value pairs as they're exposed a separate field. |
Thanks for the pointer @Thomasdezeeuw. Found this one which confirms your guess 😏 So I'll close this issue again... |
Add short name for no-confirm flag Closes rust-lang#536 The -y short name is a convention, often used by package managers (apt, yum, ...) and it is associated with a request of no interaction (thus often used in scripts, to automate workflows)
Hi 👋🏻 I'm trying write structured logs, but somehow the key/values seem to be ignored...
I have this in my
Cargo.toml
:And this is
main.rs
:And when I run this I get this:
Any ideas? Am I missing anything or doing something wrong?
Thanks!
The text was updated successfully, but these errors were encountered: