Log Type Reference
Overview
Logs provide detailed visibility into plugin execution, webhook processing, and data flow. Each log entry includes shared metadata and a context-specific body under the root key. Use these logs to debug plugin selection, slot resolution, action execution, webhook handling, and more.
Note: Logs with sensitive data may be redacted. Learn more about log redaction.
Shared Metadata
Every log includes the following top-level fields:
Log Types
dm.user.message
Purpose: Logs the user’s original utterance and plugins that passed initial filtering.
Example Body:
Debug Use Cases:
- If your Plugin is low in the list but not selected, you may need to write better names, descriptions, and example triggering utterances
- If your Plugin is not on the list, you may not be passing the Launch Permissions that are set on the Plugin.
conversational_process.execute
Purpose: Logs plugin selection and resolved slots.
Example Body:
Debug Use Cases
- Why did my Plugin fail to trigger?
- Are the slot values correct?
dm.assistant.message
Purpose: Logs a message sent to the user.
Example Body:
Example:
Debug Use Cases:
- Why no response? Check
error_messageandplugin_status.
conversational_process.step.execute
Purpose: Logs individual step execution (actions, resolvers) in a plugin.
Example Body:
Debug Use Cases:
- Which step failed?
- Unexpected input/output?
compound_action.trigger
Purpose: Logs initiation of a Compound Action.
Example Body:
Debug Use Cases:
- Malformed input data when triggered.
- Trigger errors.
compound_action.step.execute
Purpose: Logs execution of a single step in a Compound Action.
Example Body:
Debug Use Cases:
- Compound Action hit the wrong conditional
- HTTP, Script, or Built-in Action failed
- Compound Action isn’t returning the correct data
action.http.trigger
Purpose: Logs HTTP action execution.
Example Body:
Debug Use Cases:
- HTTP Request failed due to bad/incorrect auth info
- HTTP Request failed due to bad/incorrect request info
action.script.trigger
Purpose: Logs script (APIthon) execution.
Example Body:
Debug Use Cases
- Understand why a script failed by inspecting the
error_message - Reproduce issues with access to all variables the script received
- Confirm whether the result matches expected output logic
listener.webhook.trigger
Purpose: Logs incoming webhook request and response sent back to the external system.
Example Body:
Debug Use Cases:
- Did the webhook arrive?
- Was the response correct?
listener.webhook.processor.update
Purpose: Logs processing of the webhook payload and event data.
Example Body:
Debug Use Cases:
- Event parsing issues.
- Payload transformation.
listener.webhook.plugin.trigger
Purpose: Logs plugins triggered by the webhook.
Example Body:
Debug Use Cases:
- Which plugins ran?
Best Practices
- Use
root_uuidto correlate logs across plugin executions - Filter by
plugin_nameorlog_type**to isolate issues.