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.
Every log includes the following top-level fields:
dm.user.messagePurpose: Logs the user’s original utterance and plugins that passed initial filtering.
conversational_process.executePurpose: Logs plugin selection and resolved slots.
dm.assistant.messagePurpose: Logs a message sent to the user.
Example:
error_message and plugin_status.conversational_process.step.executePurpose: Logs individual step execution (actions, resolvers) in a plugin.
compound_action.triggerPurpose: Logs initiation of a Compound Action.
compound_action.step.executePurpose: Logs execution of a single step in a Compound Action.
action.http.triggerPurpose: Logs HTTP action execution.
action.script.triggerPurpose: Logs script (APIthon) execution.
error_messagelistener.webhook.triggerPurpose: Logs incoming webhook request and response sent back to the external system.
listener.webhook.processor.updatePurpose: Logs processing of the webhook payload and event data.
listener.webhook.plugin.triggerPurpose: Logs plugins triggered by the webhook.
root_uuid to correlate logs across plugin executionsplugin_name or log_type to isolate issues.