You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/digital-twins/concepts-azure-digital-twins-explorer.md
+2-10Lines changed: 2 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
5
5
description: Learn about the capabilities and purpose of Azure Digital Twins Explorer (preview) and when it can be a useful tool for visualizing digital models, twins, and graphs.
6
6
author: baanders
7
7
ms.author: baanders # Microsoft employees only
8
-
ms.date: 06/29/2023
8
+
ms.date: 01/27/2025
9
9
ms.topic: conceptual
10
10
ms.service: azure-digital-twins
11
11
@@ -64,21 +64,13 @@ For detailed instructions on how to use each feature, see [Use Azure Digital Twi
Azure Digital Twins Explorer is an open-source tool that welcomes contributions to the code and documentation. The hosted application is deployed regularly from a source code repository in GitHub.
70
-
71
-
To view the source code for the tool and read detailed instructions on how to contribute to the code, visit its GitHub repository: [digital-twins-explorer](https://github.com/Azure-Samples/digital-twins-explorer).
72
-
73
-
To view instructions for contributing to this documentation, review our [contributor guide](/contribute/).
74
-
75
67
## Other considerations
76
68
77
69
### Region support
78
70
79
71
Azure Digital Twins Explorer is available for use with all instances of Azure Digital Twins in all [supported regions](https://azure.microsoft.com/global-infrastructure/services/?products=digital-twins).
80
72
81
-
During public preview, however, data may be sent for processing through different regions than the region where the instance is hosted. To avoid data being routed in this way in situations where data sovereignty is a concern, you can download the [open source code](#how-to-contribute) to create a locally hosted version of the explorer on your own machine.
73
+
During public preview, however, data may be sent for processing through different regions than the region where the instance is hosted. To avoid data being routed in this way in situations where data sovereignty is a concern, you can download the open source code from the [digital-twins-explorer](https://github.com/Azure-Samples/digital-twins-explorer) repository to create a locally hosted version of the explorer on your own machine.
Copy file name to clipboardExpand all lines: articles/digital-twins/concepts-data-explorer-plugin.md
+48-47Lines changed: 48 additions & 47 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
5
5
description: Learn about the Azure Digital Twins query plugin for Azure Data Explorer
6
6
author: baanders
7
7
ms.author: baanders # Microsoft employees only
8
-
ms.date: 03/23/2022
8
+
ms.date: 01/27/2025
9
9
ms.topic: conceptual
10
10
ms.service: azure-digital-twins
11
11
@@ -17,9 +17,9 @@ ms.service: azure-digital-twins
17
17
18
18
# Azure Digital Twins query plugin for Azure Data Explorer
19
19
20
-
This article explains about the Azure Digital Twin query plugin for [Azure Data Explorer](/azure/data-explorer/data-explorer-overview), how to use Azure Data Explorer IoT data with Azure Digital Twins, how to map data across Azure Data Explorer and Azure Digital Twins, and more.
20
+
This article is about the Azure Digital Twins query plugin for [Azure Data Explorer](/azure/data-explorer/data-explorer-overview).
21
21
22
-
The Azure Digital Twins plugin for [Azure Data Explorer](/azure/data-explorer/data-explorer-overview) lets you run Azure Data Explorer queries that access and combine data across the Azure Digital Twins graph and Azure Data Explorer time series databases. Use the plugin to contextualize disparate time series data by reasoning across digital twins and their relationships to gain insights into the behavior of modeled environments.
22
+
The Azure Digital Twins plugin for Azure Data Explorer lets you run Azure Data Explorer queries that access and combine data across the Azure Digital Twins graph and Azure Data Explorer time series databases. Use the plugin to contextualize disparate time series data by reasoning across digital twins and their relationships to gain insights into the behavior of modeled environments.
23
23
24
24
For example, with this plugin, you can write a Kusto query that:
25
25
1. Selects digital twins of interest via the Azure Digital Twins query plugin,
@@ -28,50 +28,6 @@ For example, with this plugin, you can write a Kusto query that:
28
28
29
29
Combining data from a twin graph in Azure Digital Twins with time series data in Azure Data Explorer can help you understand the operational behavior of various parts of your solution.
30
30
31
-
## Using the plugin
32
-
33
-
You can invoke the plugin in a Kusto query with the following command. There are two placeholders, `<Azure-Digital-Twins-endpoint>` and `<Azure-Digital-Twins-query>`, which are strings representing the Azure Digital Twins instance endpoint and Azure Digital Twins query, respectively.
The plugin works by calling the [Azure Digital Twins Query API](/rest/api/digital-twins/dataplane/query), and the [query language structure](concepts-query-language.md) is the same as when using the API, with two exceptions:
40
-
* The `*` wildcard in the `SELECT` clause isn't supported. Instead, Azure Digital Twin queries that are executed using the plugin should use aliases in the `SELECT` clause.
41
-
42
-
For example, consider the below Azure Digital Twins query that is executed using the API:
43
-
44
-
```SQL
45
-
SELECT*FROM DIGITALTWINS
46
-
```
47
-
48
-
To execute that query when using the plugin, it should be rewritten like this:
49
-
50
-
```SQL
51
-
SELECT T FROM DIGITALTWINS T
52
-
```
53
-
* Column names returned by the plugin may not start with a `$`. Using aliases in the `SELECT` clause will also help to avoid this scenario.
54
-
55
-
For example, consider the below Azure Digital Twins query that is executed using the API:
56
-
57
-
```SQL
58
-
SELECT T.$dtId, T.Temperature FROM DIGITALTWINS T
59
-
```
60
-
61
-
To execute that query when using the plugin, it should be rewritten like this:
62
-
63
-
```SQL
64
-
SELECT T.$dtId as tid, T.Temperature FROM DIGITALTWINS T
65
-
```
66
-
67
-
68
-
>[!IMPORTANT]
69
-
>The user of the plugin must be granted the **Azure Digital Twins Data Reader** role or the **Azure Digital Twins Data Owner** role, as the user's Microsoft Entra token is used to authenticate. Information on how to assign this role can be found in [Security for Azure Digital Twins solutions](concepts-security.md#authorization-azure-roles-for-azure-digital-twins).
70
-
71
-
For more information on using the plugin, see the [Kusto documentation for the azure_digital_twins_query_request plugin](/azure/data-explorer/kusto/query/azure-digital-twins-query-request-plugin).
72
-
73
-
To see example queries and complete a walkthrough with sample data, see [Azure Digital Twins query plugin for Azure Data Explorer: Sample queries and walkthrough](https://github.com/Azure-Samples/azure-digital-twins-getting-started/tree/main/adt-adx-queries) in GitHub.
74
-
75
31
## Ingesting Azure Digital Twins data into Azure Data Explorer
76
32
77
33
Before querying with the plugin, you'll need to ingest your Azure Digital Twins data into Azure Data Explorer. There are two main ways you can do so: through the **data history** feature, or through direct ingestion. The following sections describe these options in more detail.
@@ -148,6 +104,51 @@ You may want to store a property in your schema with multiple fields. These prop
148
104
149
105
For instance, if you want to represent a property with three fields for roll, pitch, and yaw, the value object would look like this: `{"roll": 20, "pitch": 15, "yaw": 45}`.
150
106
107
+
## Using the plugin
108
+
109
+
Once your Azure Digital Twins data is in Azure Data Explorer, you can use the plugin to query it.
110
+
111
+
You can invoke the plugin in a Kusto query with the following command. There are two placeholders, `<Azure-Digital-Twins-endpoint>` and `<Azure-Digital-Twins-query>`, which are strings representing the Azure Digital Twins instance endpoint and Azure Digital Twins query, respectively.
>The user of the plugin must be granted the **Azure Digital Twins Data Reader** role or the **Azure Digital Twins Data Owner** role, as the user's Microsoft Entra token is used to authenticate. Information on how to assign this role can be found in [Security for Azure Digital Twins solutions](concepts-security.md#authorization-azure-roles-for-azure-digital-twins).
119
+
120
+
The plugin works by calling the [Azure Digital Twins Query API](/rest/api/digital-twins/dataplane/query), and the [query language structure](concepts-query-language.md) is the same as when using the API, with two exceptions:
121
+
* The `*` wildcard in the `SELECT` clause isn't supported. Instead, Azure Digital Twin queries that are executed using the plugin should use aliases in the `SELECT` clause.
122
+
123
+
For example, consider the below Azure Digital Twins query that is executed using the API:
124
+
125
+
```SQL
126
+
SELECT*FROM DIGITALTWINS
127
+
```
128
+
129
+
To execute that query when using the plugin, it should be rewritten like this:
130
+
131
+
```SQL
132
+
SELECT T FROM DIGITALTWINS T
133
+
```
134
+
* Column names returned by the plugin may not start with a `$`. Using aliases in the `SELECT` clause will also help to avoid this scenario.
135
+
136
+
For example, consider the below Azure Digital Twins query that is executed using the API:
137
+
138
+
```SQL
139
+
SELECT T.$dtId, T.Temperature FROM DIGITALTWINS T
140
+
```
141
+
142
+
To execute that query when using the plugin, it should be rewritten like this:
143
+
144
+
```SQL
145
+
SELECT T.$dtId as tid, T.Temperature FROM DIGITALTWINS T
146
+
```
147
+
148
+
For more information on using the plugin, see the [Kusto documentation for the azure_digital_twins_query_request plugin](/azure/data-explorer/kusto/query/azure-digital-twins-query-request-plugin).
149
+
150
+
To see example queries and complete a walkthrough with sample data, see [Azure Digital Twins query plugin for Azure Data Explorer: Sample queries and walkthrough](https://github.com/Azure-Samples/azure-digital-twins-getting-started/tree/main/adt-adx-queries) in GitHub.
151
+
151
152
## Next steps
152
153
153
154
* View the plugin documentation for the Kusto Query Language in Azure Data Explorer: [azure_digital_twins_query_request plugin](/azure/data-explorer/kusto/query/azure-digital-twins-query-request-plugin)
Azure Digital Twins is typically used together with other services to create flexible, connected solutions that use your data in different kinds of ways. This article covers data ingress and egress for Azure Digital Twins and Azure services that can be used to take advantage of it.
20
+
Azure Digital Twins is typically used together with other services to create flexible, connected solutions that use your data in different kinds of ways. This article covers data ingress and egress for Azure Digital Twins.
21
21
22
22
Azure Digital Twins can receive data from upstream services such as [IoT Hub](../iot-hub/about-iot-hub.md) or [Logic Apps](../logic-apps/logic-apps-overview.md), which are used to deliver telemetry and notifications.
23
23
24
-
Azure Digital Twins can also use [event routes](concepts-route-events.md) to send data to downstream services, such as [Azure Maps](../azure-maps/about-azure-maps.md), for storage, workflow integration, analytics, and more.
24
+
Azure Digital Twins can also use [event routes](concepts-route-events.md) to send data to downstream services, such as [Azure Storage](../storage/common/storage-introduction.md), for storage, workflow integration, analytics, and more.
Copy file name to clipboardExpand all lines: articles/digital-twins/concepts-models.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
5
5
description: Learn how Azure Digital Twins uses custom models to describe entities in your environment and how to define these models using the Digital Twin Definition Language (DTDL).
6
6
author: baanders
7
7
ms.author: baanders # Microsoft employees only
8
-
ms.date: 1/3/2024
8
+
ms.date: 01/27/2025
9
9
ms.topic: conceptual
10
10
ms.service: azure-digital-twins
11
11
@@ -90,7 +90,7 @@ Here are the attributes available in DTDL that are supported in Azure Digital Tw
90
90
The [DTDL v3 Language Description](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v3/DTDL.v3.md) also defines *Commands* and *Telemetry*, but neither of these are used in Azure Digital Twins. Commands are not supported, and Telemetry—although it's allowed in model definitions—has no unique use case in Azure Digital Twins modeling. Instead of using DTDL telemetry, you should use DTDL properties for storing twin state information.
91
91
92
92
> [!NOTE]
93
-
> Although there's no need to define Telemetry fields in your DTDL models to store incoming device data, Azure Digital Twins can emit events as telemetry using the [SendTelemetry API](concepts-event-notifications.md#digital-twin-telemetry-messages). This triggers a [Digital Twin Telemetry Message event](concepts-event-notifications.md#digital-twin-telemetry-messages) that can be received by an event handler to take actions on other twins or trigger downstream services.
93
+
> While there's no need to define Telemetry fields in your DTDL models to store incoming device data, Azure Digital Twins can emit events as telemetry using the [SendTelemetry API](concepts-event-notifications.md#digital-twin-telemetry-messages). This triggers a [Digital Twin Telemetry Message event](concepts-event-notifications.md#digital-twin-telemetry-messages) that can be received by an event handler to take actions on other twins or trigger downstream services.
94
94
95
95
## Properties
96
96
@@ -324,7 +324,7 @@ An alternative to the Import Jobs API is the [Model uploader sample](https://git
324
324
325
325
If you need to delete all models in an Azure Digital Twins instance at once, you can use the [Model Deleter sample](https://github.com/Azure/opendigitaltwins-tools/tree/main/ADTTools#deletemodels). This is a project that contains recursive logic to handle model dependencies through the deletion process. It currently only works with [version 2 of DTDL](concepts-models.md#supported-dtdl-versions).
326
326
327
-
Or, if you want to clear out the data in an instance by deleting all the models **along with** all twins and relationships, you can use the [Delete Jobs API](concepts-apis-sdks.md#bulk-delete-with-the-delete-jobs-api).
327
+
Or, if you want to clear out the data in an instance by deleting all the models **along with all twins and relationships**, you can use the [Delete Jobs API](concepts-apis-sdks.md#bulk-delete-with-the-delete-jobs-api).
Copy file name to clipboardExpand all lines: articles/digital-twins/concepts-ontologies-adopt.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
5
5
description: Learn about existing industry ontologies that can be adopted for Azure Digital Twins
6
6
author: baanders
7
7
ms.author: baanders # Microsoft employees only
8
-
ms.date: 01/18/2024
8
+
ms.date: 01/27/2025
9
9
ms.topic: conceptual
10
10
ms.service: azure-digital-twins
11
11
@@ -28,8 +28,6 @@ Microsoft has partnered with domain experts to create DTDL model sets based on i
28
28
| Energy grids |[Digital Twins Definition Language (DTDL) ontology for Energy Grid](https://github.com/Azure/opendigitaltwins-energygrid/)| This ontology was created to help solution providers accelerate development of digital twin solutions for energy use cases like monitoring grid assets, outage and impact analysis, simulation, and predictive maintenance. Additionally, the ontology can be used to enable the digital transformation and modernization of the energy grid. It's adapted from the [Common Information Model (CIM)](https://cimug.ucaiug.org/), a global standard for energy grid assets management, power system operations modeling, and physical energy commodity market. | You can also read more about the partnerships and approach for energy grids in the following blog post: [Energy Grid Ontology for Digital Twins](https://techcommunity.microsoft.com/t5/internet-of-things/energy-grid-ontology-for-digital-twins-is-now-available/ba-p/2325134). |
29
29
| Manufacturing |[Manufacturing Ontologies](https://github.com/digitaltwinconsortium/ManufacturingOntologies)| These ontologies were created to help solution providers accelerate development of digital twin solutions for manufacturing use cases like asset condition monitoring, simulation, OEE calculation, and predictive maintenance. Additionally, the ontologies can be used to enable the digital transformation and modernization of factories and plants. They are adapted from [OPC UA](https://opcfoundation.org), [ISA95](https://www.isa.org/standards-and-publications/isa-standards/isa-standards-committees/isa95) and the [Asset Administration Shell](https://reference.opcfoundation.org/I4AAS/v100/docs/4.1), three global standards widely used in the manufacturing space. | Visit the repository to read more about this ontology and explore a sample solution for ingesting OPC UA data into Azure Digital Twins. |
30
30
31
-
Each ontology is focused on an initial set of models. You can contribute to the ontologies by suggesting extensions or other improvements through the GitHub contribution process in each ontology repository.
32
-
33
31
## Next steps
34
32
35
33
Learn about extending existing industry-standard ontologies for your specific solution: [Extending industry ontologies](concepts-ontologies-extend.md).
0 commit comments