Skip to content

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

Open
BlaidddDrwg wants to merge 1 commit intoAzure:mainfrom
BlaidddDrwg:main
Open

Add extra documentation for ARM telemetry and Arc node liveness check…#282
BlaidddDrwg wants to merge 1 commit intoAzure:mainfrom
BlaidddDrwg:main

Conversation

@BlaidddDrwg
Copy link
Copy Markdown
Collaborator

Add extra documentation for ARM telemetry and Arc node liveness checking.

Copilot AI review requested due to automatic review settings May 7, 2026 20:57
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation to help troubleshoot Azure Local deployments by querying (1) ARM telemetry and (2) Arc node liveness via Census records, complementing existing TSG content.

Changes:

  • Updated the Lifecycle TSG index to include Arc node liveness guidance and a sample Census KQL query.
  • Added a new ARM TSG README with a sample KQL query and a reference table of related ARM databases/tables.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File Description
TSG/Lifecycle/README.md Adds Arc node liveness/Census query guidance directly into the Lifecycle README.
TSG/ARM/README.md Introduces ARM telemetry querying guidance, including a sample query and database/table listing.

Comment thread TSG/Lifecycle/README.md
Comment on lines +4 to +14

The status of any ARC Node can be ascertained by looking at it's Census records. A sample query could be:

```KQL
cluster("https://aeoprodtelemetry.eastus.kusto.windows.net").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.
Comment thread TSG/Lifecycle/README.md
Comment on lines +5 to +10
The status of any ARC Node can be ascertained by looking at it's Census records. A sample query could be:

```KQL
cluster("https://aeoprodtelemetry.eastus.kusto.windows.net").database("Telemetry").Census
| where AEODeviceARMResourceUri =~ '<resource_id>'
| where AEOClusterNodeName =~ "Node name"
Comment thread TSG/ARM/README.md
| take 50;
```

the above query is for a deployment, 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:
Comment thread TSG/ARM/README.md
| Deployments | DeploymentOperations, Deployments, PreflightEvents |
| Traces | Errors, Traces |
| Providers | ProviderErrors, ProviderTraces |
| Jobs | JobDefinitions, JobDispatchingErrors, JobErrors, JobExecutionStatus, JobHistory, JobOperations, JobStatus, JobThrottles, JobTrace|
Comment thread TSG/ARM/README.md
| take 50;
```

the above query is for a deployment, 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:
@AlBurns-MSFT
Copy link
Copy Markdown
Collaborator

@BlaidddDrwg Please review the copilot suggestions. Once completed I'll review as well and then merge if everything looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants