Optional twilioTwilio Alert resource logs, which detail the errors and warnings raised when Twilio makes a webhook request to your server or when your application calls the Twilio REST API. This is the one kind of data the integration collects by default.
Optional twilioTwilio Call Summary resource logs, covering the metadata and performance of the calls made from your Twilio account. Requires Voice Insights Advanced Features to be enabled on the Twilio account; without it this dataflow collects no data.
Optional twilioYour Twilio cost data, so that Twilio spend can be broken down and attributed in Cloud Cost Management. Cost data appears in Cloud Cost Management within 24 hours of enabling this dataflow.
Optional twilioTwilio Event resource logs, which record virtually every action taken in your Twilio account, such as provisioning a phone number, changing account security settings, or deleting a recording. Actions are recorded whether they came from the REST API, a user in the Twilio Console, or Twilio itself. Cloud SIEM analyzes and correlates these logs to detect threats in real time.
Optional twilioTwilio Message resource logs for inbound and outbound messages, used to track delivery and troubleshoot message errors. A log is produced when you send a message through the REST API, when Twilio executes a TwiML instruction, and when someone messages one of your Twilio numbers or channel addresses. Message bodies are never collected.
Generated using TypeDoc
Data Datadog collects from Twilio, keyed by dataflow id. Each dataflow turns on a distinct kind of collection: set
enabledto start or stop it. Defaults listed on each dataflow apply when the account is created; on update, omitted fields keep their current values. Where a dataflow depends on a Twilio feature being enabled, that prerequisite is noted on the dataflow; a dataflow enabled without it is stored but collects no data.