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

Update logging.md for 3.5+ to show zap as default #645

Merged
merged 1 commit into from
Mar 3, 2023
Merged

Update logging.md for 3.5+ to show zap as default #645

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/docs/v3.5/dev-internal/logging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ weight: 1600
description: Logging level categories
---

etcd uses the [capnslog][capnslog] library for logging application output categorized into *levels*. A log message's level is determined according to these conventions:
etcd uses the [zap][zap] library for logging application output categorized into *levels*. A log message's level is determined according to these conventions:

* Error: Data has been lost, a request has failed for a bad reason, or a required resource has been lost
* Examples:
Expand All @@ -30,4 +30,4 @@ etcd uses the [capnslog][capnslog] library for logging application output catego
* Send a normal message to a remote peer
* Write a log entry to disk

[capnslog]: https://github.com/coreos/pkg/tree/master/capnslog
[zap]: https://github.com/uber-go/zap
4 changes: 2 additions & 2 deletions content/en/docs/v3.6/dev-internal/logging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ weight: 1600
description: Logging level categories
---

etcd uses the [capnslog][capnslog] library for logging application output categorized into *levels*. A log message's level is determined according to these conventions:
etcd uses the [zap][zap] library for logging application output categorized into *levels*. A log message's level is determined according to these conventions:

* Error: Data has been lost, a request has failed for a bad reason, or a required resource has been lost
* Examples:
Expand All @@ -30,4 +30,4 @@ etcd uses the [capnslog][capnslog] library for logging application output catego
* Send a normal message to a remote peer
* Write a log entry to disk

[capnslog]: https://github.com/coreos/pkg/tree/master/capnslog
[zap]: https://github.com/uber-go/zap