You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Features
12
12
* The Agent no longer enforces all events must have monotonically increasing timestamps when pushed into Scalyr. The is now possible due to changes in the server. This allow better use of the default timestamps, such as in Docker and Kubernetes.
13
13
* Log lines collected via the Kubernetes or Docker monitors will now have their default timestamps set to the timestamp generated by K8s/Docker. As long as a parser does not override the timestamp, the K8s and Docker timestamps will be used in Scalyr.
14
14
* Agent logs with severity higher than INFO will now be output to stdout as well as the `agent.log` file when running with the `--no-fork` flag.
15
-
* The Journald monitor now supports a `detect_escaped_strings` option which automatically detects if the `details` field is already an escaped string, and if so, just emits it directly to the log instead of re-escaping it. This option is specified using the `journald_logs` array. See the [journald monitor documentation for more details](https://www.scalyr.com/help/monitors/journald).
15
+
* The Journald monitor now supports a `detect_escaped_strings` option which automatically detects if the `details` field is already an escaped string, and if so, just emits it directly to the log instead of re-escaping it. This option is specified using the `journald_logs` array. See the [journald monitor documentation](https://www.scalyr.com/help/monitors/journald) for more details.
16
16
17
17
Bugs
18
18
* Fixed monitor configuration bug that prevented config options that did not have a default nor were required from being properly set via environment variables.
0 commit comments