JSON logging support for CloudWatch integration.
Log messages should be maps with a :msg key for the human-readable message. Additional keys become structured data that CloudWatch Logs Insights can query.
Example:
(log/info {:msg "Segment restored"
:segment-start 1000
:segment-end 2000
:duration-ms 1234})
JSON logging support for CloudWatch integration.
Log messages should be maps with a :msg key for the human-readable message.
Additional keys become structured data that CloudWatch Logs Insights can query.
Example:
```
(log/info {:msg "Segment restored"
:segment-start 1000
:segment-end 2000
:duration-ms 1234})
```(configure-json-logging! {:keys [min-level service-name]
:or {min-level :info
service-name "datomic-replication"}})Configure Timbre for JSON output to stdout.
Options:
Configure Timbre for JSON output to stdout. Options: - :min-level - Minimum log level (default :info) - :service-name - Service name in log entries (default "datomic-replication")
(make-json-output-fn {:keys [service-name]
:or {service-name "datomic-replication"}})Creates a Timbre output-fn that prints JSON to stdout for CloudWatch ingestion.
Options:
Log entries can be maps with a :msg key. Additional keys become structured fields. If the log message is not a map, it becomes the :msg field.
Creates a Timbre output-fn that prints JSON to stdout for CloudWatch ingestion. Options: - :service-name - Name to include in log entries (default "datomic-replication") Log entries can be maps with a :msg key. Additional keys become structured fields. If the log message is not a map, it becomes the :msg field.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |