Fixed typos in readme

parent 4e31eb13
# Change Log
All notable changes to this project will be documented in this file. This change log follows the conventions of [keepachangelog.com](http://keepachangelog.com/).
## [Unreleased]
## [0.1.11] - 2019-08-02
### Fixed
- Use library to do ANSI colors.
......
......@@ -90,9 +90,9 @@ function takes an optional map with these values, in addition to other things
you might want to tweak.
Any field supported by `Timbre` can be set. Note that setting the `:output-fn`
and `timestamp-opts` fields will not have any effect when `:log-to-elk` is true
(which is the default). Instead it will use the built in functions that follows
NSD's ELK schema.
, `x-request-formatter`, `level-formatter`and `timestamp-opts` fields will not
have any effect when `:log-to-elk` is true (which is the default). Instead it
will use the built in functions that follows NSD's ELK schema.
In addition to the `Timbre` fields, `Envelope` supports the following fields:
......@@ -152,7 +152,7 @@ entries will be consumed by `Envelope` and injected into your log. You don't
need to do anything for this to work.
**Note**: Some libraries (datomic peer being one of these) will look at your
dependency graph and try redirect their log output to known log targets they
dependency graph and try to redirect their log output to known log targets they
find there. If you are seeing some components not using `envelope`, try using
`:exclusions` in your dependency graph to remove transient dependencies to
`slf4j`, `logback` and other logging frameworks.
......@@ -160,10 +160,10 @@ find there. If you are seeing some components not using `envelope`, try using
### Context
When using `with-context`, Any fields present in the NSD ELK schema and in the
context map will converted to camel case and included in the log entry when
using ELK format logging. Please note that there is not schema validation done
on the context *values*.
When using `with-context`, any fields in the context map will be converted to
camel case and, if they exist in the NSD ELK schema, included in the log entry
when using ELK format logging. Please note that there is no schema validation
done on the context *values*.
The default non-elk (console) format will print the x-request-id field from the
context when present and ignore any other context values.
......
......@@ -91,6 +91,7 @@
:request
:response]))))
(defn local-console-format-fn [config data]
"A simpler log format, suitable for readable logs during development. colorized stacktraces"
(let [{:keys [level ?err msg_ ?ns-str ?file hostname_
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment