Skip to content

Log message created

Plugin ID: log:log_message

Available since: 1.0.0

Provided tokens

Token Description
[user] The current user.
Alias: current_user
[htmx] Information about the current HTMX request.
[htmx:is_request] Whether the current request was sent by HTMX ("1" or "0").
[htmx:boosted] Whether the current request was boosted by HTMX ("1" or "0").
[htmx:history_restore] Whether the current request is for HTMX history restoration ("1" or "0").
[htmx:target] The value of the HX-Target request header.
[htmx:trigger] The value of the HX-Trigger request header.
[htmx:trigger_name] The value of the HX-Trigger-Name request header.
[htmx:current_url] The value of the HX-Current-URL request header.
[log] The logger data which dispatched the event.
[log:severity] The log message severity.
[log:message] The log message.
[log:message:raw] The raw log message.
[log:message:full] The full and formatted log message with all variables replaced.
[log:context] All context variables of the log message.
[event] The event.
[event:machine_name] The machine name of the ECA event.
[session_user] The user account that dispatched the event, regardless if ECA is processing models under a different account. This is only available if ECA is configured to always run under a specific account.

Fires whenever a log message is submitted to Drupal's logging system. The [log:severity], [log:message:raw], [log:message:full], and [log:context] tokens provide details about the log entry.

Avoid infinite loops

If your ECA reaction generates a log message (e.g., via an action that logs), it can cause infinite recursion. Be careful about what actions are triggered from this event.

Fields

Type — config key: channel

The name of the logger type.

Type: textfield · Required: no · Default: empty string

The logger channel/type to filter by (e.g., php, system, cron). Leave empty to match all channels. This corresponds to the 'Type' column in Drupal's database log.

Minimum severity — config key: min_severity

The minimum severity. E.g. "critical" also covers "alert" and below.

Type: select · Required: no · Default: 3

Allowed values: 0, 1, 2, 3, 4, 5, 6, 7

The minimum severity level to react to. Uses RFC 5424 levels: Emergency (0), Alert (1), Critical (2), Error (3), Warning (4), Notice (5), Info (6), Debug (7). Setting to 'Error' also catches more severe levels.