charleszipp / abode Goto Github PK

Many of the ch7 exercises cannot be completed as asked due to missing data in the diagnostic and metric tables, despite capturing all diagnostics:

Create a query that reports the billing costs from the usage of each digital twins operation

BillingQueryUnits metrics type doesn't appear to get created after capturing diagnostic logs and messages -- after 24h of collecting logs, the following query reveals that BillingApiOperations and BillingMessagesProcessed are present but BillingQueryUnits is not as verified by:

AzureMetrics
| summarize count() by MetricName

Create a query that checks for a property value anomaly or threshold for a twin entity

The DigitalTwinsOperation and EventRoutesOperation are present, while ModelsOperation, QueryOperation, ResourceProviderOperation are not. However even looking at the sample logs for these tables, I don't believe any of them capture specifics for specific property values on the twin in a way that could predict anomalies. They only capture the operation performed against the twin.

Note - it may also be worth noting in the docs that metrics take up to 1h to being flowing in to Log Analytics.

The second learning exercise, Using Time Series Insights with Azure Digital Twin, links to this walkthrough which has incomplete code samples and describes a procedure for instance synchronization, not model/hierarchy synchronization. See also MicrosoftDocs/azure-docs#77641.

In the interim, I think would be worth removing it as at the present time is adds some confusion.

After running through ch6, I found the Integrating ADT with TSI guide to the most informative and functional. Presently, the learning experience guides users to the Getting started tutorial and ingesting data from event hub which is effectively what the first link does, but without ADT-specific guidance so users may end up using the wrong property name when creating TSI, etc and need to start over or have to manually setup the flow into the event hub.

I would recommend directly pointing users to the Integrating ADT with TSI page as a learning experience as it is more targeted and instructional.