使用資料匯出將 IoT 資料匯出至雲端目的地Export IoT data to cloud destinations using data export

注意

本文說明 IoT Central 中的資料匯出功能。This article describes the data export features in IoT Central.

本文說明如何使用 Azure IoT Central 中的新資料匯出功能。This article describes how to use the new data export feature in Azure IoT Central. 使用此功能可從您的 IoT Central 應用程式持續匯出已篩選和擴充的 IoT 資料。Use this feature to continuously export filtered and enriched IoT data from your IoT Central application. 資料匯出會以近乎即時的方式將變更推送至雲端解決方案的其他部分,以取得暖路徑見解、分析和儲存體。Data export pushes changes in near real time to other parts of your cloud solution for warm-path insights, analytics, and storage.

例如,您可以:For example, you can:

  • 以近乎即時的方式連續匯出 JSON 格式的遙測資料和屬性變更。Continuously export telemetry data and property changes in JSON format in near-real time.
  • 篩選資料串流,以匯出符合自訂條件的資料。Filter the data streams to export data that matches custom conditions.
  • 使用來自裝置的自訂值和屬性值來擴充資料流程。Enrich the data streams with custom values and property values from the device.
  • 將資料傳送至目的地,例如 Azure 事件中樞、Azure 服務匯流排、Azure Blob 儲存體和 webhook 端點。Send the data to destinations such as Azure Event Hubs, Azure Service Bus, Azure Blob Storage, and webhook endpoints.

提示

當您開啟資料匯出時,您只會取得該時間的資料。When you turn on data export, you get only the data from that moment onward. 目前,資料匯出關閉時無法取出資料。Currently, data can't be retrieved for a time when data export was off. 若要保留更多歷程記錄資料,請提早開啟資料匯出。To retain more historical data, turn on data export early.

先決條件Prerequisites

若要使用資料匯出功能,您必須有 V3 應用程式,而且必須擁有 資料匯出 許可權。To use data export features, you must have a V3 application, and you must have the Data export permission.

設定匯出目的地Set up export destination

設定資料匯出之前,您必須先有匯出目的地。Your export destination must exist before you configure your data export. 目前提供下列目的地類型:The following destination types are currently available:

  • Azure 事件中心Azure Event Hubs
  • Azure 服務匯流排佇列Azure Service Bus queue
  • Azure 服務匯流排主題Azure Service Bus topic
  • Azure Blob 儲存體Azure Blob Storage
  • WebhookWebhook

建立事件中樞目的地Create an Event Hubs destination

如果您沒有要匯出的現有事件中樞命名空間,請遵循下列步驟:If you don't have an existing Event Hubs namespace to export to, follow these steps:

  1. 在 Azure 入口網站中建立新事件中樞命名空間Create a new Event Hubs namespace in the Azure portal. 您可以透過 Azure 事件中樞文件深入了解。You can learn more in Azure Event Hubs docs.

  2. 在「事件中樞」命名空間中建立一個事件中樞。Create an event hub in your Event Hubs namespace. 移至您的命名空間,然後選取頂端的 [+ 事件中樞] 以建立事件中樞執行個體。Go to your namespace, and select + Event Hub at the top to create an event hub instance.

  3. 當您在 IoT Central 中設定資料匯出時,請產生要使用的金鑰:Generate a key to use when you to set up your data export in IoT Central:

    • 選取您建立的事件中樞實例。Select the event hub instance you created.
    • 選取 [ 設定] > 共用存取原則Select Settings > Shared access policies.
    • 建立新的金鑰,或選擇具有 傳送 許可權的現有金鑰。Create a new key or choose an existing key that has Send permissions.
    • 複製主要連接字串或次要連接字串。Copy either the primary or secondary connection string. 您可以使用此連接字串,在 IoT Central 中設定新的目的地。You use this connection string to set up a new destination in IoT Central.
    • 或者,您可以為整個事件中樞命名空間產生連接字串:Alternatively, you can generate a connection string for the entire Event Hubs namespace:
      1. 移至 Azure 入口網站中的事件中樞命名空間。Go to your Event Hubs namespace in the Azure portal.
      2. 在 [ 設定 ] 底下,選取 [ 共用存取原則 ]Under Settings , select Shared Access Policies
      3. 建立新的金鑰,或選擇具有 傳送 許可權的現有金鑰。Create a new key or choose an existing key that has Send permissions.
      4. 複製主要連接字串或次要連接字串Copy either the primary or secondary connection string

建立服務匯流排佇列或主題目的地Create a Service Bus queue or topic destination

如果您沒有要匯出的現有服務匯流排命名空間,請遵循下列步驟:If you don't have an existing Service Bus namespace to export to, follow these steps:

  1. 在 Azure 入口網站中建立新的服務匯流排命名空間Create a new Service Bus namespace in the Azure portal. 您可以透過 Azure 服務匯流排文件深入了解。You can learn more in Azure Service Bus docs.

  2. 若要建立要匯出的佇列或主題,請移至您的服務匯流排命名空間,然後選取 [ + 佇列 ] 或 [ + 主題 ]。To create a queue or topic to export to, go to your Service Bus namespace, and select + Queue or + Topic.

  3. 當您在 IoT Central 中設定資料匯出時,請產生要使用的金鑰:Generate a key to use when you to set up your data export in IoT Central:

    • 選取您建立的佇列或主題。Select the queue or topic you created.
    • 選取 [ 設定]/[共用存取原則 ]。Select Settings/Shared access policies.
    • 建立新的金鑰,或選擇具有 傳送 許可權的現有金鑰。Create a new key or choose an existing key that has Send permissions.
    • 複製主要連接字串或次要連接字串。Copy either the primary or secondary connection string. 您可以使用此連接字串,在 IoT Central 中設定新的目的地。You use this connection string to set up a new destination in IoT Central.
    • 或者,您可以為整個服務匯流排命名空間產生連接字串:Alternatively, you can generate a connection string for the entire Service Bus namespace:
      1. 在 Azure 入口網站中,移至您的服務匯流排命名空間。Go to your Service Bus namespace in the Azure portal.
      2. 在 [ 設定 ] 底下,選取 [ 共用存取原則 ]Under Settings , select Shared Access Policies
      3. 建立新的金鑰,或選擇具有 傳送 許可權的現有金鑰。Create a new key or choose an existing key that has Send permissions.
      4. 複製主要連接字串或次要連接字串Copy either the primary or secondary connection string

建立 Azure Blob 儲存體目的地Create an Azure Blob Storage destination

如果您沒有要匯出的現有 Azure 儲存體帳戶,請遵循下列步驟:If you don't have an existing Azure storage account to export to, follow these steps:

  1. 在 Azure 入口網站中建立新儲存體帳戶Create a new storage account in the Azure portal. 您可以深入瞭解如何建立新的 Azure Blob 儲存體帳戶Azure Data Lake Storage v2 儲存體帳戶You can learn more about creating new Azure Blob storage accounts or Azure Data Lake Storage v2 storage accounts. 資料匯出只能將資料寫入支援區塊 blob 的儲存體帳戶。Data export can only write data to storage accounts that support block blobs. 下列清單顯示已知的相容儲存體帳戶類型:The following list shows the known compatible storage account types:

    效能層級Performance Tier 帳戶類型Account Type
    標準Standard 一般用途 V2General Purpose V2
    標準Standard 一般用途 V1General Purpose V1
    標準Standard Blob 儲存體Blob storage
    PremiumPremium 區塊 Blob 儲存體Block Blob storage
  2. 若要在儲存體帳戶中建立容器,請移至您的儲存體帳戶。To create a container in your storage account, go to your storage account. 在 [Blob 服務] 下,選取 [瀏覽 Blob]。Under Blob Service , select Browse Blobs. 選取頂端的 [+ 容器] 以建立新的容器。Select + Container at the top to create a new container.

  3. 前往 [ 設定 > 存取金鑰 ],以產生儲存體帳戶的連接字串。Generate a connection string for your storage account by going to Settings > Access keys. 複製這兩個連接字串的其中一個。Copy one of the two connection strings.

建立 webhook 端點Create a webhook endpoint

您可以將資料匯出至公開可用的 HTTP webhook 端點。You can export data to a publicly available HTTP webhook endpoint. 您可以使用 RequestBin來建立測試 webhook 端點。You can create a test webhook endpoint using RequestBin. 當達到要求限制時,RequestBin 會對要求進行節流:RequestBin throttles request when the request limit is reached:

  1. 開啟 RequestBinOpen RequestBin.
  2. 建立新的 RequestBin,並複製 Bin URLCreate a new RequestBin and copy the Bin URL. 當您測試資料匯出時,會使用此 URL。You use this URL when you test your data export.

設定資料匯出Set up data export

現在您已有目的地可將資料匯出至,請在 IoT Central 應用程式中設定資料匯出:Now that you have a destination to export your data to, set up data export in your IoT Central application:

  1. 登入您的 IoT Central 應用程式。Sign in to your IoT Central application.

  2. 在左窗格中,選取 [ 資料匯出 ]。In the left pane, select Data export.

    提示

    如果您在左窗格中看不到 [ 資料匯出 ],則表示您沒有在應用程式中設定資料匯出的許可權。If you don't see Data export in the left pane, then you don't have permissions to configure data export in your app. 請連絡系統管理員來設定資料匯出。Talk to an administrator to set up data export.

  3. 選取 [ + 新增匯出 ]。Select + New export.

  4. 輸入新匯出的顯示名稱,並確定 已啟用 資料匯出。Enter a display name for your new export, and make sure the data export is Enabled.

  5. 選擇要匯出的資料類型。Choose the type of data to export. 下表列出支援的資料匯出類型:The following table lists the supported data export types:

    資料類型Data type 描述Description 資料格式Data format
    遙測Telemetry 以近乎即時的方式從裝置匯出遙測訊息。Export telemetry messages from devices in near-real time. 每個匯出的訊息都包含原始裝置訊息的完整內容,並正規化。Each exported message contains the full contents of the original device message, normalized. 遙測訊息格式Telemetry message format
    屬性變更Property changes 以近乎即時的方式將變更匯出至裝置和雲端屬性。Export changes to device and cloud properties in near-real time. 針對唯讀裝置屬性,系統會匯出回報值的變更。For read-only device properties, changes to the reported values are exported. 若為讀寫屬性,則會匯出報告和所需的值。For read-write properties, both reported and desired values are exported. 屬性變更訊息格式Property change message format

  1. (選擇性)新增篩選器來減少匯出的資料量。Optionally, add filters to reduce the amount of data exported. 有不同類型的篩選適用于每種資料匯出類型:There are different types of filter available for each data export type:

    若要篩選遙測,您可以:To filter telemetry, you can:

    • 篩選 匯出的資料流程,使其只包含符合裝置名稱、裝置識別碼和裝置範本篩選準則之裝置的遙測。Filter the exported stream to only contain telemetry from devices that match the device name, device ID, and device template filter condition.
    • 篩選 功能:如果您在 [ 名稱 ] 下拉式清單中選擇遙測專案,則匯出的資料流程只會包含符合篩選準則的遙測。Filter over capabilities: If you choose a telemetry item in the Name dropdown, the exported stream only contains telemetry that meets the filter condition. 如果您在 [ 名稱 ] 下拉式清單中選擇 [裝置] 或 [雲端] 屬性專案,則匯出的資料流程只會包含具有符合篩選準則之屬性之裝置的遙測。If you choose a device or cloud property item in the Name dropdown, the exported stream only contains telemetry from devices with properties matching the filter condition.
    • 訊息屬性篩選 :使用裝置 sdk 的裝置可以在每個遙測訊息上傳送 訊息屬性應用程式屬性Message property filter : Devices that use the device SDKs can send message properties or application properties on each telemetry message. 這些屬性是一組索引鍵/值組,會以自訂識別碼標記訊息。The properties are a bag of key-value pairs that tag the message with custom identifiers. 若要建立訊息屬性篩選,請輸入您要尋找的訊息屬性索引鍵,然後指定條件。To create a message property filter, enter the message property key you're looking for, and specify a condition. 只會匯出具有符合指定篩選準則之屬性的遙測訊息。Only telemetry messages with properties that match the specified filter condition are exported. 以下是支援的字串比較運算子: equals、不等於、contains、不包含、exists、不存在。The following string comparison operators are supported: equals, does not equal, contains, does not contain, exists, does not exist. 深入瞭解 IoT 中樞檔中的應用程式屬性Learn more about application properties from IoT Hub docs.

    若要篩選屬性變更,請使用 功能篩選To filter property changes, use a Capability filter. 選擇下拉式清單中的屬性專案。Choose a property item in the dropdown. 匯出的資料流程只包含符合篩選準則之選定屬性的變更。The exported stream only contains changes to the selected property that meets the filter condition.

  1. (選擇性)使用額外的索引鍵/值組中繼資料來擴充匯出的訊息。Optionally, enrich exported messages with additional key-value pair metadata. 下列擴充適用于遙測和屬性變更資料匯出類型:The following enrichments are available for the telemetry and property changes data export types:

    • 自訂字串 :將自訂靜態字串加入至每個訊息。Custom string : Adds a custom static string to each message. 輸入任何金鑰,並輸入任何字串值。Enter any key, and enter any string value.
    • 屬性 :將目前裝置回報的屬性或雲端屬性值新增至每個訊息。Property : Adds the current device reported property or cloud property value to each message. 輸入任何金鑰,然後選擇裝置或雲端屬性。Enter any key, and choose a device or cloud property. 如果匯出的訊息來自沒有指定屬性的裝置,則匯出的訊息不會取得擴充。If the exported message is from a device that doesn't have the specified property, the exported message doesn't get the enrichment.
  2. 加入新的目的地,或新增已建立的目的地。Add a new destination or add a destination that you've already created. 選取 [ 建立新的一個 ] 連結並新增下列資訊:Select the Create a new one link and add the following information:

    • 目的地名稱 : IoT Central 中目的地的顯示名稱。Destination name : the display name of the destination in IoT Central.
    • 目的地類型 :選擇目的地的類型。Destination type : choose the type of destination. 如果尚未設定目的地,請參閱 設定匯出目的地If you haven't already set up your destination, see Set up export destination.
    • 針對 Azure 事件中樞、Azure 服務匯流排佇列或主題,貼上資源的連接字串,並視需要輸入區分大小寫的事件中樞、佇列或主題名稱。For Azure Event Hubs, Azure Service Bus queue or topic, paste the connection string for your resource, and enter the case-sensitive event hub, queue, or topic name if necessary.
    • 針對 Azure Blob 儲存體,貼上資源的連接字串,並視需要輸入區分大小寫的容器名稱。For Azure Blob Storage, paste the connection string for your resource and enter the case-sensitive container name if necessary.
    • 針對 Webhook,貼上 webhook 端點的回呼 URL。For Webhook, paste the callback URL for your webhook endpoint. 您可以選擇性地 (OAuth 2.0 與授權權杖) 設定 webhook 授權,並新增自訂標頭。You can optionally configure webhook authorization (OAuth 2.0 and Authorization token) and add custom headers.
      • 針對 OAuth 2.0,僅支援用戶端認證流程。For OAuth 2.0, only the client credentials flow is supported. 儲存目的地之後,IoT Central 會與您的 OAuth 提供者進行通訊,以抓取授權權杖。When the destination is saved, IoT Central will communicate with your OAuth provider to retrieve an authorization token. 此權杖會附加至每個傳送至此目的地之訊息的「授權」標頭。This token will be attached to the "Authorization" header for every message sent to this destination.
      • 針對授權權杖,您可以針對每個傳送至此目的地的訊息,指定將直接附加至「授權」標頭的權杖值。For Authorization token, you can specify a token value that will be directly attached to the "Authorization" header for every message sent to this destination.
    • 選取 [建立]。Select Create.
  3. 選取 [ + 目的地 ],然後從下拉式清單中選擇目的地。Select + Destination and choose a destination from the dropdown. 您最多可以在單一匯出中新增五個目的地。You can add up to five destinations to a single export.

  4. 當您完成匯出的設定時,請選取 [ 儲存 ]。When you've finished setting up your export, select Save. 幾分鐘後,您的資料就會出現在您的目的地中。After a few minutes, your data appears in your destinations.

匯出內容和格式Export contents and format

Azure Blob 儲存體目的地Azure Blob Storage destination

資料會每分鐘匯出一次,每個檔案都包含自上一次匯出之後的變更批次。Data is exported once per minute, with each file containing the batch of changes since the previous export. 匯出的資料會以 JSON 格式儲存。Exported data is saved in JSON format. 您儲存體帳戶中匯出資料的預設路徑為:The default paths to the exported data in your storage account are:

  • 遙測: {container}/{app-id}/{partition_id}/{YYYY}/{MM}/{dd}/{hh}/{mm}/{filename}Telemetry: {container}/{app-id}/{partition_id}/{YYYY}/{MM}/{dd}/{hh}/{mm}/{filename}
  • 屬性變更: {container}/{app-id}/{partition_id}/{YYYY}/{MM}/{dd}/{hh}/{mm}/{filename}Property changes: {container}/{app-id}/{partition_id}/{YYYY}/{MM}/{dd}/{hh}/{mm}/{filename}

若要流覽 Azure 入口網站中匯出的檔案,請流覽至該檔案,然後選取 [ 編輯 blob ]。To browse the exported files in the Azure portal, navigate to the file and select Edit blob.

Azure 事件中樞和 Azure 服務匯流排目的地Azure Event Hubs and Azure Service Bus destinations

資料會以近乎即時的方式匯出。Data is exported in near real time. 資料會在訊息本文中,並以 JSON 格式編碼為 UTF-8。The data is in the message body and is in JSON format encoded as UTF-8.

訊息的注釋或系統屬性包包含 iotcentral-device-idiotcentral-application-idiotcentral-message-sourceiotcentral-message-type 欄位,這些欄位的值與訊息本文中的對應欄位相同。The annotations or system properties bag of the message contains the iotcentral-device-id, iotcentral-application-id, iotcentral-message-source, and iotcentral-message-type fields that have the same values as the corresponding fields in the message body.

Webhook 目的地Webhook destination

針對 webhook 目的地,資料也會以近乎即時的方式匯出。For webhooks destinations, data is also exported in near real time. 訊息本文中的資料會與事件中樞和服務匯流排的格式相同。The data in the message body is in the same format as for Event Hubs and Service Bus.

遙測格式Telemetry format

每個匯出的訊息都包含在訊息本文中傳送之完整訊息的標準化形式。Each exported message contains a normalized form of the full message the device sent in the message body. 此訊息為 JSON 格式,並編碼為 UTF-8。The message is in JSON format and encoded as UTF-8. 每則訊息中的資訊包括:Information in each message includes:

  • applicationId: IoT Central 應用程式的識別碼。applicationId: The ID of the IoT Central application.
  • messageSource:訊息的來源 telemetrymessageSource: The source for the message - telemetry.
  • deviceId:傳送遙測訊息的裝置識別碼。deviceId: The ID of the device that sent the telemetry message.
  • schema:裝載架構的名稱和版本。schema: The name and version of the payload schema.
  • templateId:與裝置相關聯之裝置範本的識別碼。templateId: The ID of the device template associated with the device.
  • enrichments:在匯出時設定的任何擴充。enrichments: Any enrichments set up on the export.
  • messageProperties:裝置隨訊息傳送的其他屬性。messageProperties: Additional properties that the device sent with the message. 這些屬性有時稱為 應用程式屬性These properties are sometimes referred to as application properties. 深入瞭解 IoT 中樞檔。Learn more from IoT Hub docs.

針對事件中樞和服務匯流排,IoT Central 會在收到來自裝置的訊息之後,快速匯出新訊息。For Event Hubs and Service Bus, IoT Central exports a new message quickly after it receives the message from a device. 在 [使用者屬性] (也稱為每個訊息) 的應用程式屬性, iotcentral-device-id iotcentral-application-id iotcentral-message-source 會自動包含、和。In the user properties (also referred to as application properties) of each message, the iotcentral-device-id, iotcentral-application-id, and iotcentral-message-source are included automatically.

針對 Blob 儲存體,每分鐘會批次處理和匯出訊息一次。For Blob storage, messages are batched and exported once per minute.

下列範例顯示匯出的遙測訊息:The following example shows an exported telemetry message:


{
    "applicationId": "1dffa667-9bee-4f16-b243-25ad4151475e",
    "messageSource": "telemetry",
    "deviceId": "1vzb5ghlsg1",
    "schema": "default@v1",
    "templateId": "urn:qugj6vbw5:___qbj_27r",
    "enqueuedTime": "2020-08-05T22:26:55.455Z",
    "telemetry": {
        "Activity": "running",
        "BloodPressure": {
            "Diastolic": 7,
            "Systolic": 71
        },
        "BodyTemperature": 98.73447010562934,
        "HeartRate": 88,
        "HeartRateVariability": 17,
        "RespiratoryRate": 13
    },
    "enrichments": {
      "userSpecifiedKey": "sampleValue"
    },
    "messageProperties": {
      "messageProp": "value"
    }
}

屬性變更格式Property changes format

每個訊息或記錄都代表一個對裝置或雲端屬性的變更。Each message or record represents one change to a device or cloud property. 針對裝置屬性,只會將回報值的變更匯出為個別的訊息。For device properties, only changes in the reported value are exported as a separate message. 匯出訊息中的資訊包括:Information in the exported message includes:

  • applicationId: IoT Central 應用程式的識別碼。applicationId: The ID of the IoT Central application.
  • messageSource:訊息的來源 propertiesmessageSource: The source for the message - properties.
  • messageTypecloudPropertyChangedevicePropertyDesiredChangedevicePropertyReportedChangemessageType: Either cloudPropertyChange, devicePropertyDesiredChange, or devicePropertyReportedChange.
  • deviceId:傳送遙測訊息的裝置識別碼。deviceId: The ID of the device that sent the telemetry message.
  • schema:裝載架構的名稱和版本。schema: The name and version of the payload schema.
  • templateId:與裝置相關聯之裝置範本的識別碼。templateId: The ID of the device template associated with the device.
  • enrichments:在匯出時設定的任何擴充。enrichments: Any enrichments set up on the export.

針對事件中樞和服務匯流排,IoT Central 會以近乎即時的方式將新的訊息資料匯出至事件中樞或服務匯流排佇列或主題。For Event Hubs and Service Bus, IoT Central exports new messages data to your event hub or Service Bus queue or topic in near real time. 在 [使用者屬性] (也稱為每個訊息) 的應用程式屬性, iotcentral-device-id iotcentral-application-id iotcentral-message-source iotcentral-message-type 會自動包含、、和。In the user properties (also referred to as application properties) of each message, the iotcentral-device-id, iotcentral-application-id, iotcentral-message-source, and iotcentral-message-type are included automatically.

針對 Blob 儲存體,每分鐘會批次處理和匯出訊息一次。For Blob storage, messages are batched and exported once per minute.

下列範例顯示 Azure Blob 儲存體中收到的已匯出屬性變更訊息。The following example shows an exported property change message received in Azure Blob Storage.

{
    "applicationId": "1dffa667-9bee-4f16-b243-25ad4151475e",
    "messageSource": "properties",
    "messageType": "cloudPropertyChange",
    "deviceId": "18a985g1fta",
    "schema": "default@v1",
    "templateId": "urn:qugj6vbw5:___qbj_27r",
    "enqueuedTime": "2020-08-05T22:37:32.942Z",
    "properties": [{
        "name": "MachineSerialNumber",
        "value": "abc"
    }],
    "enrichments": {
        "userSpecifiedKey" : "sampleValue"
    }
}

舊版資料匯出和資料匯出的比較Comparison of legacy data export and data export

下表顯示 舊版資料匯出 與新的資料匯出功能之間的差異:The following table shows the differences between the legacy data export and the new data export features:

功能Capabilities 舊版資料匯出Legacy data export 新增資料匯出New data export
可用的資料類型Available data types 遙測、裝置、裝置範本Telemetry, Devices, Device templates 遙測,屬性變更Telemetry, Property changes
篩選Filtering None 取決於匯出的資料類型。Depends on the data type exported. 針對遙測,依遙測篩選、訊息屬性、屬性值For telemetry, filtering by telemetry, message properties, property values
擴充Enrichments None 使用裝置上的自訂字串或屬性值進行擴充Enrich with a custom string or a property value on the device
DestinationsDestinations Azure 事件中樞、Azure 服務匯流排佇列和主題,Azure Blob 儲存體Azure Event Hubs, Azure Service Bus queues and topics, Azure Blob Storage 與舊版資料匯出和 webhook 相同Same as for legacy data export plus webhooks
支援的應用程式版本Supported application versions V2、V3V2, V3 僅限第 3 版V3 only
值得注意的限制Notable limits 每個應用程式5個匯出,每個匯出1個目的地5 exports per app, 1 destination per export 10個匯出-每個應用程式的目的地連線數10 exports-destination connections per app

後續步驟Next steps

現在您已瞭解如何使用新的資料匯出,建議的下一個步驟是瞭解 如何在 IoT Central 中流量分析Now that you know how to use the new data export, a suggested next step is to learn How to use analytics in IoT Central