Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
BlaidddDrwg wants to merge 1 commit into
base: main
Choose a base branch
from
+33 −1
Open

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions TSG/ARM/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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 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:

| 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 |
13 changes: 12 additions & 1 deletion TSG/Lifecycle/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,14 @@
# 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 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 on lines +5 to +10
| 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 on lines +4 to +14