Add extra documentation for ARM telemetry and Arc node liveness check…

TSG/ARM/README.md

@@ -0,0 +1,21 @@
+# ARM Telemetry
+
+ARM telemetry for a deployment, update, or even status can be queried using a query like:
+
+```KQL
+cluster("https://armprodgbl.eastus.kusto.windows.net").database('ARMProd').Unionizer('Deployments', 'DeploymentOperations')
+| where providerNamespace contains "AzureStackHCI"
+| take 50;
+```
+
+The above query targets deployments, but there are a number of [other databases](https://eng.ms/docs/cloud-ai-platform/azure-core/azure-cloud-native-and-management-platform/control-plane-bburns/azure-resource-reporting/azure-resource-reporting/dataconsumeronboarding/armdata/kustov2/overview_prod) that can be accessed, as listed on that page:
+
+| database | tables |
+|---------|----------|
+| Requests | EventServiceEntries, HttpIncomingRequests, HttpOutgoingRequests |
+| Deployments | DeploymentOperations, Deployments, PreflightEvents |
+| Traces | Errors, Traces |
+| Providers | ProviderErrors, ProviderTraces |
+| Jobs | JobDefinitions, JobDispatchingErrors, JobErrors, JobExecutionStatus, JobHistory, JobOperations, JobStatus, JobThrottles, JobTrace |
+| Storage | Compactions, Diagnostics, RedisOperations, RegionalStoreAdminLogs, RegionalStoreAdminTraces, RegionalStoreConfigurationLogs, RegionalStoreGarnetServerLogs, RegionalStoreGarnetServerTraces, RegionalStoreHealthCheckLogs, RegionalStoreJobEngineLogs, RegionalStoreServerLogs, RegionalStoreServerTraces, RegionalStoreService, StorageOperations, StorageRequests |
+| General | APIValidationErrors, APIValidationTraces, AppPerfCounters, ArmHttpOutgoingRequests, CapacityErrors, CapacityTraces, ClientErrors, ClientRequests, ClientTelemetry, ClientTraces, DispatcherErrors, DispatcherEvents, DispatcherTraces, IISHttpErrors, IISLogs, ManifestRegistrations, MarketplaceErrors, MarketplaceTraces, PolicyServiceDebug, PolicyServiceError, PolicyServiceWarning, ResourceDeletions, ResourceGroupDeletions, Service, SubscriptionProvisioningRequests2, SysPerfCounters, WindowsEvents |

TSG/Lifecycle/README.md

@@ -1,3 +1,17 @@
 # Infra Lifecycle Operations
 
-* [Add node, repair node fails with Type 'AddAsZHostToDomain' of Role 'BareMetal' raised an exception after cluster upgrade fail when upgraded from <=2311](./Add-node-repair-node-fails-with-Type-AddAsZHostToDomain-of-Role-BareMetal-raised-an-exception.md)
+* [Add node, repair node fails with Type 'AddAsZHostToDomain' of Role 'BareMetal' raised an exception after cluster upgrade fail when upgraded from <=2311](./Add-node-repair-node-fails-with-Type-AddAsZHostToDomain-of-Role-BareMetal-raised-an-exception.md)
+
+The status of any ARC Node can be ascertained by looking at its Census records. A sample query could be:
+
+> [!NOTE]
+> This sample query requires access to the appropriate Kusto cluster and database. Replace the placeholders with values from your environment and ensure you have the required permissions before running it.
+
+```KQL
+cluster("<kusto_cluster_uri>").database("Telemetry").Census
+| where AEODeviceARMResourceUri =~ '<resource_id>'
+| where AEOClusterNodeName =~ "<node_name>"
+| take 20
+| order by PreciseTimeStamp desc
+```
+Regular census reports indicate a healthy node. The 'EventString' column provides detailed information of various components of the Arc Node reporting in.