log Action
Last updated
Was this helpful?
Last updated
Was this helpful?
Used to augment the with .
The action takes a JSON object as its argument. The object may contain nested fields. A may be used for dynamic fields. (The has plenty examples for that.)
All name/value pairs of the object are registered for logging. When the system writes the flat_access
event the registered fields are included in that log line.
like timestamp
cannot be overriden.
You can call the action multiple times. Fields of the same name are overwritten. However, nested fields are merged into the previously registered log fields. The order of fields is maintained.
The merged custom log fields are:
Fields with null
values are not included in the log event. In order to remove a previously registered field, you can unset it with null
value.
The user
field of the previous example can be unregistered like this:
They would appear in the like this:
(Administration)
(Cookbook)
(Reference)