Skip to content

Commit 492daf2

Browse files
authored
Merge branch 'main' into patch-15
2 parents bd38ce9 + e0bb55d commit 492daf2

File tree

55 files changed

+757
-539
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

55 files changed

+757
-539
lines changed

.openpublishing.publish.config.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -92,6 +92,12 @@
9292
"branch": "main",
9393
"branch_mapping": {}
9494
},
95+
{
96+
"path_to_root": "azure-reference-other-repo",
97+
"url": "https://github.com/MicrosoftDocs/azure-reference-other-pr",
98+
"branch": "main",
99+
"branch_mapping": {}
100+
},
95101
{
96102
"path_to_root": "quickstart-templates",
97103
"url": "https://github.com/Azure/azure-quickstart-templates",

AKS-Hybrid/aks-edge-howto-setup-machine.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to prepare your machines for AKS Edge Essentials clusters
44
author: rcheeran
55
ms.author: rcheeran
66
ms.topic: how-to
7-
ms.date: 02/13/2024
7+
ms.date: 08/19/2024
88
ms.custom: template-how-to
99
---
1010

@@ -111,6 +111,5 @@ This command displays output similar to the following list:
111111

112112
## Next steps
113113

114-
- Create a [simple deployment](aks-edge-howto-single-node-deployment.md)
115-
- Create a [full deployment](aks-edge-howto-multi-node-deployment.md)
116-
114+
- [Create a single machine deployment](aks-edge-howto-single-node-deployment.md)
115+
- [Create a full Kubernetes deployment](aks-edge-howto-multi-node-deployment.md)

azure-managed-lustre/TOC.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,12 @@
4444
href: configure-network-security-group.md
4545
- name: Use customer-managed encryption keys
4646
href: customer-managed-encryption-keys.md
47+
- name: Monitoring metrics and logs
48+
items:
49+
- name: Monitor a file system
50+
href: monitor-file-system.md
51+
- name: Monitoring reference for metrics and logs
52+
href: monitor-file-system-reference.md
4753
- name: Availability and disaster recovery
4854
items:
4955
- name: Recover from a regional outage

azure-managed-lustre/create-file-system-resource-manager.md

Lines changed: 149 additions & 228 deletions
Large diffs are not rendered by default.
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
title: Monitoring data reference for Azure Managed Lustre
3+
description: This article contains important reference material you need when you monitor Azure Managed Lustre.
4+
ms.date: 08/16/2024
5+
ms.custom: horz-monitor
6+
ms.topic: reference
7+
author: pauljewellmsft
8+
ms.author: pauljewell
9+
ms.service: azure-managed-lustre
10+
---
11+
12+
# Azure Managed Lustre monitoring data reference
13+
14+
[!INCLUDE [horz-monitor-ref-intro](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-intro.md)]
15+
16+
See [Monitor Azure Managed Lustre](monitor-file-system.md) for details on the data you can collect for Azure Managed Lustre and how to use it.
17+
18+
[!INCLUDE [horz-monitor-ref-metrics-intro](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-intro.md)]
19+
20+
### Supported metrics for Microsoft.StorageCache/amlFilesystems
21+
22+
The following table lists the metrics available for the Microsoft.StorageCache/amlFilesystems resource type.
23+
24+
[!INCLUDE [horz-monitor-ref-metrics-tableheader](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
25+
26+
[!INCLUDE [Microsoft.StorageCache/amlFilesystems](~/../azure-reference-other-repo/azure-monitor-ref/supported-metrics/includes/microsoft-storagecache-amlfilesystems-metrics-include.md)]
27+
28+
> [!NOTE]
29+
> The metric `OSTBytesUsed` represents the total capacity consumed on the file system, including all metadata and overhead associated with the files. The value for `OSTBytesUsed` might be greater than the result of running `lfs df` on the file system, as `df` output for **Used** only attempts to capture the data that the end user has placed on the file system.
30+
31+
[!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
32+
33+
[!INCLUDE [horz-monitor-ref-metrics-dimensions](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions.md)]
34+
35+
### Dimensions specific to Azure Managed Lustre
36+
37+
| Dimension name | Description |
38+
| --- | --- |
39+
| `ostnum` | Object Storage Target (OST) index number |
40+
| `mdtnum` | Metadata Target (MDT) index number |
41+
| `operation` | Type of operation performed |
42+
43+
### Supported resource logs for Microsoft.StorageCache/amlFilesystems
44+
45+
[!INCLUDE [Microsoft.StorageCache/amlFilesystems](~/../azure-reference-other-repo/azure-monitor-ref/supported-logs/includes/microsoft-storagecache-amlfilesystems-logs-include.md)]
46+
47+
### Azure Monitor Logs tables
48+
49+
This section lists the Azure Monitor Logs tables relevant to this service, which are available for query by Log Analytics using Kusto queries.
50+
51+
- [AFSAuditLogs](/azure/azure-monitor/reference/tables/AFSAuditLogs)
52+
- [AzureActivity](/azure/azure-monitor/reference/tables/azureactivity)
53+
- [AzureMetrics](/azure/azure-monitor/reference/tables/azuremetrics)
54+
55+
[!INCLUDE [horz-monitor-ref-activity-log](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-activity-log.md)]
56+
57+
- [Microsoft.StorageCache permissions](/azure/role-based-access-control/permissions/storage#microsoftstoragecache)
58+
59+
## Related content
60+
61+
- See [Monitor Azure Managed Lustre](monitor-file-system.md) for a description of monitoring Azure Managed Lustre.
62+
- See [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.
Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
---
2+
title: Monitor Azure Managed Lustre
3+
description: Start here to learn how to monitor Azure Managed Lustre.
4+
ms.date: 08/16/2024
5+
ms.custom: horz-monitor
6+
ms.topic: conceptual
7+
author: pauljewellmsft
8+
ms.author: pauljewell
9+
ms.service: azure-managed-lustre
10+
---
11+
12+
# Monitor Azure Managed Lustre
13+
14+
[!INCLUDE [horz-monitor-intro](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-intro.md)]
15+
16+
[!INCLUDE [horz-monitor-resource-types](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-resource-types.md)]
17+
18+
For more information about the resource types for Azure Managed Lustre, see [Azure Managed Lustre monitoring data reference](monitor-file-system-reference.md).
19+
20+
[!INCLUDE [horz-monitor-data-storage](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-data-storage.md)]
21+
22+
[!INCLUDE [horz-monitor-platform-metrics](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-platform-metrics.md)]
23+
24+
For a list of available metrics for Azure Managed Lustre, see [Azure Managed Lustre monitoring data reference](monitor-file-system-reference.md#metrics).
25+
26+
[!INCLUDE [horz-monitor-resource-logs](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-resource-logs.md)]
27+
28+
For the available resource log categories, their associated Log Analytics tables, and the log schemas for Azure Managed Lustre, see [Azure Managed Lustre monitoring data reference](monitor-file-system-reference.md#supported-resource-logs-for-microsoftstoragecacheamlfilesystems).
29+
30+
[!INCLUDE [horz-monitor-activity-log](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-activity-log.md)]
31+
32+
[!INCLUDE [horz-monitor-analyze-data](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-analyze-data.md)]
33+
34+
[!INCLUDE [horz-monitor-external-tools](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-external-tools.md)]
35+
36+
[!INCLUDE [horz-monitor-kusto-queries](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-kusto-queries.md)]
37+
38+
This section shows queries that you can enter in the **Log search** bar to help you monitor your Managed Lustre file system.
39+
40+
- **Aggregate operations query**: List all the UnsuspendAmlFilesystem requests for a given time duration.
41+
42+
```kusto
43+
AFSAuditLogs
44+
// The OperationName below can be replaced by obtain other operations such as "RebootAmlFilesystemNode" or "AmlFSRefreshHSMToken".
45+
| where OperationName has "UnsuspendAmlFilesystem"
46+
| project TimeGenerated, _ResourceId, ActivityId, ResultSignature, ResultDescription, Location
47+
| sort by TimeGenerated asc
48+
| limit 100
49+
```
50+
51+
- **Unauthorized requests query**: Count of failed AMLFilesystems requests due to unauthorized access.
52+
53+
```kusto
54+
AFSAuditLogs
55+
// 401 below could be replaced by other result signatures to obtain different operation results.
56+
// For example, 'ResultSignature == 202' to obtain accepted requests.
57+
| where ResultSignature == 401
58+
| summarize count() by _ResourceId, OperationName
59+
```
60+
61+
[!INCLUDE [horz-monitor-alerts](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-alerts.md)]
62+
63+
### Azure Managed Lustre alert rules
64+
65+
The following table lists some suggested alert rules for Azure Managed Lustre. The alerts in this table are just examples. You can set alerts for any metric, log entry, or activity log entry listed in the [Azure Managed Lustre monitoring data reference](monitor-file-system-reference.md).
66+
67+
| Alert type | Condition | Description |
68+
| --- | --- | --- |
69+
| Metric | (**OST Bytes Used** / **OST Bytes Total**) > 0.85 | Storage capacity usage for the file system has exceeded 85% of total|
70+
| Metric | (**OST Files Used** / **OST Files Total**) > 0.85 | Number of files in the file system has exceeded 85% of total |
71+
72+
> [!NOTE]
73+
> The threshold value of 85% is used as an example to show an alert before the file system reaches full capacity. You can adjust the threshold based on your requirements.
74+
75+
[!INCLUDE [horz-monitor-advisor-recommendations](~/../azure-stack/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-advisor-recommendations.md)]
76+
77+
## Related content
78+
79+
- See [Azure Managed Lustre monitoring data reference](monitor-file-system-reference.md) for a reference of the metrics, logs, and other important values created for Azure Managed Lustre.
80+
- See [Monitoring Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for general details on monitoring Azure resources.

azure-stack/asdk/asdk-admin-basics.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,8 @@ description: Learn how to do basic admin tasks for the Azure Stack Development K
44
author: sethmanheim
55

66
ms.topic: article
7-
ms.date: 10/29/2021
7+
ms.date: 08/19/2024
88
ms.author: sethm
9-
ms.reviewer: misainat
10-
ms.lastreviewed: 10/15/2019
119

1210
# Intent: As an ASDK user, I want to familiarize myself with the admin basics so my users can become productive as quickly as possible.
1311
# Keyword: asdk admin basics
@@ -16,22 +14,22 @@ ms.lastreviewed: 10/15/2019
1614

1715

1816
# ASDK admin basics
17+
1918
There are several things you need to know if you're new to Azure Stack Development Kit (ASDK) administration. This guidance provides an overview of your role as an Azure Stack operator in the evaluation environment. Familiarizing yourself with this info ensures your test users will become productive as quickly as possible.
2019

2120
First, you should review the [What is Azure Stack Development Kit?](asdk-what-is.md) article to make sure you understand the purpose of the ASDK and its limitations. You should use the development kit as a "sandbox," where you can evaluate Azure Stack to develop and test your apps in a non-production environment.
2221

2322
Like Azure, Azure Stack innovates rapidly so we'll regularly release new builds of the ASDK. However, you can't upgrade the ASDK like you can Azure Stack integrated systems deployments. So, if you want to move to the latest build, you must completely [redeploy the ASDK](asdk-redeploy.md). You can't apply update packages. This process takes time, but the benefit is that you can try out the latest features as soon as they become available.
2423

2524
## What account should I use?
25+
2626
There are a few account considerations you should be aware of when managing Azure Stack. This is especially true in deployments using Windows Server Active Directory Federation Services (AD FS) as the identity provider instead of Microsoft Entra ID. The following account considerations apply to both Azure Stack integrated systems and ASDK deployments:
2727

2828
|Account|Microsoft Entra ID|AD FS|
2929
|-----|-----|-----|
3030
|Local Admin (.\Administrator)|ASDK host admin|ASDK host admin|
3131
|AzureStack\AzureStackAdmin|ASDK host admin<br><br>Can be used to sign in to the Azure Stack administrator portal<br><br>Access to view and administer Service Fabric rings|ASDK host admin<br><br>No access to the Azure Stack administrator portal<br><br>Access to view and administer Service Fabric rings<br><br>No longer owner of the Default Provider Subscription (DPS)|
3232
|AzureStack\CloudAdmin|Can access and run permitted commands within the Privileged Endpoint|Can access and run permitted commands within the Privileged Endpoint<br><br>Can't sign in to the ASDK host<br><br>Owner of the Default Provider Subscription (DPS)|
33-
|Microsoft Entra Global Administrator|Used during installation<br><br>Owner of the Default Provider Subscription (DPS)|Not applicable|
34-
|
3533

3634
## What tools do I use to manage?
3735
You can use the Azure Stack administrator portal `https://adminportal.local.azurestack.external` or PowerShell to manage Azure Stack. The easiest way to learn the basic concepts is through the portal. If you want to use PowerShell, you need to install [PowerShell for Azure Stack](asdk-post-deploy.md#install-azure-stack-powershell) and [download the Azure Stack tools from GitHub](asdk-post-deploy.md#download-the-azure-stack-tools).

azure-stack/asdk/asdk-deploy-considerations.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,8 @@ description: Learn about the hardware, software, and environment requirements fo
44
author: sethmanheim
55

66
ms.topic: article
7-
ms.date: 09/23/2020
7+
ms.date: 08/19/2024
88
ms.author: sethm
9-
ms.reviewer: misainat
10-
ms.lastreviewed: 09/23/2020
119

1210
# Intent: As an ASDK user, I want to know the requirements for properly deploying the ASDK.
1311
# Keyword: asdk requirements
@@ -91,7 +89,7 @@ If your environment isn't connected to the internet, or you don't want to use Mi
9189
<a name='azure-active-directory-accounts'></a>
9290

9391
### Microsoft Entra accounts
94-
To deploy Azure Stack by using a Microsoft Entra account, you must prepare a Microsoft Entra account before you run the deployment PowerShell script. This account becomes the Global Admin for the Microsoft Entra tenant. It's used to provision and delegate apps and service principals for all Azure Stack services that interact with Microsoft Entra ID and Graph API. It's also used as the owner of the default provider subscription (which you can later change). You can sign in to your Azure Stack system's administrator portal by using this account.
92+
To deploy Azure Stack by using a Microsoft Entra account, you must prepare a Microsoft Entra account before you run the deployment PowerShell script. This account becomes the administrator for the Microsoft Entra tenant. It's used to provision and delegate apps and service principals for all Azure Stack services that interact with Microsoft Entra ID and Graph API. It's also used as the owner of the default provider subscription (which you can later change). You can sign in to your Azure Stack system's administrator portal by using this account.
9593

9694
1. Create a Microsoft Entra account that is the directory admin for at least one Microsoft Entra ID. If you already have one, you can use that. Otherwise, you can create one for free at [https://azure.microsoft.com/free/](https://azure.microsoft.com/free/) (in China, visit <https://go.microsoft.com/fwlink/?LinkID=717821> instead). If you plan to later [register Azure Stack with Azure](asdk-register.md), you must also have a subscription in this newly created account.
9795

@@ -100,13 +98,11 @@ To deploy Azure Stack by using a Microsoft Entra account, you must prepare a Mic
10098

10199
| **Microsoft Entra account** | **Supported?** |
102100
| --- | --- |
103-
| Work or school account with valid global Azure subscription |Yes |
104-
| Microsoft Account with valid global Azure subscription |Yes |
101+
| Work or school account with valid Azure subscription |Yes |
102+
| Microsoft Account with valid Azure subscription |Yes |
105103
| Work or school account with valid China Azure subscription |Yes |
106104
| Work or school account with valid US Government Azure subscription |Yes |
107105

108-
After deployment, Microsoft Entra global admin permission isn't required. However, some operations may require the global admin credential. Examples of such operations include a resource provider installer script or a new feature requiring a permission to be granted. You can either temporarily reinstate the account's global admin permissions or use a separate global admin account that's an owner of the *default provider subscription*.
109-
110106
## Network
111107
### Switch
112108
One available port on a switch for the ASDK machine.

azure-stack/asdk/asdk-deploy-powershell.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,8 @@ description: Learn how to deploy the ASDK from the command line using PowerShell
44
author: sethmanheim
55

66
ms.topic: article
7-
ms.date: 10/14/2020
7+
ms.date: 08/19/2024
88
ms.author: sethm
9-
ms.reviewer: misainat
10-
ms.lastreviewed: 10/14/2020
119

1210
# Intent: As an ASDK user, I want to deploy the ASDK using the command line in Powershell so I can evaluate Azure Stack features.
1311
# Keyword: deploy asdk command line
@@ -84,9 +82,7 @@ Run the following PowerShell commands to deploy the ASDK using Microsoft Entra I
8482
.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass.Password
8583
```
8684

87-
A few minutes into ASDK installation you'll be prompted for Microsoft Entra credentials. Provide the global admin credentials for your Microsoft Entra tenant.
88-
89-
After deployment, Microsoft Entra global admin permission isn't required. However, some operations may require the global admin credential. Examples of such operations include a resource provider installer script or a new feature requiring a permission to be granted. You can either temporarily reinstate the account's global admin permissions or use a separate global admin account that's an owner of the *default provider subscription*.
85+
A few minutes into ASDK installation you'll be prompted for Microsoft Entra credentials. Provide the Microsoft Entra admin credentials for your tenant.
9086

9187
### Deploy Azure Stack using AD FS
9288
To deploy the ASDK **using AD FS as the identity provider**, run the following PowerShell commands (you just need to add the -UseADFS parameter):
@@ -115,15 +111,15 @@ If your Microsoft Entra identity is only associated with **one** Microsoft Entra
115111
```powershell
116112
cd C:\CloudDeployment\Setup
117113
$adminpass = Get-Credential Administrator
118-
$aadcred = Get-Credential "<Azure AD global administrator account name>"
114+
$aadcred = Get-Credential "<Microsoft Entra administrator account name>"
119115
.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass.Password -InfraAzureDirectoryTenantAdminCredential $aadcred -TimeServer 52.168.138.145 #Example time server IP address.
120116
```
121117

122118
If your Microsoft Entra identity is associated with **greater than one** Microsoft Entra directory:
123119
```powershell
124120
cd C:\CloudDeployment\Setup
125121
$adminpass = Get-Credential Administrator
126-
$aadcred = Get-Credential "<Azure AD global administrator account name>" #Example: [email protected]
122+
$aadcred = Get-Credential "<Microsoft Entra administrator account name>" #Example: [email protected]
127123
.\InstallAzureStackPOC.ps1 -AdminPassword $adminpass.Password -InfraAzureDirectoryTenantAdminCredential $aadcred -InfraAzureDirectoryTenantName "<Azure AD directory in the form of domainname.onmicrosoft.com or an Azure AD verified custom domain name>" -TimeServer 52.168.138.145 #Example time server IP address.
128124
```
129125

0 commit comments

Comments
 (0)