Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

Enterprise Knowledge observability


With Enterprise Knowledge observability, you can monitor, debug, and trace product events across the entire lifecycle of knowledge bases and knowledge sources. This includes tracking create, read, update, and delete (CRUD) operations, as well as searches, indexing, and retrievals.


Key capabilities

key-capabilities page anchor
FeatureDescriptionPrimary use case
Product event loggingStructured logs for key CRUD lifecycle operations, plus sync, import, and more across Enterprise Knowledge resourcesAuditing, event tracing, and downstream analysis
Error and warning logsDetailed diagnostics for all CRUD operation failures, including error_code, error_type, possible causes, and suggested actionsAccelerated root cause analysis and debugging
AlertingSet custom error and warning thresholds in the Twilio Console and route proactive alerts across multiple channels—including email, webhooks, and PagerDutyProactive incident response and SRE workflows
Traceability and lineageUnified trace ID propagation (conversation_id, request_id, profile_id, operator_id, and knowledge_id) across Conversation Orchestrator, Conversation Intelligence, and KnowledgeEnd-to-end debugging and correlation across the Twilio AI stack
Onboarding UI errorsBuilt-in observability for errors encountered during setup (profile and knowledge ingest, identity resolution). Errors are tagged with interface_type: "UI" in logsDebugging setup and configuration failures
Data export and integrationReal-time log export using Twilio Event Streams to external systems (Security Information and Event Management (SIEM), data warehouse, analytics) with personal data redactionAgent monitoring, compliance, and custom analytics

To view Enterprise Knowledge logs:

  1. Open the Twilio Console(link takes you to an external page).
  2. Go to Develop > Troubleshoot > Debugger.
  3. Filter by event type (for example, com.twilio.knowledge.knowledge.created) or search for Knowledge-related events.
  4. Select any log entry to expand the full diagnostic panel, including error descriptions, possible causes, and suggested remediation steps.

Enterprise Knowledge emits a structured log event for each significant state change. Events follow the naming convention:

com.twilio.<domain>.<resource>.<action>

Knowledge events

knowledge-events page anchor
Event typeDescription
com.twilio.knowledge.knowledge.createdNew knowledge document or source successfully created
com.twilio.knowledge.knowledge.updatedExisting knowledge document or source modified
com.twilio.knowledge.knowledge.deletedKnowledge document or source permanently removed
com.twilio.knowledge.knowledge.searchedKnowledge search operation completed
com.twilio.knowledge.knowledge.indexedKnowledge document indexed for retrieval
Event typeDescription
com.twilio.knowledge.knowledgebase.createdNew knowledge base provisioned
com.twilio.knowledge.knowledgebase.updatedKnowledge base configuration modified
com.twilio.knowledge.knowledgebase.deletedKnowledge base removed

Every log entry shares a common top-level structure:

FieldTypeDescription
logIdstringUnique identifier for this log entry
eventTimestring (ISO 8601)Timestamp of the event
sourcestringThe Knowledge subsystem that emitted the event
eventTypestringFull event type name (for example, com.twilio.knowledge.knowledgebase.created)
levelstringSeverity level: INFO, WARNING, or ERROR
errorCodeinteger0 for success; non-zero maps to the Twilio error catalog
errorReasonstring | nullHuman-readable error description, if applicable
requestIdstringUnique ID for the originating API request
correlationIdstringTrace ID for correlating events across services
bodyobjectOperation-specific payload
1
{
2
"logId": "1775677339108-67cbb62a",
3
"eventTime": "2026-04-08T19:42:19Z",
4
"source": "knowledge",
5
"eventType": "com.twilio.knowledge.knowledgebase.created",
6
"level": "INFO",
7
"errorCode": 0,
8
"errorReason": null,
9
"requestId": "4cc248bf-330b-49e6-9257-c9756e34c267",
10
"correlationId": "4cc248bf-330b-49e6-9257-c9756e34c267",
11
"body": {
12
"created_by": "ACda1bb2889ad6cbe4814c2addbc8a657c",
13
"error_code": null,
14
"interface_type": "API",
15
"latency_ms": 251,
16
"knowledge_base_id": "know_base_01knq9vx4qfghrt2dyrh4942w0"
17
}
18
}

Enterprise Knowledge logs errors and warnings for all create, update, delete, search, indexing, and retrieval operations. Twilio structures every error log entry to help you quickly identify the root cause and take corrective action.

FieldDescription
error_listArray of one or more error entries associated with the operation
error_codeNumeric code referencing the Twilio error catalog
error_typeCategorical classification (for example, ValidationError, IngestError, SearchError)
descriptionHuman-readable summary of what went wrong
possible_causesList of likely root causes for the error condition
possible_solutionsRecommended remediation steps
(information)

Info

Full error code descriptions and remediation guidance are available in the Twilio API error reference. Error details are also viewable directly in the Twilio Console Debugger.