summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJay Mundrawala <jdmundrawala@gmail.com>2015-05-13 13:57:46 -0500
committerJay Mundrawala <jdmundrawala@gmail.com>2015-05-13 13:57:46 -0500
commit2b3615376dd757a61d26111c3497875e487e8a2c (patch)
tree410d1e17e77dca44e2233a4e1ef4ec0ee8275034
parent982491cfa2e6673ee3aba3496485c51aa918b04b (diff)
downloadchef-2b3615376dd757a61d26111c3497875e487e8a2c.tar.gz
updated release notes for #3345
-rw-r--r--RELEASE_NOTES.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 4520a37d44..40308484dd 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -8,3 +8,16 @@ and edit keys for a given user or client. They can be used to implement
key rotation with multiple expiring keys for a single actor or just
for basic key management. See `knife user key` and `knife client key`
for a full list of subcommands and their usage.
+
+## System Loggers
+
+### Windows Event Logger
+
+You can now have all Chef logs sent to the Windows Event Logger. The logger can be
+used by adding the following line to your chef config file:
+
+```ruby
+log_location Chef::Log::WinEvt.new
+```
+
+This will write to the Application log with the source set as Chef.