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/industrial-iot/industrial-iot-platform-versions.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,28 @@
1
1
---
2
2
title: Azure Industrial IoT platform versions
3
3
description: This article provides an overview of the existing version of the Industrial IoT platform and their support.
4
-
author: monikavar
5
-
ms.author: movarshn
4
+
author: hansgschossmann
5
+
ms.author: johanng
6
6
ms.service: industrial-iot
7
7
ms.topic: overview
8
8
ms.date: 11/10/2021
9
9
---
10
10
# Azure Industrial IoT Platform Release 2.8.2
11
-
We are pleased to announce the release of version 2.8.2 of our Industrial IoT Platform components as a second patch update of the 2.8 Long-Term Support (LTS) release. This release contains important backward compatibility fixes including Direct Methods API support with version 2.5.x, performance optimizations as well as security updates and bugfixes.
11
+
We're pleased to announce the release of version 2.8.2 of our Industrial IoT Platform components as a second patch update of the 2.8 Long-Term Support (LTS) release. This release contains important backward compatibility fixes including Direct Methods API support with version 2.5.x, performance optimizations and security updates and bug fixes.
12
12
13
13
## Azure Industrial IoT Platform Release 2.8.1
14
-
We are pleased to announce the release of version 2.8.1 of our Industrial IoT Platform components. This is the first patch update of the 2.8 Long-Term Support (LTS) release. It contains important security updates, bug fixes, and performance optimizations.
14
+
We're pleased to announce the release of version 2.8.1 of our Industrial IoT Platform components. This is the first patch update of the 2.8 Long-Term Support (LTS) release. It contains important security updates, bug fixes, and performance optimizations.
15
15
16
16
## Azure Industrial IoT Platform Release 2.8
17
17
18
-
We are pleased to announce the declaration of Long-Term Support (LTS) for version 2.8. While we continue to develop and release updates to our ongoing projects on GitHub, we now also offer a branch that will only get critical bug fixes and security updates starting in July 2021. Customers can rely upon a longer-term support lifecycle for these LTS builds, providing stability and assurance for the planning on longer time horizons our customers require. The LTS branch offers customers a guarantee that they will benefit from any necessary security or critical bug fixes with minimal impact to their deployments and module interactions. At the same time, customers can access the latest updates in the [main branch](https://github.com/Azure/Industrial-IoT) to keep pace with the latest developments and fastest cycle time for product updates.
18
+
We're pleased to announce the declaration of Long-Term Support (LTS) for version 2.8. While we continue to develop and release updates to our ongoing projects on GitHub, we now also offer a branch that will only get critical bug fixes and security updates starting in July 2021. Customers can rely upon a longer-term support lifecycle for these LTS builds, providing stability and assurance for the planning on longer time horizons our customers require. The LTS branch offers customers a guarantee that they'll benefit from any necessary security or critical bug fixes with minimal impact to their deployments and module interactions. At the same time, customers can access the latest updates in the [main branch](https://github.com/Azure/Industrial-IoT) to keep pace with the latest developments and fastest cycle time for product updates.
|2.5.4 |Stable |March 2020 |IoT Hub Direct Method Interface, control from cloud without any additional microservices (standalone mode), OPC UA Server Interface, uses OPC Foundation's OPC stack - [Release notes](https://github.com/Azure/Industrial-IoT/releases/tag/2.5.4)|
25
-
|[2.7.206](https://github.com/Azure/Industrial-IoT/tree/release/2.7.206)|Stable |January 2021 |Configuration through REST API (orchestrated mode), supports Samples telemetry format as well as PubSub - [Release notes](https://github.com/Azure/Industrial-IoT/releases/tag/2.7.206)|
24
+
|2.5.4 |Stable |March 2020 |IoT Hub Direct Method Interface, control from cloud without any microservices (standalone mode), OPC UA Server interface, uses OPC Foundation's OPC stack - [Release notes](https://github.com/Azure/Industrial-IoT/releases/tag/2.5.4)|
25
+
|[2.7.206](https://github.com/Azure/Industrial-IoT/tree/release/2.7.206)|Stable |January 2021 |Configuration through REST API (orchestrated mode), supports Samples telemetry format and PubSub format - [Release notes](https://github.com/Azure/Industrial-IoT/releases/tag/2.7.206)|
26
26
|[2.8](https://github.com/Azure/Industrial-IoT/tree/2.8.0)|Long-term support (LTS)|July 2021 |IoT Edge update to 1.1 LTS, OPC stack logging and tracing for better OPC Publisher diagnostics, Security fixes - [Release notes](https://github.com/Azure/Industrial-IoT/releases/tag/2.8.0)|
27
27
|[2.8.1](https://github.com/Azure/Industrial-IoT/tree/2.8.1)|Patch release for LTS 2.8|November 2021 |Critical bug fixes, security updates, performance optimizations for LTS v2.8|
28
28
|[2.8.2](https://github.com/Azure/Industrial-IoT/tree/2.8.2)|Patch release for LTS 2.8|March 2022 |Backwards compatibility with 2.5.x, bug fixes, security updates, performance optimizations for LTS v2.8|
Copy file name to clipboardExpand all lines: articles/industrial-iot/overview-what-is-opc-publisher.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
2
title: Microsoft OPC Publisher
3
3
description: This article provides an overview of the OPC Publisher Edge module.
4
-
author: v-condav
5
-
ms.author: jemorina
4
+
author: hansgschossmann
5
+
ms.author: johanng
6
6
ms.service: industrial-iot
7
7
ms.topic: conceptual
8
8
ms.date: 3/22/2021
9
9
---
10
10
11
11
# What is the OPC Publisher?
12
12
13
-
OPC Publisher is a fully-supported Microsoft product that bridges the gap between industrial assets and the Microsoft Azure cloud. It does so by connecting OPC UA-enabled assets or industrial connectivity software to your Microsoft Azure cloud. It publishes the telemetry data it gathers to Azure IoT Hub in various formats, including IEC62541 OPC UA PubSub standard format (from version 2.6 onwards). OPC Publisher runs on Azure IoT Edge as a Module or on plain Docker as a container. Because it leverages the .NET cross-platform runtime, it runs natively on both Linux and Windows 10.
13
+
OPC Publisher is a fullysupported Microsoft product that bridges the gap between industrial assets and the Microsoft Azure cloud. It does so by connecting OPC UA-enabled assets or industrial connectivity software to your Microsoft Azure cloud. It publishes the telemetry data it gathers to Azure IoT Hub in various formats, including IEC62541 OPC UA PubSub standard format (from version 2.6 onwards). OPC Publisher runs on Azure IoT Edge as a Module or on plain Docker as a container. Because it uses the .NET cross-platform runtime, it runs natively on both Linux and Windows 10.
14
14
15
15
OPC Publisher is a reference implementation that demonstrates how to:
16
16
@@ -42,7 +42,7 @@ OPC Publisher supports batching of the data sent to IoT Hub to reduce network lo
42
42
This application uses the OPC Foundation OPC UA reference stack as NuGet packages. See [https://opcfoundation.org/license/redistributables/1.3/](https://opcfoundation.org/license/redistributables/1.3/) for the licensing terms.
43
43
44
44
## Next steps
45
-
Now that you have learned what the OPC Publisher is, you can get started by deploying it:
45
+
Now that you've learned what the OPC Publisher is, you can get started by deploying it:
46
46
47
47
> [!div class="nextstepaction"]
48
48
> [Deploy OPC Publisher in standalone mode](tutorial-publisher-deploy-opc-publisher-standalone.md)
Copy file name to clipboardExpand all lines: articles/industrial-iot/tutorial-industrial-iot-azure-data-explorer.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
2
title: Pull Azure Industrial IoT data into ADX
3
3
description: In this tutorial, you learn how to pull IIoT data into ADX.
4
-
author: jehona-m
5
-
ms.author: jemorina
4
+
author: hansgschossmann
5
+
ms.author: johanng
6
6
ms.service: industrial-iot
7
7
ms.topic: tutorial
8
8
ms.date: 3/22/2021
9
9
---
10
10
11
11
# Tutorial: Pull Azure Industrial IoT data into ADX
12
12
13
-
The Azure Industrial IoT (IIoT) Platform combines edge modules and cloud microservices with a number of Azure PaaS services to provide capabilities for industrial asset discovery and to collect data from these assets using OPC UA. [Azure Data Explorer (ADX)](/azure/data-explorer) is a natural destination for IIoT data with data analytics features that enables running flexible queries on the ingested data from the OPC UA servers connected to the IoT Hub through the OPC Publisher. Although an ADX cluster can ingest data directly from the IoT Hub, the IIoT platform does further processing of the data to make it more useful before putting it on the Event Hub provided when a full deployment of the microservices is used (refer to the IIoT platform architecture).
13
+
The Azure Industrial IoT (IIoT) Platform combines edge modules and cloud microservices with many Azure PaaS services to provide capabilities for industrial asset discovery and to collect data from these assets using OPC UA. [Azure Data Explorer (ADX)](/azure/data-explorer) is a natural destination for IIoT data with data analytics features that enables running flexible queries on the ingested data from the OPC UA servers connected to the IoT Hub through the OPC Publisher. Although an ADX cluster can ingest data directly from the IoT Hub, the IIoT platform does further processing of the data to make it more useful before putting it on the Event Hubs provided when a full deployment of the microservices is used (refer to the IIoT platform architecture).
14
14
15
15
In this tutorial, you learn how to:
16
16
@@ -21,7 +21,7 @@ In this tutorial, you learn how to:
21
21
22
22
## How to make the data available in the ADX cluster to query it effectively
23
23
24
-
If we look at the message format from the Event Hub (as defined by the class Microsoft.Azure.IIoT.OpcUa.Subscriber.Models.MonitoredItemMessageModel), we can see a hint to the structure that we need for the ADX table schema.
24
+
If we look at the message format from the Event Hubs (as defined by the class Microsoft.Azure.IIoT.OpcUa.Subscriber.Models.MonitoredItemMessageModel), we can see a hint to the structure that we need for the ADX table schema.
5. Our table is now ready to receive data from the Event Hub.
48
-
6. Use the instructions [here](/azure/data-explorer/ingest-data-event-hub#connect-to-the-event-hub) to connect the Event Hub to the ADX cluster and start ingesting the data into our staging table. We only need to create the connection as we already have an Event Hub provisioned by the IIoT platform.
47
+
5. Our table is now ready to receive data from the Event Hubs.
48
+
6. Use the instructions [here](/azure/data-explorer/ingest-data-event-hub#connect-to-the-event-hub) to connect the Event Hubs to the ADX cluster and start ingesting the data into our staging table. We only need to create the connection as we already have an Event Hubs provisioned by the IIoT platform.
49
49
7. Once the connection is verified, data will start flowing to our table and after a short delay we can start examining the data in our table. Use the following query in the ADX web interface to look at a data sample of 10 rows. We can see here how the data in the payload resembles the MonitoredItemMessageModel class mentioned earlier.
@@ -63,7 +63,7 @@ Since our ‘payload’ column contains a dynamic data type, we need to carry ou
63
63
64
64
As we mentioned earlier, ingesting the OPC UA data into a staging table with one ‘Dynamic’ column gives us flexibility. However, having to run data type conversions at query time can result in delays in executing the queries particularly if the data volume is large and if there are many concurrent queries. At this stage, we can create another table with the data types already determined, so that we avoid the query-time data type conversions.
65
65
66
-
9. Create a new table for the parsed data that consists of a limited selection from the content of the dynamic ‘payload’ in the staging table. Note that we've created a value column for each of the expected data types expected in our telemetry.
66
+
9. Create a new table for the parsed data that consists of a limited selection from the content of the dynamic ‘payload’ in the staging table. We've created a value column for each of the expected data types expected in our telemetry.
67
67
68
68
```
69
69
.create table ['iiot_parsed']
@@ -124,7 +124,7 @@ We can see that the query that uses the parsed table is roughly twice as fast as
124
124
> The Update Policy only works on the data that is ingested into the staging table after the policy was set up and doesn't apply to any pre-existing data. This needs to be taken into consideration when, for example, we need to change the update policy. Full details can be found in the ADX documentation.
125
125
126
126
## Next steps
127
-
Now that you have learned how to change the default values of the configuration, you can
127
+
Now that you've learned how to change the default values of the configuration, you can
0 commit comments