+The Authentication methods policy is the recommended way to manage authentication methods, including modern methods like passwordless authentication. [Authentication Policy Administrators](../roles/permissions-reference.md#authentication-policy-administrator) can edit this policy to enable authentication methods for all users or specific groups.

+## Known issues and limitations

+- Some customers may see the control to enable Voice call grayed out due to a licensing requirement, despite having a premium license. This is a known issue that we are actively working to fix.

+- As a part of the public preview we removed the ability to target individual users. Previously targeted users will remain in the policy but we recommend moving them to a targeted group.

+| Support for device writeback|ΓùÅ |Customers should use [Cloud kerberose trust](https://learn.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust?tabs=intune) for this moving forward|

+We don't support selecting macOS or Linux device platforms when selecting **Require approved client app** or **Require app protection policy** as the only grant controls or when you choose **Require all the selected controls**.

+Conditional Access is widely used by our customers to stay secure by applying the right access controls in the right circumstances. However one of the challenges with deploying a Conditional Access policy in your organization is determining the impact to end users. It can be difficult to anticipate the number and names of users impacted by common deployment initiatives such as blocking legacy authentication, requiring multifactor authentication for a population of users, or implementing sign-in risk policies.

+- Conditional Access policies can be enabled in report-only mode, this isn't applicable with the "User Actions" scope.

+| Report-only: Success | All configured policy conditions, required non-interactive grant controls, and session controls were satisfied. For example, a multifactor authentication requirement is satisfied by an MFA claim already present in the token, or a compliant device policy is satisfied by performing a device check on a compliant device. |

+| Report-only: User action required | All configured policy conditions were satisfied but user action would be required to satisfy the required grant controls or session controls. With report-only mode, the user isn't prompted to satisfy the required controls. For example, users aren't prompted for multifactor authentication challenges or terms of use. |

+Administrators have the capability to create multiple policies in report-only mode, so it's necessary to understand both the individual impact of each policy and the combined impact of multiple policies evaluated together. The new Conditional Access Insights workbook enables administrators to visualize Conditional Access queries and monitor the impact of a policy for a given time range, set of applications, and users.

+If you haven't integrated Azure AD logs with Azure Monitor logs, you'll need to take the following steps before the workbook will load:

+**User action required**: The number of users or sign-ins during the time period where the combined result of the selected policies was ΓÇ£Report-only: User action requiredΓÇ¥. User action is required when an interactive grant control, such as multifactor authentication is required by a report-only Conditional Access policy. Since interactive grant controls aren't enforced by report-only policies, success or failure can't be determined.

+In order to access the workbook, you need the proper Azure AD permissions and Log Analytics workspace permissions. To test whether you have the proper workspace permissions by running a sample log analytics query:

+1. If the query doesn't return any results, your workspace may not have been configured correctly.

+Customers have noticed that queries sometimes fail if the wrong or multiple workspaces are associated with the workbook. To fix this problem, click **Edit** at the top of the workbook and then the Settings gear. Select and then remove workspaces that aren't associated with the workbook. There should be only one workspace associated with each workbook.

+You can save your parameter selections at the top of the workbook by going to **Azure Active Directory** > **Workbooks** > **Conditional Access Insights and reporting**. Here you'll find the workbook template, where you can edit the workbook and save a copy to your workspace, including the parameter selections, in **My reports** or **Shared reports**.

+You can edit and customize the workbook by going to **Azure Active Directory** > **Workbooks** > **Conditional Access Insights and reporting**. Here you'll find the workbook template, where you can edit the workbook and save a copy to your workspace, including the parameter selections, in **My reports** or **Shared reports**. To start editing the queries, click **Edit** at the top of the workbook.

+A web browser is required for interactive authentication. On iOS and macOS 10.15+, the Microsoft Authentication Library (MSAL) uses the system web browser by default (which might appear on top of your app) to do interactive authentication to sign in users. Using the system browser has the advantage of sharing the single sign-on (SSO) state with other applications and with web applications.

+- [SFAuthenticationSession](https://developer.apple.com/documentation/safariservices/sfauthenticationsession?language=objc)

+MSAL for macOS only supports `WKWebView` on older OS versions. `ASWebAuthenticationSession` is only supported on macOS 10.15 and above.

+By default, MSAL will dynamically detect iOS version and select the recommended system browser available on that version. On iOS 12+ it will be `ASWebAuthenticationSession`.

+| Version | Web browser |

+| :--: | :: |

+| iOS 11 | SFAuthenticationSession |

+| iOS 10 | SFSafariViewController |

+| Version | Web browser |

+| :: | :: |

+| macOS 10.15+ | ASWebAuthenticationSession |

+| other versions | WKWebView |

+## Cookie sharing and SSO implications

+| Technology | Browser Type | iOS availability | macOS availability | Shares cookies and other data | MSAL availability | SSO |

+| :--: | :-: | :--: | :-: | :: | :: | : |

+| [ASWebAuthenticationSession](https://developer.apple.com/documentation/authenticationservices/aswebauthenticationsession) | System | iOS12 and up | macOS 10.15 and up | Yes | iOS and macOS 10.15+ | w/ Safari instances |

+| [SFAuthenticationSession](https://developer.apple.com/documentation/safariservices/sfauthenticationsession) | System | iOS11 and up | N/A | Yes | iOS only | w/ Safari instances |

+| [SFSafariViewController](https://developer.apple.com/documentation/safariservices/sfsafariviewcontroller) | System | iOS11 and up | N/A | No | iOS only | No\*\* |

+| **SFSafariViewController** | System | iOS10 | N/A | Yes | iOS only | w/ Safari instances |

+| **WKWebView** | In-app | iOS8 and up | macOS 10.10 and up | No | iOS and macOS | No\*\* |

+\*\* For SSO to work, tokens need to be shared between apps. This requires a token cache, or broker application, such as Microsoft Authenticator for iOS.

+| Permission types | Delegated permissions | Application permissions |

+With an Azure AD joined device, your users already have an SSO experience to the cloud apps in your environment. If your environment has Azure AD and on-premises AD DS, you may want to expand the scope of your SSO experience to your on-premises Line Of Business (LOB) apps, file shares, and printers.

+Azure AD joined devices have no knowledge about your on-premises AD DS environment because they aren't joined to it. However, you can provide additional information about your on-premises AD to these devices with Azure AD Connect.

+If you have a hybrid environment, with both Azure AD and on-premises AD DS, it's likely that you already have Azure AD Connect or Azure AD Connect cloud sync deployed to synchronize your on-premises identity information to the cloud. As part of the synchronization process, on-premises user and domain information is synchronized to Azure AD. When a user signs in to an Azure AD joined device in a hybrid environment:

+- Access an AD DS member web server configured for Windows-integrated security

+- Apps and resources that depend on Active Directory machine authentication don't work because Azure AD joined devices don't have a computer object in AD DS.

+ - If applications use the NETBIOS or legacy name like contoso\user, the errors the application gets would be either, NT error STATUS_BAD_VALIDATION_CLASS - 0xc00000a7, or Windows error ERROR_BAD_VALIDATION_CLASS - 1348 ΓÇ£The validation information class requested was invalid.ΓÇ¥ This error happens even if you can resolve the legacy domain name.

+### Require multifactor authentication (MFA) to join devices

+

+| | Windows Hello for Business for Windows 10 or newer |

+This article provides information on how to troubleshoot and diagnose issues with Enterprise State Roaming, and provides a list of known issues.

+If you can't solve your issue with the guidance that follows, you can contact our support engineers. When you contact them, include the following information:

+1. After joining your Windows 10 or newer PC to a domain that is configured to allow Enterprise State Roaming, sign on with your work account. Go to **Settings** > **Accounts** > **Sync Your Settings** and confirm that sync and the individual settings are on, and that the top of the settings page indicates that you're syncing with your work account. Confirm the same account is also used as your login account in **Settings** > **Accounts** > **Your Info**.

+**Potential issue**: If the controls in the **Settings** page aren't available, and you see the message ΓÇ£Some Windows features are only available if you're using a Microsoft account or work account.ΓÇ¥ This issue might arise for devices that are set up to be domain-joined and registered to Azure AD, but the device hasn't yet successfully authenticated to Azure AD. A possible cause is that the device policy must be applied, but this application happens asynchronously, and could be delayed by a few hours.

+Enterprise State Roaming requires the device to be registered with Azure AD. Although not specific to Enterprise State Roaming, using the following instructions can help confirm that the Windows 10 or newer Client is registered, and confirm thumbprint, Azure AD settings URL, NGC status, and other information.

+**Potential issue**: **WamDefaultSet** and **AzureAdJoined** both have ΓÇ£NOΓÇ¥ in the field value, the device was domain-joined and registered with Azure AD, and the device doesn't sync. If it's showing this, the device may need to wait for policy to be applied or the authentication for the device failed when connecting to Azure AD. The user may have to wait a few hours for the policy to be applied. Other troubleshooting steps may include retrying autoregistration by signing out and back in, or launching the task in Task Scheduler. In some cases, running ΓÇ£*dsregcmd.exe /leave*ΓÇ¥ in an elevated command prompt window, rebooting, and trying registration again may help with this issue.

+**Potential issue**: The field for **SettingsUrl** is empty and the device doesn't sync. The user may have last logged in to the device before Enterprise State Roaming was enabled in the Azure Active Directory Portal. Restart the device and have the user login. Optionally, in the portal, try having the IT Admin navigate to **Azure Active Directory** > **Devices** > **Enterprise State Roaming** disable and re-enable **Users may sync settings and app data across devices**. Once re-enabled, restart the device and have the user login. If this doesn't resolve the issue, **SettingsUrl** may be empty if there's a bad device certificate. In this case, running ΓÇ£*dsregcmd.exe /leave*ΓÇ¥ in an elevated command prompt window, rebooting, and trying registration again may help with this issue.

+## Enterprise State Roaming and multifactor authentication

+Under certain conditions, Enterprise State Roaming can fail to sync data if Azure AD Multifactor Authentication is configured. For more information on these symptoms, see the support document [KB3193683](https://support.microsoft.com/kb/3193683).

+**Potential issue**: If your device is configured to require Multifactor Authentication on the Azure Active Directory portal, you may fail to sync settings while signing in to a Windows 10 or newer device using a password. This type of Multifactor Authentication configuration is intended to protect an Azure administrator account. Admin users may still be able to sync by signing in to their Windows 10 or newer devices with their Windows Hello for Business PIN or by completing Multifactor Authentication while accessing other Azure services like Microsoft 365.

+**Potential issue**: Sync can fail if the admin configures the Active Directory Federation Services Multifactor Authentication Conditional Access policy and the access token on the device expires. Ensure that you sign in and sign out using the Windows Hello for Business PIN or complete Multifactor Authentication while accessing other Azure services like Microsoft 365.

+Devices that are domain-joined won't experience sync for the setting Date, Time, and Region: automatic time. Using automatic time may override the other Date, Time, and Region settings and cause those settings not to sync.

+The user will need to unjoin and rejoin the device to the cloud. To do this, login as the Local Administrator user and unjoin the device by going to **Settings** > **System** > **About** and select "Manage or disconnect from work or school". Clean up the following files, and then Azure AD Join the device again in **Settings** > **System** > **About** and selecting "Connect to Work or School". Continue to join the device to Azure Active Directory and complete the flow.

+In Event Viewer under the SettingSync/Debug logs, this error can be seen when the user's credentials have expired. In addition, it can occur when the tenant didn't automatically have AzureRMS provisioned.

+In Event Viewer under the AAD/Operational logs, this error may be seen with `Event 1104: AAD Cloud AP plugin call Get token returned error: 0xC000005F`. This issue occurs if there are missing permissions or ownership attributes.

+For an overview, see [enterprise state roaming overview](enterprise-state-roaming-overview.md).

+Scenarios that break without line of sight to your domain controllers include:

+- Any existing Azure AD registered state for a user would be automatically removed <i>after the device is hybrid Azure AD joined and the same user logs in</i>. For example, if User A had an Azure AD registered state on the device, the dual state for User A is cleaned up only when User A logs in to the device. If there are multiple users on the same device, the dual state is cleaned up individually when those users log in. After an admin removes the Azure AD registered state, Windows 10 will unenroll the device from Intune or other MDM, if the enrollment happened as part of the Azure AD registration via auto-enrollment.

+- Routable users UPN: A routable UPN has a valid verified domain that is registered with a domain registrar. For example, if contoso.com is the primary domain in Azure AD, contoso.org is the primary domain in on-premises AD owned by Contoso and [verified in Azure AD](../fundamentals/add-custom-domain.md).

+- Hybrid Azure AD join for downlevel Windows devices works slightly differently than it does in Windows 10 or newer. Many customers don't realize that they need AD FS (for federated domains) or Seamless SSO configured (for managed domains).

+- For customers with federated domains, if the Service Connection Point (SCP) was configured such that it points to the managed domain name (for example, contoso.onmicrosoft.com, instead of contoso.com), then Hybrid Azure AD Join for downlevel Windows devices won't work.

+- Make sure [KB4284842](https://support.microsoft.com/help/4284842) is installed on Windows 7 SP1 or Windows Server 2008 R2 SP1. This update prevents future authentication failures due to customer's access loss to protected keys after changing password.

+- Hybrid Azure AD join may fail after a user has their UPN changed, breaking the Seamless SSO authentication process. During the join process, you may see that it's still sending the old UPN to Azure AD, unless, browser session cookies are cleared or user explicitly signs-out and removes old UPN.

+If the device wasn't hybrid Azure AD joined, you can attempt to do hybrid Azure AD join by clicking on the "Join" button. If the attempt to do hybrid Azure AD join fails, the details about the failure will be shown.

+ - Autoworkplace.exe is unable to silently authenticate with Azure AD or AD FS. This issue could be caused by missing or misconfigured AD FS (for federated domains) or missing or misconfigured Azure AD Seamless Single Sign-On (for managed domains) or network issues.

+ - It could be that multifactor authentication (MFA) is enabled/configured for the user and WIAORMULTIAUTHN isn't configured at the AD FS server.

+ - If your organization uses Azure AD Seamless Single Sign-On, `https://autologon.microsoftazuread-sso.com` or `https://aadg.windows.net.nsatc.net` aren't present on the device's IE intranet settings.

+- You aren't signed on as a domain user

+ There are a few different reasons why this issue can occur:

+ - The signed in user isn't a domain user (for example, a local user). Hybrid Azure AD join on down-level devices is supported only for domain users.

+ - The client isn't able to connect to a domain controller.

+- The service isn't responding

+ :::image type="content" source="./media/troubleshoot-hybrid-join-windows-legacy/05.png" alt-text="Screenshot of the Workplace Join for Windows dialog box. Text reports that an error occurred because the server didn't respond." border="false":::

+- Your computer isn't connected to your organizationΓÇÖs internal network or to a VPN with a connection to your on-premises AD domain controller.

+- You're logged on to your computer with a local computer account.

+ - The AD FS server hasn't been configured to support **WIAORMULTIAUTHN**.

+ - Or if your domain is managed, then Seamless SSO wasn't configured or working.

+>[!NOTE]

+> The columns downloaded are pre-defined

+All Azure subscriptions have a trust relationship with an Azure Active Directory (Azure AD) instance. Subscriptions rely on their trusted Azure AD to authenticate and authorize security principals and devices. When a subscription expires, the trusted instance of the Azure AD service remains, but the security principals lose access to Azure resources. Subscriptions can only trust a single directory while one Azure AD may be trusted by multiple subscriptions.

+While users may only have a single authentication *home* directory, users may participate as guests in multiple directories. You can see both the home and guest directories for each user in Azure AD.

+> When a subscription is associated with a different directory, users who have roles assigned using [Azure role-based access control](../../role-based-access-control/role-assignments-portal.md) lose their access. Classic subscription administrators, including Service Administrator and Co-Administrators, also lose access.

+Before you can associate or add your subscription, do the following steps:

+- Review the following list of changes that will occur after you associate or add your subscription, and how you might be affected:

+ - Users that have been assigned roles using Azure RBAC will lose their access.

+ - Service Administrator and Co-Administrators will lose access.

+ - If you have any key vaults, they'll be inaccessible, and you'll have to fix them after association.

+ - If you have any managed identities for resources such as Virtual Machines or Logic Apps, you must re-enable or recreate them after the association.

+ - If you have a registered Azure Stack, you'll have to re-register it after association.

+

+ For more information, see [Transfer an Azure subscription to a different Azure AD directory](../../role-based-access-control/transfer-subscription.md).

+ - Has an [Owner](../../role-based-access-control/built-in-roles.md#owner) role assignment for the subscription. For information about how to assign the Owner role, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.md).

+ - Exists in both the current directory and in the new directory. The current directory is associated with the subscription. You'll associate the new directory with the subscription. For more information about getting access to another directory, see [Add Azure Active Directory B2B collaboration users in the Azure portal](../external-identities/add-users-administrator.md).

+ - Make sure that you're not using an Azure Cloud Service Providers (CSP) subscription (MS-AZR-0145P, MS-AZR-0146P, MS-AZR-159P), a Microsoft Internal subscription (MS-AZR-0015P), or a Microsoft Azure for Students Starter subscription (MS-AZR-0144P).

+To associate an existing subscription with your Azure AD, follow these steps:

+After you associate a subscription with a different directory, you might need to do the following tasks to resume operations:

+Azure subscriptions have a trust relationship with Azure Active Directory (Azure AD). Azure AD is trusted to authenticate the subscription's users, services, and devices. Each subscription has a tenant ID associated with it, and there are a few ways you can find the tenant ID for your subscription.

+1. Scroll down to the **Tenant ID** section and you can find your tenant ID in the box.

+For more information, see the [Get-AzTenant](/powershell/module/az.accounts/get-aztenant) cmdlet reference.

+For Azure CLI, use one of the commands **az login**, **az account list**, or **az account tenant list**. All of command's included below return the **tenantId** property for each of your subscriptions.

+Azure Active Directory (Azure AD) administrators can reset a user's password if the password is forgotten, if the user gets locked out of a device, or if the user never received a password.

+>If you're not an administrator and you need instructions on how to reset your own work or school password, see [Reset your work or school password](https://support.microsoft.com/account-billing/reset-your-work-or-school-password-using-security-info-23dde81f-08bb-4776-ba72-e6b72b9dda9e).

+> If an administrator is unable to reset the user's password, and the Application Event Logs on the Azure AD Connect server has error code hr=80231367, review the user's attributes in Active Directory. If the attribute **AdminCount** is set to 1, this will prevent an administrator from resetting the user's password. The attribute **AdminCount** must be set to 0, in order for an administrators to reset the user's password.

+Azure Active Directory (Azure AD) is a cloud-based identity and access management service. Azure AD enables your employees access external resources, such as Microsoft 365, the Azure portal, and thousands of other SaaS applications. Azure Active Directory also helps them access internal resources like apps on your corporate intranet, and any cloud apps developed for your own organization. To learn how to create a tenant, see [Quickstart: Create a new tenant in Azure Active Directory](active-directory-access-create-new-tenant.md).

+Azure AD provides different benefits to members of your organization based on their role:

+- **IT admins** use Azure AD to control access to apps and app resources, based on business requirements. For example, as an IT admin, you can use Azure AD to require multi-factor authentication when accessing important organizational resources. You could also use Azure AD to automate user provisioning between your existing Windows Server AD and your cloud apps, including Microsoft 365. Finally, Azure AD gives you powerful tools to automatically help protect user identities and credentials and to meet your access governance requirements. To get started, sign up for a [free 30-day Azure Active Directory Premium trial](https://azure.microsoft.com/trial/get-started-active-directory/).

+- **App developers** can use Azure AD as a standards-based authentication provider that helps them add single sign-on (SSO) to apps that works with a user's existing credentials. Developers can also use Azure AD APIs to build personalized experiences using organizational data. To get started, sign up for a [free 30-day Azure Active Directory Premium trial](https://azure.microsoft.com/trial/get-started-active-directory/). For more information, you can also see [Azure Active Directory for developers](../develop/index.yml).

+- **Microsoft 365, Office 365, Azure, or Dynamics CRM Online subscribers** already use Azure AD as every Microsoft 365, Office 365, Azure, and Dynamics CRM Online tenant is automatically an Azure AD tenant. You can immediately start managing access to your integrated cloud apps.

+Microsoft Online business services, such as Microsoft 365 or Microsoft Azure, use Azure AD for sign-in activities and to help protect your identities. If you subscribe to any Microsoft Online business service, you automatically get access to [Azure AD free](https://www.microsoft.com/security/business/identity-access/azure-active-directory-pricing).

+To enhance your Azure AD implementation, you can also add paid features by upgrading to Azure Active Directory Premium P1 or Premium P2 licenses. Azure AD paid licenses are built on top of your existing free directory. The licenses provide self-service, enhanced monitoring, security reporting, and secure access for your mobile users.

+- **"Pay as you go" feature licenses.** You can also get licenses for features such as, Azure Active Directory Business-to-Customer (B2C). B2C can help you provide identity and access management solutions for your customer-facing apps. For more information, see [Azure Active Directory B2C documentation](../../active-directory-b2c/index.yml).

+After you choose your Azure AD license, you'll get access to some or all of the following features:

+Azure Active Directory (Azure AD) tenants come with an initial domain name, *\<domainname>.onmicrosoft.com*. You can't change or delete the initial domain name, but you can add your organization's names. Adding custom domain names helps you to create user names that are familiar to your users, such as *alain\@contoso.com*.

+ >You must include *.com*, *.net*, or any other top-level extension for this to work. When adding a custom domain, the Password Policy values will be inherited from the initial domain.

+- **If you are trying to verify a child domain, verify the parent domain first.** Make sure the parent domain is created and verified first before you try to verify a child domain.

+There are several Azure AD license plans:

+Anyone who has a business need to use a licensed Azure AD service must have the required licenses. You can add licensing rights to users or to an entire group.

+Exceptions to these common parameters are the `Set-ADSyncRestrictedPermissions` cmdlet which is used to set the permissions on the AD DS Connector Account itself, and the `Set-ADSyncPasswordHashSyncPermissions` cmdlet since the permissions required for Password Hash Sync are only set at the domain root, hence this cmdlet does not include the `-ObjectDN` or `-IncludeAdminSdHolders` parameters.

+Set-ADSyncBasicReadPermissions -ADConnectorAccountName <String> -ADConnectorAccountDomain <String> [-IncludeAdminSdHolders] [<CommonParameters>]

+Set-ADSyncMsDsConsistencyGuidPermissions -ADConnectorAccountName <String> -ADConnectorAccountDomain <String> [-IncludeAdminSdHolders] [<CommonParameters>]

+Set-ADSyncPasswordWritebackPermissions -ADConnectorAccountName <String> -ADConnectorAccountDomain <String> [-IncludeAdminSdHolders] [<CommonParameters>]

+Set-ADSyncUnifiedGroupWritebackPermissions -ADConnectorAccountName <String> -ADConnectorAccountDomain <String> [-IncludeAdminSdHolders] [<CommonParameters>]

+Set-ADSyncExchangeHybridPermissions -ADConnectorAccountName <String> -ADConnectorAccountDomain <String> [-IncludeAdminSdHolders] [<CommonParameters>]

+Set-ADSyncExchangeMailPublicFolderPermissions -ADConnectorAccountName <String> -ADConnectorAccountDomain <String> [-IncludeAdminSdHolders] [<CommonParameters>]

+Azure AD stores reports and security signals for a defined period of time. When it comes to risk information that period may not be long enough.

+In the previous image, the following query was run to show the most recent five risk detections triggered.

+Microsoft Applications (like Exchange, SharePoint, Yammer, etc.) are assigned and managed a bit differently than third-party SaaS applications or other applications you integrate with Azure AD for single sign-on.

+- For applications that Microsoft or a third-party publishes freely for anyone to use, users may also be granted access through **administrator consent**. This means that an administrator has determined the application may be used by everyone in the organization, so they sign in to the application with a Global Administrator account and grant access to everyone in the organization.

+Following are some common issues folks run into when their users can't sign in to a Microsoft application.

+ * Make sure **Multi-Factor Authentication** isn't blocking user access. [Check a userΓÇÖs multi-factor authentication status](#check-a-users-multi-factor-authentication-status) or [Check a userΓÇÖs authentication contact info](#check-a-users-authentication-contact-info)

+ * Make sure a **Conditional Access policy** or **Identity Protection** policy isn't blocking user access. [Check a specific Conditional Access policy](#problems-with-conditional-access-policies) or [Check a specific applicationΓÇÖs Conditional Access policy](#check-a-specific-applications-conditional-access-policy) or [Disable a specific Conditional Access policy](#disable-a-specific-conditional-access-policy)

+- For **Microsoft** **applications that require a license** (like Office365), here are some specific issues to check once you've ruled out the general issues above:

+ * Make sure the license is **for the application** they're accessing.

+6. **Search** for the user you're interested in and **click the row** to select.

+6. **Search** for the user you're interested in and **click the row** to select.

+6. **Search** for the user you're interested in and **click the row** to select.

+10. Communicate this new password to the user, they be required to change this password during their next sign-in to Azure Active Directory.

+ * **Note**: If a user is in an **Enforced** state, you may set them to **Disabled** temporarily to let them back into their account. Once they're back in, you can then change their state to **Enabled** again to require them to re-register their contact information during their next sign-in. Alternatively, you can follow the steps in the [Check a userΓÇÖs authentication contact info](#check-a-users-authentication-contact-info) to verify or set this data for them.

+6. **Search** for the user you're interested in and **click the row** to select.

+6. **Search** for the user you're interested in and **click the row** to select.

+6. **Search** for the user you're interested in and **click the row** to select.

+6. **Search** for the user you're interested in and **click the row** to select.

+10. **Optional** select the **assignment options** item to granularly assign products. Select **Ok** when this is completed.

+6. **Search** for the group you're interested in and **click the row** to select.

+6. **Search** for the group you're interested in and **click the row** to select.

+6. **Search** for the group you're interested in and **click the row** to select.

+6. **Search** for the group you're interested in and **click the row** to select.

+6. **Search** for the group you're interested in and **click the row** to select.

+10. **Optional** select the **assignment options** item to granularly assign products. Select **Ok** when this is completed.

+6. Select the policy you're interested in inspecting.

+6. Search for the application you're interested in, or the user is attempting to sign in to by application display name or application ID.

+8. Select the policy you're interested in inspecting.

+9. Review that there are no specific conditions, assignments, or other settings that may be blocking user access.

+6. Select the policy you're interested in inspecting.

+7. Disable the policy by setting the **Enable policy** toggle to **No** and select the **Save** button.

+Application access can be blocked because the proper permissions consent operation hasn't occurred. Following are some ways you can troubleshoot and solve application consent issues:

+- For any Open ID Connect-enabled application that requests permissions, navigating to the applicationΓÇÖs sign-in screen performs a user level consent to the application for the signed-in user.

+- For **only applications developed using the V1 application model**, you can force this administrator level consent to occur by adding ΓÇ£**?prompt=admin\_consent**ΓÇ¥ to the end of an applicationΓÇÖs sign-in URL.

+- For **single-tenant applications** that request permissions (like those you're developing or own in your organization), you can perform an **administrative-level consent** operation on behalf of all users by signing in as a Global Administrator and clicking on the **Grant permissions** button at the top of the **Application Registry -&gt; All Applications -&gt; Select an App -&gt; Required Permissions** pane.

+This article discusses errors that can occur during the process of consenting to an application. If you're troubleshooting unexpected consent prompts that don't contain any error messages, see [Authentication Scenarios for Azure AD](../develop/authentication-vs-authorization.md).

+Many applications that integrate with Azure Active Directory require permissions to access other resources in order to function. When these resources are also integrated with Azure Active Directory, the permission to access them is often requested using the common consent framework. A consent prompt is displayed, which generally occurs the first time an application is used but can also occur on a subsequent use of the application.

+Certain conditions must be true for a user to consent to the permissions an application requires. If these conditions aren't met, the following errors can occur.

+* **AADSTS90093:** &lt;clientAppDisplayName&gt; is requesting one or more permissions that you aren't authorized to grant. Contact an administrator, who can consent to this application on your behalf.

+* **AADSTS90094:** &lt;clientAppDisplayName&gt; needs permission to access resources in your organization that only an admin can grant. Ask an admin to grant permission to this app before you can use it.

+This error occurs when a user who isn't a Global Administrator attempts to use an application that is requesting permissions that only an administrator can grant. This error can be resolved by an administrator granting access to the application on behalf of their organization.

+* **AADSTS90093:** An administrator of &lt;tenantDisplayName&gt; has set a policy that prevents you from granting &lt;name of app&gt; the permissions it's requesting. Contact an administrator of &lt;tenantDisplayName&gt;, who can grant permissions to this app on your behalf.

+* **AADSTS65005:** &lt;clientAppDisplayName&gt; is requesting access to a resource &lt;resourceAppDisplayName&gt; that isn't available in your organization &lt;tenantDisplayName&gt;.

+Ensure that these resources that provide the permissions requested are available in your tenant or contact an administrator of &lt;tenantDisplayName&gt;. Otherwise, there's a misconfiguration in how the application requests resources, and you should contact the application developer.

+* **AADSTS65005:** The app requested consent to access resource &lt;resourceAppDisplayName&gt;. This request failed because it doesn't match how the app was pre-configured during app registration. Contact the app vendor.**

+These errors all occur when the application a user is trying to consent to is requesting permissions to access a resource application that can't be found in the organizationΓÇÖs directory (tenant). This situation can occur for several reasons:

+* A Service Principal representing the target resource application doesn't exist in the organization, or existed in the past but has been removed. To resolve this issue, a Service Principal for the resource application must be provisioned in the organization so the client application can request permissions to it. The Service Principal can be provisioned in many ways, depending on the type of application, including:

+* This app may be risky. If you trust this app, ask your admin to grant you access.

+Both of these messages will be displayed when Microsoft has determined that the consent request may be risky. Among many other factors, this may occur if a [verified publisher](../develop/publisher-verification-overview.md) hasn't been added to the app registration. The first error code and message will be shown to end-users when the [Admin consent workflow](configure-admin-consent-workflow.md) is disabled. The second code and message will be shown to end-users when the admin consent workflow is enabled and to admins.

+End-users won't be able to grant consent to apps that have been detected as risky. Admins are able to, but should evaluate the app carefully and proceed with caution. If the app seems suspicious upon further review, it can be reported to Microsoft from the consent screen.

+description: How to troubleshoot when a user sees a consent prompt for an application you've integrated with Azure AD that you didn't expect

+Many applications that integrate with Azure Active Directory require permissions to various resources in order to run. When these resources are also integrated with Azure Active Directory, the permission to access them is requested using the Azure AD consent framework. These requests result in a consent prompt being shown the first time an application is used, which is often a one-time operation.

+In certain scenarios, additional consent prompts can appear when a user attempts to sign-in. In this article, we'll diagnose the reason for the unexpected consent prompts showing, and how to troubleshoot.

+* The application has been configured to require assignment. Individual user consent isn't currently supported for apps that require assignment; thus the permissions must be granted by an admin for the whole directory. If you configure an application to require assignment, be sure to also grant tenant-wide admin consent so that assigned user can sign-in.

+* The user who originally consented to the application wasn't an administrator, and now a different (non-admin) user is using the application for the first time.

+* The developer has configured the application to require a consent prompt every time it's used (note: this behavior isn't best practice).

+6. To view the requested permissions, select the **Grant admin consent** button. (NOTE: This will open a consent prompt listing all of the requested permissions. Don't click accept on the consent prompt unless you're sure you want to grant tenant-wide admin consent.)

+There may be situations while configuring or managing an application where you don't want tokens to be issued for an application. Or, you may want to block an application that you don't want your employees to try to access. To block user access to an application, you can disable user sign-in for the application, which will prevent all tokens from being issued for that application.

+In this article, you'll learn how to prevent users from signing in to an application in Azure Active Directory through both the Azure portal and PowerShell. If you're looking for how to block specific users from accessing an application, use [user or group assignment](./assign-user-or-group-access-portal.md).

+Ensure you've installed the AzureAD module (use the command Install-Module -Name AzureAD). In case you're prompted to install a NuGet module or the new Azure Active Directory V2 PowerShell module, type Y and press ENTER.

+You may know the AppId of an app that doesn't appear on the Enterprise apps list. For example, you may have deleted the app or the service principal hasn't yet been created due to the app being pre-authorized by Microsoft), you can manually create the service principal for the app and then disable it by using the following cmdlet.

+### Free and Standard pricing tiers for AKS control plane management

+This cluster has not enabled the Standard pricing tier with the Uptime SLA feature, and is limited to an SLO of 99.5%.

+Learn more about [Kubernetes service - UseUptimeSLA (Use Uptime SLA)](../aks/free-standard-pricing-tiers.md).

+AKS patches CVEs that have a "vendor fix" every week. CVEs without a fix are waiting on a "vendor fix" before it can be remediated. The AKS images will get automatically updated inside of 30 days. We recommend you apply an updated Node Image on a regular cadence to ensure that latest patched images and OS patches are all applied and current. You can do this using one of the following methods:

+AKS does not set a limit on the container image size. However, it is important to understand that the larger the image, the higher the memory demand. A larger size could potentially exceed resource limits or the overall available memory of worker nodes. By default, memory for VM size Standard_DS2_v2 for an AKS cluster is set to 7 GiB.

+AKS builds upon many Azure infrastructure resources, including Virtual Machine Scale Sets, virtual networks, and managed disks, which enables you to apply many of the core capabilities of the Azure platform within the managed Kubernetes environment provided by AKS. For example, most Azure virtual machine types can be used directly with AKS and Azure Reservations can be used to receive discounts on those resources automatically.

+2. The second resource group, known as the *node resource group*, contains all of the infrastructure resources associated with the cluster. These resources include the Kubernetes node VMs, virtual networking, and storage. By default, the node resource group has a name like *MC_myResourceGroup_myAKSCluster_eastus*. AKS automatically deletes the node resource group whenever the cluster is deleted, so it should only be used for resources that share the cluster's lifecycle.

+To specify your own resource group name, install the [aks-preview][aks-preview-cli] Azure CLI extension version *0.3.2* or later. When you create an AKS cluster by using the [`az aks create`][az-aks-create] command, use the `--node-resource-group` parameter and specify a name for the resource group. If you [use an Azure Resource Manager template][aks-rm-template] to deploy an AKS cluster, you can define the resource group name by using the *nodeResourceGroup* property.

+If you modify or delete Azure-created tags and other resource properties in the node resource group, you could get unexpected results, such as scaling and upgrading errors. AKS allows you to create and modify custom tags created by end users, and you can add those tags when [creating a node pool](use-multiple-node-pools.md#specify-a-taint-label-or-tag-for-a-node-pool). You might want to create or modify custom tags, for example, to assign a business unit or cost center. Another option is to create Azure Policies with a scope on the managed resource group.

+Yes, you may use admission controller webhooks on AKS. It's recommended you exclude internal AKS namespaces, which are marked with the **control-plane label.** For example:

+If you have a critical use case for deploying something on kube-system (not recommended) in support of your custom admission webhook, you may add the following label or annotation so that Admissions Enforcer ignores it.

+AKS provides SLA guarantees in the [Standard pricing tier with the Uptime SLA feature][pricing-tiers].

+The Free pricing tier doesn't have an associated Service Level *Agreement*, but has a Service Level *Objective* of 99.5%. Transient connectivity issues are observed if there was an upgrade, unhealthy underlay nodes, platform maintenance, or an application overwhelms the API Server with requests, etc. For mission-critical and production workloads, or if your workload doesn't tolerate API Server restarts, we recommend using the Standard tier, which includes Uptime SLA.

+You can, but we don't recommend it. Upgrades should be performed when the state of the cluster is known and healthy.

+## Can I use the Virtual Machine Scale Set APIs to scale manually?

+No, scale operations by using the Virtual Machine Scale Set APIs aren't supported. Use the AKS APIs (`az aks scale`).

+## Can I use Virtual Machine Scale Sets to manually scale to zero nodes?

+No, scale operations by using the Virtual Machine Scale Set APIs aren't supported. You can use the AKS API to scale to zero non-system node pools or [stop your cluster](start-stop-cluster.md) instead.

+The following example shows what the ip route setup looks like in Bridge mode. Regardless of how many pods the node has, there will only ever be two routes. The first one saying, all traffic excluding local on azure0 will go to the default gateway of the subnet through the interface with ip "src 10.240.0.4" (which is Node primary IP) and the second one saying "10.20.x.x" Pod space to kernel for kernel to decide.

+The following example shows a ip route setup of transparent mode. Each Pod's interface will get a static route attached so that traffic with dest IP as the Pod will be sent directly to the Pod's host side `veth` pair interface.

+FIPS-enabled nodes are now supported on Linux-based node pools. For more information, see [Add a FIPS-enabled node pool](use-multiple-node-pools.md#add-a-fips-enabled-node-pool).

+## How does Time synchronization work in AKS?

+AKS nodes run the "chrony" service, which pulls time from the localhost. Containers running on pods get the time from the AKS nodes. Applications launched inside a container use time from the container of the pod.

+[pricing-tiers]: ./free-standard-pricing-tiers.md

+ Title: Azure Kubernetes Service (AKS) Free and Standard pricing tiers for control plane management

+description: Learn about the Azure Kubernetes Service (AKS) Free and Standard pricing tiers for control plane management

+# Free and Standard pricing tiers for Azure Kubernetes Service (AKS) control plane management

+Azure Kubernetes Service (AKS) is now offering two pricing tiers for control plane management: the **Free tier** and the **Standard tier**.

+| |Free tier|Standard tier|

+|||--|

+|**When to use**|ΓÇó You want to experiment with AKS at no extra cost <br> ΓÇó You're new to AKS and Kubernetes|ΓÇó You're running production or mission-critical workloads and need high availability and reliability <br> ΓÇó You need a financially backed SLA|

+|**Supported cluster types**|ΓÇó Development clusters or small scale testing environments <br> ΓÇó Clusters with fewer than 10 nodes|ΓÇó Enterprise-grade or production workloads <br> ΓÇó Clusters with up to 5,000 nodes|

+|**Pricing**|ΓÇó Free cluster management <br> ΓÇó Pay-as-you-go for resources you consume|ΓÇó Pay-as-you-go for resources you consume|

+|**Feature comparison**|ΓÇó Recommended for clusters with fewer than 10 nodes, but can support up to 1,000 nodes <br> ΓÇó Includes all current AKS features|ΓÇó Uptime SLA is enabled by default <br> ΓÇó Greater control plane reliability and resources <br> ΓÇó Can support up to 5,000 nodes in a cluster <br> ΓÇó Includes all current AKS features

+For more information on pricing, see the [AKS pricing details](https://azure.microsoft.com/pricing/details/kubernetes-service/).

+## Uptime SLA

+> [!IMPORTANT]

+>

+> Uptime SLA has been repositioned as a default feature included with the Standard tier.

+>

+> The repositioning will result in the following API changes:

+>

+> | |Prior to 2023-01-01 API|Starting from 2023-01-01 API| Starting from 2023-07-01 API|

+> |-|--|||

+> |ManagedClusterSKUName|"Basic"|"Basic" <br> "Base"|"Base"|

+> |ManagedClusterSKUTier|"Free" <br> "Paid"|"Free" <br> "Paid" <br> "Standard"|"Free" <br> "Standard"|

+>

+> "Basic" and "Paid" will be removed in the 2023-07-01 API version, and this will be a breaking change in API version 2023-07-01 or newer. If you use automated scripts, CD pipelines, ARM templates, Terraform, or other third-party tooling that relies on the above parameters, please be sure to make the necessary changes before upgrading to the 2023-07-01 or newer API version. From API version 2023-01-01 and newer, you can start transitioning to the new API parameters "Base" and "Standard".

+>

+For more information, see [SLA for AKS](https://azure.microsoft.com/support/legal/sla/kubernetes-service/v1_1/).

+### Uptime SLA terms and conditions

+The Uptime SLA feature is included in the Standard tier and is enabled per cluster. For more information on pricing, see the [AKS pricing details](https://azure.microsoft.com/pricing/details/kubernetes-service/).

+## Region availability

+* Uptime SLA is available in public regions and Azure Government regions where [AKS is supported](https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service).

+* Uptime SLA is available for [private AKS clusters][private-clusters] in all public regions where AKS is supported.

+## Before you begin

+[Azure CLI](/cli/azure/install-azure-cli) version 2.8.0 or later and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].

+## Creating a new cluster in the Free tier or Standard tier

+Use the Azure CLI to create a new cluster on an AKS pricing tier. You can create your cluster in an existing resource group or create a new one. To learn more about resource groups and working with them, see [managing resource groups using the Azure CLI][manage-resource-group-cli].

+Use the [`az aks create`][az-aks-create] command to create an AKS cluster. The commands below show you how to create a new resource group named *myResourceGroup* and a cluster named *myAKSCluster* in that resource group in each tier.

+```azurecli-interactive

+# Create a new AKS cluster in the Free tier

+az aks create --resource-group myResourceGroup --name myAKSCluster --no-uptime-sla

+# Create a new AKS cluster in the Standard tier

+az aks create --resource-group myResourceGroup --name myAKSCluster --uptime-sla

+```

+> [!NOTE]

+>

+> The outputs to `--no-uptime-sla` and `--uptime-sla` correspond to API properties prior to the 2023-01-01 API version. Starting in Azure CLI 2.46.0:

+>

+> * `--tier free` will correspond to the existing `--no-uptime-sla` parameter.

+> * `--tier standard` will correspond to the existing `--uptime-sla` parameter.

+> * The CLI output "Basic" for ManagedClusterSKUName will correspond to the API property: "Base".

+> * The CLI output "Free" or "Paid" for ManagerClusterSKUTier will correspond to the API properties: "Free" or "Standard".

+Once the deployment completes, it returns JSON-formatted information about your cluster:

+```output

+# Sample output for `--no-uptime-sla`

+ },

+ "sku": {

+ "name": "Basic",

+ "tier": "Free"

+ },

+# Sample output for `uptime-sla`

+ },

+ "sku": {

+ "name": "Basic",

+ "tier": "Paid"

+ },

+```

+## Update the tier of an existing cluster

+The following example uses the [`az aks update`][az-aks-update] command to update the existing cluster.

+```azurecli-interactive

+# Update an existing cluster to the Free tier

+az aks update --resource-group myResourceGroup --name myAKSCluster --no-uptime-sla

+# Update an existing cluster to the Standard tier

+az aks update --resource-group myResourceGroup --name myAKSCluster --uptime-sla

+```

+This process takes several minutes to complete. When finished, the following example JSON snippet shows the paid tier for the SKU, indicating your cluster is enabled with Uptime SLA.

+```output

+ },

+ "sku": {

+ "name": "Basic",

+ "tier": "Paid"

+ },

+```

+## Next steps

+* Use [Availability Zones][availability-zones] to increase high availability with your AKS cluster workloads.

+* Configure your cluster to [limit egress traffic](limit-egress-traffic.md).

+<!-- LINKS - External -->

+[azure-support]: https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest

+[region-availability]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service

+<!-- LINKS - Internal -->

+[vm-skus]: ../virtual-machines/sizes.md

+[paid-sku-tier]: /rest/api/aks/managed-clusters/create-or-update#managedclusterskutier

+[nodepool-upgrade]: use-multiple-node-pools.md#upgrade-a-node-pool

+[manage-resource-group-cli]: ../azure-resource-manager/management/manage-resource-groups-cli.md

+[faq]: ./faq.md

+[availability-zones]: ./availability-zones.md

+[az-aks-create]: /cli/azure/aks?#az_aks_create

+[limit-egress-traffic]: ./limit-egress-traffic.md

+[az-extension-add]: /cli/azure/extension#az_extension_add

+[az-extension-update]: /cli/azure/extension#az_extension_update

+[az-aks-update]: /cli/azure/aks#az_aks_update

+[az-group-delete]: /cli/azure/group#az_group_delete

+[private-clusters]: private-clusters.md

+[install-azure-cli]: /cli/azure/install-azure-cli

+If your AKS clusters satisfy any of the following criteria, we recommend using the [Standard tier that comes with the Uptime SLA feature][standard-tier] for higher reliability and scalability of the Kubernetes control plane:

+* Clusters running production workloads or availability-sensitive, mission-critical workloads

+To scale AKS clusters beyond 1000 nodes, you need to request a node limit quota increase by raising a support ticket in the [Azure portal][Azure portal] up to a maximum of 5000 nodes per cluster. Increasing the node limit doesn't increase other AKS service quota limits, like the number of pods per node. For more information, see [Limits, quotas, and restrictions for AKS resources][quotas-skus-regions].

+* Clusters using the Standard tier.

+[standard-tier]: free-standard-pricing-tiers.md

+1. Check that the new Application Insights logger now appears in the list.

+ :::image type="content" source="media/api-management-howto-app-insights/apim-app-insights-logger-2.png" alt-text="Screenshot that shows where to view the newly created Application Insights logger.":::

+> [!TIP]

+> If you need to update the instrumentation key configured in the Application Insights logger, select the logger's row in the list (not the name of the logger). Enter the instrumentation key, and select **Save**.

+|resource|String. The application ID of the target web API (secured resource) in Azure Active Directory. Policy expressions are allowed. |Yes|N/A|

+|client-id|String. The client ID of the user-assigned identity in Azure Active Directory. Policy expressions are not allowed. |No|system-assigned identity|

+|output-token-variable-name|String. Name of the context variable that will receive token value as an object of type `string`. Policy expresssions are not allowed. |No|N/A|

+ Title: Migrate WordPress to App Service on Linux

+description: Migrate WordPress to App Service on Linux.

+ms.devlang: php

+# Migrate WordPress on App Service on Linux

+This article describes two ways to migrate WordPress from App Service on Windows or external hosting providers to App Service on Linux.

+> [!NOTE]

+> Migrate the content to a test instance, validate all scenarios, and if everything works as expected, swap this instance to the production slot.

+>

+ You can migrate your site to WordPress on Azure App Service in two ways:

+ 1. WordPress plugin: All-In-One WP Migration

+ 2. Manual process of migration

+## Migrate WordPress with All-In-One WP Migration plugin

+This plugin is popular for migrating sites with ease. This approach is recommended for sites less than 256MB. If it's more, you can either **purchase the premium version** of the plugin or **migrate manually** using the steps outlined in [manual migration process](#manual-migration-process).

+By default, the file upload size for WordPress on Linux App Services is limited to 50MB, and it can be increased up to 256MB (Maximum Limit). To change the file upload limit, add the following [Application Settings](configure-common.md?tabs=portal) in the App Service and save it.

+| Application Setting Name | Default Value | New Value |

+|--||-|

+| UPLOAD_MAX_FILESIZE | 50M | 256M |

+| POST_MAX_SIZE | 128M | 256M |

+> [!IMPORTANT]

+> Install All-In-One Migration plugin on both source and target sites.

+>

+### Export the data at source site

+1. Launch WordPress Admin page.

+1. Open All-In-One WP Migration plugin.

+1. Click on 'Export' option and specify the export type as file.

+1. Download the bundle.

+### Import the data at destination site

+1. Launch WordPress Admin page

+1. Open All-In-One WP Migration plugin

+1. Click on import option on the destination site, and upload the file downloaded in previous section

+1. Empty the caches in W3TC plugin (or any other caches) and validate the content of the site.

+ - Click on the **Performance** option given in the left sidebar of the admin panel to open the W3TC plugin.

+ - Then click on the **Dashboard** option shown below it.

+ - On the dashboard, you will see a button with the label **Empty All Caches**.

+## Manual migration process

+The prerequisite is that the WordPress on Linux Azure App Service must have been created with an appropriate hosting plan from here: [WordPress on Linux App Service](https://aka.ms/linux-wordpress).

+### Manually export the data at source site

+> [!NOTE]

+> Depending on the size of your content and your internet connection, this operation could take several minutes.

+>

+1. Download the **wp-content** folder from the source site. You can use popular FTP tools like [FileZilla](https://filezilla-project.org/download.php?type=client) to connect to the web server and download the content.

+1. Export the contents of the source database into an SQL file. You can perform this task either using MySQL client tools like HeidiSQL, [MySQL workbench](https://dev.mysql.com/downloads/workbench/), [PhpMyAdmin](https://docs.phpmyadmin.net/en/latest/setup.html) or through command line interface. For more information on exporting the database, refer to the following [documentation](https://dev.mysql.com/doc/workbench/en/wb-admin-export-import-management.html).

+### Manually import the data at destination site

+1. Create a new Wordpress app using our [WordPress on Linux App Service template](https://aka.ms/linux-wordpress)

+2. Open an SSH session using **WebSSH** from the Azure portal.

+

+3. Delete the existing content of **/home/site/wwwroot/wp-content** folder using the following command.

+ ```bash

+ rm -rf /home/site/wwwroot/wp-content/*

+ ```

+4. Upload the new contents of **wp-content** folder using the File Manager. Click on the label that says '**Drag a File/Folder here to upload, or click to select one**'.

+5. You can either [use an existing MySQL database](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/using_an_existing_mysql_database.md) or migrate the content to a new Azure MySQL Flexible Server created by App Service on Linux.

+> [!NOTE]

+> Azure Database for MySQL - Single Server is on the road to retirement by 16 September 2024. If your existing MySQL database is hosted on Azure Database for MySQL - Single Server, consider migrating to Azure Database for MySQL - Flexible Server using the following steps, or using [Azure Database Migration Service (DMS)](/mysql/single-server/whats-happening-to-mysql-single-server#migrate-from-single-server-to-flexible-server).

+>

+6. If you migrate the database, import the SQL file downloaded from the source database into the database of your newly created WordPress site. You can do it via the PhpMyAdmin dashboard available at **\<sitename\>.azurewebsites.net/phpmyadmin**. If you're unable to one single large SQL file, separate the files into parts and try uploading again. Steps to import the database through phpmyadmin are described [here](https://docs.phpmyadmin.net/en/latest/import_export.html#import).

+7. Launch the Azure Portal and navigate to your **App Service -> Configuration** blade. Update the database name in the **Application Settings** of App Service and save it. This will restart your App and the new changes will get reflected. [Learn more: WordPress Application Settings](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_application_settings.md)

+ | Application Setting Name | Update Required? |

+ |--||

+ | DATABASE_NAME | Yes, replace with the source (exported) database name |

+ | DATABASE_HOST | Not Required |

+ | DATABASE_USERNAME | Not Required |

+ | DATABASE_PASSWORD | Not Required |

+ 

+## Post migration actions

+### Install recommended plugins

+It's an optional step, after the site migration it is recommended to validate that you have the default recommended/equivalent plugins activated and configured accurate as before. If you're prohibited from not configuring them as per your organization governing policies, then you can uninstall the plugins.

+- The W3TC plugin should be activated and configured properly to use the local Redis cache server and Azure CDN/Blob Storage (if it was configured to use them originally). For more information on how to configure these, refer to the following documentations:

+ - [Local Redis Cache](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_local_redis_cache.md)

+ - [Azure CDN](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_azure_cdn.md)

+ - [Azure Blob Storage](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_azure_blob_storage.md)

+- WP Smush plugin is activated and configured properly for image optimization. See [Image Compression](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_image_compression.md) for more information on configuration.

+### Recommended WordPress settings

+The following WordPress settings are recommended. However, when the users migrate their custom sites, is it up to them to decide whether to use these settings or not.

+1. Open the WordPress Admin dashboard.

+2. Set the permalink structure to 'day and name', as it performs better compared to the plain permalinks that use the format **?p=123**.

+3. Under the comment settings, enable the option to break comments into pages.

+4. Show excerpts instead of the full post in the feed.

+## Search and replace (paths and domains)

+One common issue that users face during migration is that some of the contents of their old site use absolute urls/paths instead of relative ones. To resolve this issue, you can use plugins like [Search and Replace](https://wordpress.org/plugins/search-replace/) to update the database records.

+## Configuring custom domain

+To configure your site with a custom domain follow the steps described here: Tutorial: [Map existing custom DNS name](app-service-web-tutorial-custom-domain.md?tabs=a%2Cazurecli)

+## Migrating custom domain

+When you migrate a live site and its DNS domain name to App Service, that DNS name is already serving live traffic. You can avoid DNS resolution downtime by binding the active DNS name to your app as described in [Migrate an active DNS name](manage-custom-dns-migrate-domain.md).

+## Updating SSL certificates

+If your site is configured with SSL certs, then follow [Add and manage TLS/SSL certificates](configure-ssl-certificate.md?tabs=apex%2Cportal) to configure SSL.

+Next steps:

+[At-scale assessment of .NET web apps](/training/modules/migrate-app-service-migration-assistant/)

+| `MYSQLCONNSTR_` | Signifies a MySQL Database connection string in the app configuration. It's injected into a .NET app as a connection string. |

+ -->

+ kubectl apply -f https://raw.githubusercontent.com/Azure/application-gateway-kubernetes-ingress/7b55ad194e7582c47589eb9e78615042e00babf3/crds/AzureIngressProhibitedTarget-v1-CRD-v1.yaml

+## Microsoft container registry (MCR)

+Form Recognizer container images can be found within the [**Microsoft Container Registry Catalog**](https://mcr.microsoft.com/v2/_catalog) listing, the primary registry for all Microsoft Published Docker images:

+ :::image type="content" source="../media/containers/microsoft-container-registry-catalog.png" alt-text="Screenshot of the Microsoft Container Registry (MCR) catalog list.":::

+> [!IMPORTANT]

+>

+> * To use Form Recognizer containers, you must submit an online request, and have it approved. For more information, _see_ [Request approval to run container](#request-approval-to-run-container) below.

+## Request approval to run container

+Complete and submit the [**Azure Cognitive Services Application for Gated Services**](https://aka.ms/csgate) to request access to the container.

+#### Required supporting containers

+ Title: Use Form Recognizer containers in disconnected environments

+description: Learn how to run Azure Cognitive Services Docker containers disconnected from the internet.

+# Use Form Recognizer containers in disconnected environments

+<!-- markdownlint-disable MD036 -->

+<!-- markdownlint-disable MD001 -->

+Azure Cognitive Services Form Recognizer containers allow you to use Form Recognizer APIs with the benefits of containerization. Disconnected containers are offered through commitment tier pricing offered at a discounted rate compared to pay-as-you-go pricing. With commitment tier pricing, you can commit to using Form Recognizer features for a fixed fee, at a predictable total cost, based on the needs of your workload.

+## Get started

+Before attempting to run a Docker container in an offline environment, make sure you're familiar with the following requirements to successfully download and use the container:

+* Host computer requirements and recommendations.

+* The Docker `pull` command you'll use to download the container.

+* How to validate that a container is running.

+* How to send queries to the container's endpoint, once it's running.

+## Request access to use containers in disconnected environments

+Complete and submit the [request form](https://aka.ms/csdisconnectedcontainers) to request access to the containers disconnected from the Internet.

+Access is limited to customers that meet the following requirements:

+* Your organization should be identified as strategic customer or partner with Microsoft.

+* Disconnected containers are expected to run fully offline, hence your use cases must meet one of the following or similar requirements:

+ * Environment or device(s) with zero connectivity to internet.

+ * Remote location that occasionally has internet access.

+ * Organization under strict regulation of not sending any kind of data back to cloud.

+* Application completed as instructed - Pay close attention to guidance provided throughout the application to ensure you provide all the necessary information required for approval.

+## Create a new resource and purchase a commitment plan

+1. Create a new [Form Recognizer resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) in the Azure portal.

+1. Enter the applicable information to create your resource. Be sure to select **Commitment tier disconnected containers** as your pricing tier.

+ > [!NOTE]

+ >

+ > * You will only see the option to purchase a commitment tier if you have been approved by Microsoft.

+ :::image type="content" source="../media/create-resource-offline-container.png" alt-text="A screenshot showing resource creation on the Azure portal.":::

+1. Select **Review + Create** at the bottom of the page. Review the information, and select **Create**.

+## Gather required parameters

+There are three required parameters for all Cognitive Services' containers:

+* The end-user license agreement (EULA) must be present with a value of *accept*.

+* The endpoint URL for your resource from the Azure portal.

+* The API key for your resource from the Azure portal.

+Both the endpoint URL and API key are needed when you first run the container to configure it for disconnected usage. You can find the key and endpoint on the **Key and endpoint** page for your resource in the Azure portal:

+ :::image type="content" source="../media/containers/keys-and-endpoint.png" alt-text="Screenshot: Azure portal keys and endpoint page.":::

+> [!IMPORTANT]

+> You will only use your key and endpoint to configure the container to run in a disconnected environment. After you configure the container, you won't need the key and endpoint values to send API requests. Store them securely, for example, using Azure Key Vault. Only one key is necessary for this process.

+## Download a Docker container with `docker pull`

+Download the Docker container that has been approved to run in a disconnected environment. For example:

+|Docker pull command | Value |Format|

+|-|-||

+|&bullet; **`docker pull [image]`**</br>&bullet; **`docker pull [image]:latest`**|The latest container image.|&bullet; mcr.microsoft.com/azure-cognitive-services/form-recognizer/layout</br> </br>&bullet; mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice: latest |

+|||

+|&bullet; **`docker pull [image]:[version]`** | A specific container image |dockers pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/receipt:2.1-preview |

+ **Example Docker pull command**

+```docker

+docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice:latest

+```

+## Configure the container to be run in a disconnected environment

+Now that you've downloaded your container, you'll need to execute the `docker run` command with the following parameter:

+* **`DownloadLicense=True`**. This parameter will download a license file that will enable your Docker container to run when it isn't connected to the internet. It also contains an expiration date, after which the license file will be invalid to run the container. You can only use the license file in corresponding approved container.

+> [!IMPORTANT]

+>The `docker run` command will generate a template that you can use to run the container. The template contains parameters you'll need for the downloaded models and configuration file. Make sure you save this template.

+The following example shows the formatting for the `docker run` command you'll use, with placeholder values. Replace these placeholder values with your own values.

+| Placeholder | Value | Format or example |

+|-|-||

+| `{IMAGE}` | The container image you want to use. | `mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice` |

+| `{LICENSE_MOUNT}` | The path where the license will be downloaded, and mounted. | `/host/license:/path/to/license/directory` |

+| `{ENDPOINT_URI}` | The endpoint for authenticating your service request. You can find it on your resource's **Key and endpoint** page, on the Azure portal. | `https://<your-custom-subdomain>.cognitiveservices.azure.com` |

+| `{API_KEY}` | The key for your Text Analytics resource. You can find it on your resource's **Key and endpoint** page, on the Azure portal. |`{string}`|

+| `{CONTAINER_LICENSE_DIRECTORY}` | Location of the license folder on the container's local filesystem. | `/path/to/license/directory` |

+ **Example `docker run` command**

+```docker

+docker run --rm -it -p 5000:5000 \

+

+-v {LICENSE_MOUNT} \

+{IMAGE} \

+eula=accept \

+billing={ENDPOINT_URI} \

+apikey={API_KEY} \

+DownloadLicense=True \

+Mounts:License={CONTAINER_LICENSE_DIRECTORY}

+```

+After you've configured the container, use the next section to run the container in your environment with the license, and appropriate memory and CPU allocations.

+## Form Recognizer container models and configuration

+> [!IMPORTANT]

+> If you're using the Translator, Neural text-to-speech, or Speech-to-text containers, read the **Additional parameters** section for information on commands or additional parameters you will need to use.

+After you've [configured the container](#configure-the-container-to-be-run-in-a-disconnected-environment), the values for the downloaded translation models and container configuration will be generated and displayed in the container output:

+```bash

+-e MODELS= /path/to/model1/, /path/to/model2/

+-e TRANSLATORSYSTEMCONFIG=/path/to/model/config/translatorsystemconfig.json

+```

+## Run the container in a disconnected environment

+Once the license file has been downloaded, you can run the container in a disconnected environment with your license, appropriate memory, and suitable CPU allocations. The following example shows the formatting of the `docker run` command with placeholder values. Replace these placeholders values with your own values.

+Whenever the container is run, the license file must be mounted to the container and the location of the license folder on the container's local filesystem must be specified with `Mounts:License=`. In addition, an output mount must be specified so that billing usage records can be written.

+Placeholder | Value | Format or example |

+|-|-||

+| `{IMAGE}` | The container image you want to use. | `mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice` |

+ `{MEMORY_SIZE}` | The appropriate size of memory to allocate for your container. | `4g` |

+| `{NUMBER_CPUS}` | The appropriate number of CPUs to allocate for your container. | `4` |

+| `{LICENSE_MOUNT}` | The path where the license will be located and mounted. | `/host/license:/path/to/license/directory` |

+| `{OUTPUT_PATH}` | The output path for logging [usage records](#usage-records). | `/host/output:/path/to/output/directory` |

+| `{CONTAINER_LICENSE_DIRECTORY}` | Location of the license folder on the container's local filesystem. | `/path/to/license/directory` |

+| `{CONTAINER_OUTPUT_DIRECTORY}` | Location of the output folder on the container's local filesystem. | `/path/to/output/directory` |

+ **Example `docker run` command**

+```docker

+docker run --rm -it -p 5000:5000 --memory {MEMORY_SIZE} --cpus {NUMBER_CPUS} \

+-v {LICENSE_MOUNT} \

+-v {OUTPUT_PATH} \

+{IMAGE} \

+eula=accept \

+Mounts:License={CONTAINER_LICENSE_DIRECTORY}

+Mounts:Output={CONTAINER_OUTPUT_DIRECTORY}

+```

+## Other parameters and commands

+Here are a few more parameters and commands you may need to run the container.

+#### Usage records

+When operating Docker containers in a disconnected environment, the container will write usage records to a volume where they're collected over time. You can also call a REST API endpoint to generate a report about service usage.

+#### Arguments for storing logs

+When run in a disconnected environment, an output mount must be available to the container to store usage logs. For example, you would include `-v /host/output:{OUTPUT_PATH}` and `Mounts:Output={OUTPUT_PATH}` in the following example, replacing `{OUTPUT_PATH}` with the path where the logs will be stored:

+```Docker

+docker run -v /host/output:{OUTPUT_PATH} ... <image> ... Mounts:Output={OUTPUT_PATH}

+```

+#### Get records using the container endpoints

+The container provides two endpoints for returning records about its usage.

+#### Get all records

+The following endpoint will provide a report summarizing all of the usage collected in the mounted billing record directory.

+```http

+https://<service>/records/usage-logs/

+```

+ **Example HTTPS endpoint**

+ `http://localhost:5000/records/usage-logs`

+The usage-log endpoint will return a JSON response similar to the following example:

+```json

+{

+ "apiType": "string",

+ "serviceName": "string",

+ "meters": [

+ {

+ "name": "string",

+ "quantity": 256345435

+ }

+ ]

+}

+```

+#### Get records for a specific month

+The following endpoint will provide a report summarizing usage over a specific month and year.

+```HTTP

+https://<service>/records/usage-logs/{MONTH}/{YEAR}

+```

+This usage-logs endpoint will return a JSON response similar to the following example:

+```json

+{

+ "apiType": "string",

+ "serviceName": "string",

+ "meters": [

+ {

+ "name": "string",

+ "quantity": 56097

+ }

+ ]

+}

+```

+### Purchase a different commitment plan for disconnected containers

+Commitment plans for disconnected containers have a calendar year commitment period. When you purchase a plan, you'll be charged the full price immediately. During the commitment period, you can't change your commitment plan, however you can purchase more unit(s) at a pro-rated price for the remaining days in the year. You have until midnight (UTC) on the last day of your commitment, to end a commitment plan.

+You can choose a different commitment plan in the **Commitment tier pricing** settings of your resource under the **Resource Management** section.

+### End a commitment plan

+If you decide that you don't want to continue purchasing a commitment plan, you can set your resource's auto-renewal to **Do not auto-renew**. Your commitment plan will expire on the displayed commitment end date. After this date, you won't be charged for the commitment plan. You'll be able to continue using the Azure resource to make API calls, charged at pay-as-you-go pricing. You have until midnight (UTC) on the last day of the year to end a commitment plan for disconnected containers. If you cancel at or before that time, you won't be charged for the following year.

+## Troubleshooting

+Run the container with an output mount and logging enabled. These settings will enable the container generates log files that are helpful for troubleshooting issues that occur while starting or running the container.

+> [!TIP]

+> For more troubleshooting information and guidance, see [Disconnected containers Frequently asked questions (FAQ)](../../../cognitive-services/containers/disconnected-container-faq.yml).

+## Next steps

+[Deploy the Sample Labeling tool to an Azure Container Instance (ACI)](../deploy-label-tool.md#deploy-with-azure-container-instances-aci)

+Claims generated in the process of attesting enclaves using Microsoft Azure Attestation can be divided into these categories:

+## Incoming claims

+ Attestation policy must be updated using the format below.

+These claims are considered deprecated but are fully supported and will continue to be included in the future. It is recommended to use the non-deprecated claim names:

+ | |

+In addition to the TPM attestation policy claims, these claims can be used by policy authors to define authorization rules in a VBS attestation policy:

+## Outgoing claims

+Azure Attestation includes these claims in the attestation token for all attestation types:

+These claim names are used from [IETF EAT draft specification](https://tools.ietf.org/html/draft-ietf-rats-eat-03#page-9):

+These caims are generated and included in the attestation token by the service for SGX attestation:

+These claims will appear only in the attestation token generated for Intel® Xeon® Scalable processor-based server platforms. The claims will not appear if the SGX enclave is not configured with [Key Separation and Sharing Support](https://github.com/openenclave/openenclave/issues/3054). The claim definitions can be found [here](https://github.com/openenclave/openenclave/issues/3054):

+These claims are considered deprecated, but are fully supported and will continue to be included in the future. It is recommended to use the non-deprecated claim names:

+ | |

+# Microsoft Azure Attestation

+Azure Attestation supports both platform- and guest-attestation of AMD SEV-SNP based Confidential VMs (CVMs). Azure Attestation-based platform attestation happens automatically during critical boot path of CVMs, with no customer action needed. For more details on guest attestation, see [Announcing general availability of guest attestation for confidential VMs](https://techcommunity.microsoft.com/t5/azure-confidential-computing/announcing-general-availability-of-guest-attestation-for/ba-p/3648228).

+### TPM attestation

+### AMD SEV-SNP attestation

+### Trusted Launch attestation

+- Protects its data while-in use with implementation in an SGX enclave or Confidential Virtual Macine based on AMD SEV-SNP

+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin. The user creating an attestation provider should have sufficient access levels on the subscription to create a resource (e.g: owner/contributor). For more information, see [Azure built-in roles](../role-based-access-control/built-in-roles.md).

+1. Fix any validation issues and select **Create**.

+1. Fix any validation issues and select **Create**.

+1. Select **Policy signer certificates** on the resource menu on the left side of the window or on the lower pane. If you see a prompt to select certificate for authentication, select cancel to proceed.

+1. Select **Policy signer certificates** on the resource menu on the left side of the window or on the lower pane. If you see a prompt to select certificate for authentication, select cancel to proceed.

+1. Select **Policy signer certificates** on the resource menu on the left side of the window or on the lower pane. If you see a prompt to select certificate for authentication, Select **Cancel** to proceed.

+1. Select **Policy** on the resource menu on the left side of the window or on the lower pane. If you see a prompt to select certificate for authentication, select **Cancel** to proceed.

+1. Select **Policy** on the resource menu on the left side of the window or on the lower pane. If you see a prompt to select certificate for authentication, select **Cancel** proceed.

+> The Az.Attestation PowerShell module is now integrated into Az PowerShell module. Minimum version of Az module required to support attestation operations:

+ - Az PowerShell module 6.5.0

+Register the Microsoft.Attestation resource provider in subscription. For more information about Azure resource providers and how to configure and manage resources providers, see [Azure resource providers and types](../azure-resource-manager/management/resource-providers-and-types.md). Registering a resource provider is required only once for a subscription.

+Create a resource group for the attestation provider. Other Azure resources (including a virtual machine with client application instance) can be put in the same resource group.

+ > Once an attestation provider is created in this resource group, an Azure AD user must have **Attestation Contributor** role on the provider to perform operations like policy configuration/ policy signer certificates management. These permissions can also be inherited with roles such as **Owner** (wildcard permissions)/ **Contributor** (wildcard permissions) on the subscription/ resource group.

+The above command should produce output in this format:

+ To perform these actions, an Azure AD user must have **Attestation Contributor** role on the attestation provider. These permissions can also be inherited with roles such as **Owner** (wildcard permissions)/ **Contributor** (wildcard permissions) on the subscription/ resource group.

+ To perform this action, an Azure AD user must have **Attestation Reader** role on the attestation provider. The read permissions can also be inherited with roles such as **Reader** (wildcard permissions) on the subscription/ resource group.

+These PowerShell cmdlets provide policy management for an attestation provider (one TEE at a time).

+These PowerShell cmdlets provide policy signer certificates management for an attestation provider:

+Policy signer certificate is a signed JWT with claim named "maa-policyCertificate". Value of the claim is a JWK, which contains the trusted signing key to add. The JWT must be signed with private key corresponding to any of the existing policy signer certificates.

+All semantic manipulation of the policy signer certificate must be done outside of PowerShell. As far as PowerShell is concerned, it is a simple string.

+Attestation policy is used to process the attestation evidence and determine whether Azure Attestation will issue an attestation token. Attestation token generation can be controlled with custom policies.

+If your issue isn't addressed in this article, you can also submit an Azure support request on the [Azure support page](https://azure.microsoft.com/support/options/).

+## HTTPΓÇô401: Unauthorized exception

+ - Unable to manage attestation policies as the user isn't assigned with appropriate roles

+ - Unable to manage attestation policy signers as the user isn't assigned with appropriate roles

+ To perform these actions, an Azure AD user must have "Attestation Contributor" role on the attestation provider. These permissions can also be inherited with roles such as "Owner" (wildcard permissions), "Contributor" (wildcard permissions) on the subscription/ resource group.

+ To perform this action, an Azure AD user must have "Attestation Reader" role on the attestation provider. Read permissions are also part of roles such as "Reader" (wildcard permissions) on the subscription/ resource group.

+b. Refer to the guidance [here](../role-based-access-control/role-assignments-list-powershell.md) to verify your Azure role assignment on the attestation provider

+## HTTP ΓÇô 400 errors

+There are different reasons why a request may return 400. Here are some examples of errors returned by Azure Attestation APIs.

+### Attestation failure due to policy evaluation errors

+Attestation policy includes authorization rules and issuance rules. Enclave evidence is evaluated based on the authorization rules. Issuance rules define the claims to be included in attestation token. If claims in enclave evidence don't comply with authorization rules, attest calls will return policy evaluation error.

+When claims in the enclave quote don't match with the authorization rules of attestation policy

+### Attestation failure due to invalid input

+SGX attestation failure due to invalid input. Here are some examples of error messages:

+### Invalid certificate chain error while uploading policy/policy signer

+### Add/Delete policy signer failure

+### Attestation policy configuration failure

+To configure a policy in JWT format, use JWT with a claim named "AttestationPolicy". Value of the claim is Base64URL encoded version of the policy text. If the attestation provider is configured with policy signer certificates, the JWT must be signed with private key of any of the valid policy signer certificates associated with the provider.

+## Az.Attestation installation issues in PowerShell

+Unable to install the Az PowerShell module or Az.Attestation PowerShell module in PowerShell.

+PackageManagement\Install-Package: No match was found for the specified search criteria and module name

+## Policy access/configuration issues in PowerShell

+The client with object ID &lt;object Id&gt; does not have authorization to perform action Microsoft.Authorization/roleassignments/write over scope ΓÇÿsubcriptions/&lt;subscriptionId&gt;resourcegroups/secure_enclave_poc/providers/Microsoft.Authorization/roleassignments/&lt;role assignmentId&gt;ΓÇÖ or the scope is invalid. If access was recently granted, refresh your credentials

+The minimum version of the Az PowerShell modules required to support attestation operations are:

+- **Az 4.5.0**

+- **Az.Accounts 1.9.2**

+- **Az.Attestation 0.1.8**

+```azurepowershell-interactive

+If the versions do not meet the minimum requirement, run the Update-Module PowerShell cmdlet.

+```azurepowershell-interactive

+Update-Module -Name Az.Attestation

+```

+If you create one or more Azure Attestation resources, youΓÇÖll want to monitor how and when your attestation instance is accessed, and by whom. You can do so by enabling logging for Microsoft Azure Attestation, which saves information in an Azure storage account you provide.

+Logging information will be available up to 10 minutes after the operation occurred (in most cases, it will be quicker). Since you provide the storage account, you can secure your logs via standard Azure access controls and delete logs you no longer want to keep in your storage account.

+**Insights-logs-notprocessed** contains requests that the service was unable to process, typically due to malformed HTTP headers, incomplete message bodies, or similar issues.

+The properties contain additional Azure attestation specific context:

+| failureResourceId | Resource ID of component that resulted in request failure |

+# Trusted Platform Module (TPM) and Virtualization based Security(VBS) enclave attestation protocol

+Microsoft Azure Attestation guarantees strong security by verifying a chain of trust, maintained from a root of trust (TPM) to the launch of the hypervisor and secure kernel. To do so, Azure Attestation must attest to the boot state of the machine before we can establish trust in the secure enclave. The operating system, hypervisor, and secure kernel binaries must be signed by the correct official Microsoft authorities and configured in a secure way. Once we have bound trust between the Trusted Platform Module (TPM) and the health of the hypervisor, we can trust the Virtualization Based Security(VBS) enclave IDKs provided in the Measured Boot Log, with this we can validate that a key pair was generated by the enclave and mint an attestation report that binds trust in that key and contains other claims such as the security level and boot attestation properties.

+The protocol has two messages exchanges:

+TPM-only sample:

+- ***boot_attestation*** (Object): This is optional and contains logs and the TPM quote saved before the system hibernated and resumed. boot_attestation info must be associated with the same cold boot cycle (that is, the system was only hibernated and resumed between them).

+**other_keys** (Array(Key object)): Array of keys to be sent to the service. Maximum of two keys.

+**service_context** (BASE64URL(OCTETS)): Opaque, encrypted context created by the service that includes, among others, the challenge and an expiration time for that challenge.

+- **Relying party**: The component that relies on Azure Attestation to verify enclave validity.

+- **Client**: The component that collects information from an enclave and sends requests to Azure Attestation.

+- **Azure Attestation**: The component that accepts enclave evidence from client, validates it and returns attestation token to the client

+1. The client has an URI that refers to an instance of Azure Attestation. The client sends evidence to Azure Attestation. Exact information submitted to the provider depends on the enclave type

+1. On device/platform boot, various boot loaders and boot services measure events backed by TPM and securely store them as TCG logs. Client collects the TCG logs from the device and TPM quote, which acts evidence for attestation.

+2. The client authenticates to Azure AD and obtains an access token.

+3. The client has an URI, which refers to an instance of Azure Attestation. The client sends the evidence and the Azure Active Directory (Azure AD) access token to Azure Attestation. Exact information submitted to the provider depends on the platform.

+4. Azure Attestation validates the submitted information and evaluates it against a configured policy. If the verification succeeds, Azure Attestation issues an attestation token and returns it to the client. If this step fails, Azure Attestation reports an error to the client. The communication between the client and attestation service is dictated by the Azure attestation TPM protocol.

+5. The client then sends the attestation token to relying party. The relying party calls public key metadata endpoint of Azure Attestation to retrieve signing certificates. The relying party then verifies the signature of the attestation token and ensures the platform's trustworthiness.

+## Retry logic in runbook to avoid transient failures

+Runbooks often make calls to remote systems such as Azure via ARM, Azure Resource Graph, SQL services and other web services.

+When the system that the runbooks are calling is busy, temporary unavailable or implementing throttling under load, the calls are vulnerable to have runtime errors. To build resiliency in the runbooks, you must implement retry logic when making the calls so that the runbooks can handle a transient problem without failing.

+For more information, refer [Retry pattern](https://learn.microsoft.com/azure/architecture/patterns/retry) and [General REST and retry guidelines](https://learn.microsoft.com/azure/architecture/best-practices/retry-service-specific#general-rest-and-retry-guidelines).

+### Example 1: If your runbook makes only one or two calls

+```powershell

+$searchServiceURL = "https://$searchServiceName.search.windows.net"

+$resource = Get-AzureRmResource -ResourceType "Microsoft.Search/searchServices" -ResourceGroupName $searchResourceGroupName -ResourceName $searchServiceName -ApiVersion 2015-08-19

+$searchAPIKey = (Invoke-AzureRmResourceAction -Action listAdminKeys -ResourceId $resource.ResourceId -ApiVersion 2015-08-19 -Force).PrimaryKey

+```

+When you call `Invoke-AzureRmResourceAction`, you may observe transient failures. In such scenario, we recommend that you implement the following basic pattern around the call to the cmdlet.

+```powershell

+$searchServiceURL = "https://$searchServiceName.search.windows.net"

+$resource = Get-AzureRmResource -ResourceType "Microsoft.Search/searchServices" -ResourceGroupName $searchResourceGroupName -ResourceName $searchServiceName -ApiVersion 2015-08-19

+ # Adding in a retry

+ $Stoploop = $false

+ $Retrycount = 0

+

+ do {

+ try {

+ $searchAPIKey = (Invoke-AzureRmResourceAction -Action listAdminKeys -ResourceId $resource.ResourceId -ApiVersion 2015-08-19 -Force).PrimaryKey

+ write-verbose "Invoke-AzureRmResourceAction on $resource.ResourceId completed"

+ $Stoploop = $true

+ }

+ catch {

+ if ($Retrycount -gt 3)

+ {

+ Write-verbose "Could not Invoke-AzureRmResourceAction on $resource.ResourceId after 3 retrys."

+ $Stoploop = $true

+ }

+ else

+ {

+ Write-verbose "Could not Invoke-AzureRmResourceAction on $resource.ResourceId retrying in 30 seconds..."

+ Start-Sleep -Seconds 30

+ $Retrycount = $Retrycount + 1

+ }

+ }

+ }

+ While ($Stoploop -eq $false)

+```

+>[!NOTE]

+>The attempt to retry the call is up to three times, sleeping for 30 seconds each time.

+### Example 2 : If the runbook is making frequent remote calls

+If the runbook is making frequent remote calls then it could experience transient runtime issues. Create a function that implements the retry logic for each call that is made and pass the call to be made in as a script block to execute.

+```powershell

+Function ResilientRemoteCall {

+ param(

+ $scriptblock

+ )

+

+ $Stoploop = $false

+ $Retrycount = 0

+

+ do {

+ try {

+ Invoke-Command -scriptblock $scriptblock

+ write-verbose "Invoked $scriptblock completed"

+ $Stoploop = $true

+ }

+ catch {

+ if ($Retrycount -gt 3)

+ {

+ Write-verbose "Invoked $scriptblock failed 3 times and we will not try again."

+ $Stoploop = $true

+ }

+ else

+ {

+ Write-verbose "Invoked $scriptblock failed retrying in 30 seconds..."

+ Start-Sleep -Seconds 30

+ $Retrycount = $Retrycount + 1

+ }

+ }

+ }

+ While ($Stoploop -eq $false)

+}

+```

+You can then pass each remote call into the function as </br>

+`ResilientRemoteCall { Get-AzVm }` </br> or </br>

+`ResilientRemoteCall { $searchAPIKey = (Invoke-AzureRmResourceAction -Action listAdminKeys -ResourceId $resource.ResourceId -ApiVersion 2015-08-19 -Force).PrimaryKey}`

+|DataON AZS-6224|1.23.8|1.12.0_2022-10-11|16.0.537.5223| postgres 12.3 (Ubuntu 12.3-1) |

+| Dell EMC PowerFlex |1.21.5|1.4.1_2022-03-08|15.0.2255.119 | postgres 12.3 (Ubuntu 12.3-1) |

+| PowerFlex version 3.6 |1.21.5|1.4.1_2022-03-08|15.0.2255.119 | postgres 12.3 (Ubuntu 12.3-1) |

+| PowerFlex CSI version 1.4 |1.21.5|1.4.1_2022-03-08 | 15.0.2255.119 | postgres 12.3 (Ubuntu 12.3-1) |

+|HPE Apollo 4200 Gen10 Plus | 1.22.6 | 1.11.0_2022-09-13 |16.0.312.4243|12.3 (Ubuntu 12.3-1)|

+|Kublr 1.21.2 | 1.22.10 | 1.9.0_2022-07-12 | 16.0.312.4243 |PostgreSQL 12.3 (Ubuntu 12.3-1) |

+|Lenovo ThinkAgile MX3520 |AKS on Azure Stack HCI 21H2| 1.10.0_2022-08-09 |16.0.312.4243|postgres 12.3 (Ubuntu 12.3-1)|

+| Portworx Enterprise 2.9 | 1.22.5 | 1.1.0_2021-11-02 | 15.0.2195.191 | postgres 12.3 (Ubuntu 12.3-1) |

+| OpenShift 4.10.16 | 1.23.5 | 1.11.0_2022-09-13 | 16.0.312.4243 | postgres 12.3 (Ubuntu 12.3-1)|

+| TKGm v1.5.3 | 1.22.8 | 1.9.0_2022-07-12 | 16.0.312.4243 | postgres 12.3 (Ubuntu 12.3-1)|

+| TKG-1.6.0 | 1.23.8 | 1.11.0_2022-09-13 | 16.0.312.4243 | postgres 12.3 (Ubuntu 12.3-1)

+ https://us.atlas.microsoft.com/routesets/operations/{operationId}?api-version=2022-09-01-preview&subscription-key={Your-Azure-Maps-Subscription-key}

+1. Copy the value of the **Resource-Location** key from the responses header. This is the resource location URL and contains the `routesetId`, as shown below:

+ https://us.atlas.microsoft.com/routesets/{routesetId}?api-version=2022-09-01-preview&subscription-key={Your-Azure-Maps-Subscription-key}

+| Red Hat Enterprise Linux Server 8+ | X | X | |

+| Red Hat Enterprise Linux Server 6 | | X | |

+ Title: Transform text logs during ingestion in Azure Monitor Logs

+description: Write a KQL query that transforms text log data and add the transformation to a data collection rule in Azure Monitor Logs.

+# Tutorial: Transform text logs during ingestion in Azure Monitor Logs

+Ingestion-time transformations let you filter or modify incoming data before it's stored in a Log Analytics workspace. This article explains how to write a KQL query that transforms text log data and add the transformation to a data collection rule.

+The procedure described here assumes you've already ingested some data from a text file, as described in [Collect text logs with Azure Monitor Agent](../agents/data-collection-text-log.md). In this tutorial, you'll:

+1. Write a KQL query to transform ingested data.

+1. Modify the target table schema.

+1. Add the transformation to your data collection rule.

+1. Verify that the transformation works correctly.

+## Prerequisites

+To complete this procedure, you need:

+- Log Analytics workspace where you have at least [contributor rights](../logs/manage-access.md#azure-rbac).

+- [Data collection rule](../essentials/data-collection-rule-overview.md), [data collection endpoint](../essentials/data-collection-endpoint-overview.md#create-a-data-collection-endpoint), and [custom table](../logs/create-custom-table.md#create-a-custom-table), as described in [Collect text logs with Azure Monitor Agent](../agents/data-collection-text-log.md).

+- A VM, Virtual Machine Scale Set, or Arc-enabled on-premises server that writes logs to a text file.

+ Text file requirements:

+ - Store on the local drive of the machine on which Azure Monitor Agent is running.

+ - Delineate with an end of line.

+ - Use ASCII or UTF-8 encoding. Other formats such as UTF-16 aren't supported.

+ - Don't allow circular logging, log rotation where the file is overwritten with new entries, or renaming where a file is moved and a new file with the same name is opened.

+## Write a KQL query to transform ingested data

+1. View the data in the target custom table in Log Analytics:

+ 1. In the Azure portal, select **Log Analytics workspaces** > your Log Analytics workspace > **Logs**.

+ 1. Run a basic query the custom logs table to view table data.

+1. Use the query window to write and test a query that transforms the raw data in your table.

+ For information about the KQL operators that transformations support, see [Structure of transformation in Azure Monitor](../essentials/data-collection-transformations-structure.md#kql-limitations).

+ **Example**

+

+ The sample uses [basic KQL operators](/azure/data-explorer/kql-quick-reference) to parse the data in the `RawData` column into three new columns, called `Time Ingested`, `RecordNumber`, and `RandomContent`:

+

+ - The `extend` operator adds new columns.

+ - The `project` operator formats the output to match the columns of the target table schema:

+ ```kusto

+ MyTable_CL

+ | extend d=todynamic(RawData)

+ | project TimeGenerated,TimeIngested=tostring(d.Time),

+ RecordNumber=tostring(d.RecordNumber),

+ RandomContent=tostring(d.RandomContent),

+ RawData

+ ```

+ > [!NOTE]

+ > Information the user should notice even if skimmingQuerying table data in this way doesn't actually modify the data in the table. Azure Monitor applies the transformation in the [data ingestion pipeline](../essentials/data-collection-transformations.md#how-transformations-work) after you [add your transformation query to the data collection rule](#apply-the-transformation-to-your-data-collection-rule).

+1. Format the query into a single line and replace the table name in the first line of the query with the word `source`.

+

+ For example:

+ ```kusto

+ source | extend d=todynamic(RawData) | project TimeGenerated,TimeIngested=tostring(d.Time),RecordNumber=tostring(d.RecordNumber), RandomContent=tostring(d.RandomContent), RawData

+ ```

+1. Copy the formatted query so you can paste it into the data collection rule configuration.

+## Modify the custom table to include the new columns

+[Add or delete columns in your custom table](../logs/create-custom-table.md#add-or-delete-a-custom-column), based on your transformation query.

+The example transformation query above adds three new columns of type `string`:

+- `TimeIngested`

+- `RecordNumber`

+- `RandomContent`

+To support this transformation, add these three new columns to your custom table.

+## Apply the transformation to your data collection rule

+1. On the **Monitor** menu, select **Data Collection Rules** > your data collection rule.

+1. Select **Data sources** > your data source.

+1. Paste the formatted transformation query in the **Transform** field on the **Data source** tab of the **Add data source** screen.

+1. Select **Save**.

+ :::image type="content" source="media/azure-monitor-agent-transformation/add-transformation-to-data-collection-rule.png" alt-text="Screenshot of the Add data sources pane with the Transform field highlighted." lightbox="media/azure-monitor-agent-transformation/add-transformation-to-data-collection-rule.png":::

+## Check that the transformation works

+View the data in the target custom table and check that data is being ingested correctly into the modified table:

+1. In the Azure portal, select **Log Analytics workspaces** > your Log Analytics workspace > **Logs**.

+1. Run a basic query the custom logs table to view table data.

+## Next steps

+Learn more about:

+- [Data collection transformations](../essentials/data-collection-rule-structure.md).

+- [Data collection rules](../essentials/data-collection-rule-overview.md).

+- [Data collection endpoints](../essentials/data-collection-endpoint-overview.md).

+

+* [Windows desktop applications, services, and worker roles](https://github.com/Microsoft/appcenter)

+* [Universal Windows app](https://github.com/Microsoft/appcenter) (App Center)

+* [Android](https://github.com/Microsoft/appcenter) (App Center)

+* [iOS](https://github.com/Microsoft/appcenter) (App Center)

+> If you are upgrading from an earlier 3.x version, you may be impacted by changing defaults or slight differences in the data we collect. See the migration notes at the top of the release notes for

+> [3.4.0](https://github.com/microsoft/ApplicationInsights-Java/releases/tag/3.4.0),

+> [3.3.0](https://github.com/microsoft/ApplicationInsights-Java/releases/tag/3.3.0),

+> [3.2.0](https://github.com/microsoft/ApplicationInsights-Java/releases/tag/3.2.0), and

+> [3.1.0](https://github.com/microsoft/ApplicationInsights-Java/releases/tag/3.1.0)

+> for more details.

+1. **Mobile app code:** Use the App Center SDK to collect events from your app. Then send copies of these events to Application Insights for analysis by [following this guide](https://github.com/Microsoft/appcenter).

+You can scale your resources differently on different days of the week.

+For example, you have a Virtual Machine Scale Set and want to:

+- Set a minimum of 3 instances on weekdays, scaling based on inbound flows.

+- Scale-in to a fixed 1 instance on weekends when there's less traffic.

+In this example:

+Learn more about autoscale by referring to the following articles:

+ | Grafana workspace | To use the collected Prometheus metrics with dashboards in [Azure-managed Grafana](../../managed-grafan#enable-prometheus-metric-collection) to the Azure Monitor workspace if it isn't already. |

+ Title: Manage an Azure Monitor workspace (preview)

+description: How to create and delete Azure Monitor workspaces.

+# Manage an Azure Monitor workspace

+This article shows you how to create and delete an Azure Monitor workspace. When you configure Azure Monitor managed service for Prometheus, you can select an existing Azure Monitor workspace or create a new one.

+## Create an Azure Monitor workspace

+### [Azure portal](#tab/azure-portal)

+1. Open the **Azure Monitor workspaces** menu in the Azure portal.

+2. Select **Create**.

+ :::image type="content" source="media/azure-monitor-workspace-overview/view-azure-monitor-workspaces.png" lightbox="media/azure-monitor-workspace-overview/view-azure-monitor-workspaces.png" alt-text="Screenshot of Azure Monitor workspaces menu and page.":::

+3. On the **Create an Azure Monitor Workspace** page, select a **Subscription** and **Resource group** where the workspace should be created.

+4. Provide a **Name** and a **Region** for the workspace.

+5. Select **Review + create** to create the workspace.

+### [CLI](#tab/cli)

+Use the following command to create an Azure Monitor workspace using Azure CLI.

+```azurecli

+az resource create --resource-group <resource-group-name> --namespace microsoft.monitor --resource-type accounts --name <azure-monitor-workspace-name> --location <location> --properties {}

+```

+### [Resource Manager](#tab/resource-manager)

+Use one of the following Resource Manager templates with any of the [standard deployment options](../resource-manager-samples.md#deploy-the-sample-templates) to create an Azure Monitor workspace.

+```json

+{

+ "$schema": "http://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",

+ "contentVersion": "1.0.0.0",

+ "parameters": {

+ "name": {

+ "type": "string"

+ },

+ "location": {

+ "type": "string",

+ "defaultValue": ""

+ }

+ },

+ "resources": [

+ {

+ "type": "microsoft.monitor/accounts",

+ "apiVersion": "2021-06-03-preview",

+ "name": "[parameters('name')]",

+ "location": "[if(empty(parameters('location')), resourceGroup().location, parameters('location'))]"

+ }

+ ]

+}

+```

+```bicep

+@description('Specify the name of the workspace.')

+param workspaceName string

+@description('Specify the location for the workspace.')

+param location string = resourceGroup().location

+resource workspace 'microsoft.monitor/accounts@2021-06-03-preview' = {

+ name: workspaceName

+ location: location

+}

+```

+To connect your Azure Monitor managed service for Prometheus to your Azure Monitor workspace, see [Collect Prometheus metrics from AKS cluster](./prometheus-metrics-enable.md)

+## Delete an Azure Monitor workspace

+When you delete an Azure Monitor workspace, no soft-delete operation is performed like with a [Log Analytics workspace](../logs/delete-workspace.md). The data in the workspace is immediately deleted, and there's no recovery option.

+### [Azure portal](#tab/azure-portal)

+1. Open the **Azure Monitor workspaces** menu in the Azure portal.

+2. Select your workspace.

+4. Select **Delete**.

+ :::image type="content" source="media/azure-monitor-workspace-overview/delete-azure-monitor-workspace.png" lightbox="media/azure-monitor-workspace-overview/delete-azure-monitor-workspace.png" alt-text="Screenshot of Azure Monitor workspaces delete button.":::

+### [CLI](#tab/cli)

+To delete an AzureMonitor workspace use [az resource delete](https://learn.microsoft.com/cli/azure/resource#az-resource-delete)

+For example:

+```azurecli

+ az resource delete --ids /subscriptions/abcdef01-2345-6789-0abc-def012345678/resourcegroups/rg-azmon/providers/microsoft.monitor/accounts/prometheus-metrics-workspace

+```

+or

+```azurecli

+ az resource delete -g rg-azmon -n prometheus-metrics-workspace --resource-type Microsoft.Monitor/accounts

+```

+### [Resource Manager](#tab/resource-manager)

+For information on deleting resources and Azure Resource Manager, see [Azure Resource Manager resource group and resource deletion](../../azure-resource-manager/management/delete-resource-group.md)

+## Link a Grafana workspace

+Connect an Azure Monitor workspace to an [Azure Managed Grafana](../../managed-grafan) workspace to allow Grafana to use the Azure Monitor workspace data in a Grafana dashboard. An Azure Monitor workspace can be connected to multiple Grafana workspaces, and a Grafana workspace can be connected to multiple Azure Monitor workspaces.

+> [!NOTE]

+> When you add the Azure Monitor workspace as a data source to Grafana, it will be listed in form `Managed_Prometheus_<azure-workspace-name>`.

+### [Azure portal](#tab/azure-portal)

+1. Open the **Azure Monitor workspace** menu in the Azure portal.

+2. Select your workspace.

+3. Select **Linked Grafana workspaces**.

+4. Select a Grafana workspace.

+### [CLI](#tab/cli)

+Create a link between the Azure Monitor workspace and the Grafana workspace by updating the Azure Kubernetes Service cluster that you're monitoring.

+```azurecli

+az aks update --enable-azuremonitormetrics -n <cluster-name> -g <cluster-resource-group> --azure-monitor-workspace-resource-id

+<azure-monitor-workspace-name-resource-id> --grafana-resource-id <grafana-workspace-name-resource-id>

+```

+If your cluster is already configured to send data to an Azure Monitor managed service for Prometheus, disable it first using the following command:

+```azurecli

+az aks update --disable-azuremonitormetrics -g <cluster-resource-group> -n <cluster-name>

+```

+Output

+```JSON

+"azureMonitorProfile": {

+ "metrics": {

+ "enabled": true,

+ "kubeStateMetrics": {

+ "metricAnnotationsAllowList": "",

+ "metricLabelsAllowlist": ""

+ }

+ }

+}

+```

+### [Resource Manager](#tab/resource-manager)

+

+To set up an Azure monitor workspace as a data source for Grafana using a Resource Manager template, see [Collect Prometheus metrics from AKS cluster (preview)](prometheus-metrics-enable.md?tabs=resource-manager#enable-prometheus-metric-collection)

+If your Grafana Instance is self managed see [Use Azure Monitor managed service for Prometheus (preview) as data source for self-managed Grafana using managed system identity](./prometheus-self-managed-grafana-azure-active-directory.md)

+## Next steps

+- [Links a Grafana instance to your Azure monitor Workspace](./prometheus-metrics-enable.md#enable-prometheus-metric-collection)

+- Learn more about the [Azure Monitor data platform](../data-platform.md).

+- [Azure Monitor Workspace Overview](./azure-monitor-workspace-overview.md)

+Azure Monitor workspaces will eventually contain all metric data collected by Azure Monitor. Currently, only Prometheus metrics are data hosted in an Azure Monitor workspace.

+## Azure Monitor workspace architecture

+While a single Azure Monitor workspace may be sufficient for many use cases using Azure Monitor, many organizations create multiple workspaces to better meet their needs. This article presents a set of criteria for deciding whether to use a single Azure Monitor workspace, multiple Azure Monitor workspaces, and the configuration and placement of those workspaces.

+### Design criteria

+As you identify the right criteria to create additional Azure Monitor workspaces, your design should use the lowest number of workspaces that will match your requirements, while optimizing for minimal administrative management overhead.

+The following table presents criteria to consider when designing an Azure Monitor workspace architecture.

+|Criteria|Description|

+|||

+|Segregate by logical boundaries |Create separate Azure Monitor workspaces for operational data based on logical boundaries, for example, a role, application type, type of metric etc.|

+|Azure tenants | For multiple Azure tenants, create an Azure Monitor workspace in each tenant. Data sources can only send monitoring data to an Azure Monitor workspace in the same Azure tenant. |

+|Azure regions |Each Azure Monitor workspace resides in a particular Azure region. Regulatory or compliance requirements may dictate the storage of data in particular locations. |

+|Data ownership |Create separate Azure Monitor workspaces to define data ownership, for example by subsidiaries or affiliated companies.|

+### Considerations when creating an Azure Monitor workspace

+* Azure Monitor workspaces are regional. When you create a new Azure Monitor workspace, you provide a region, setting the location in which the data is stored.

+* Start with a single workspace to reduce the complexity of managing and querying data from multiple Azure resources.

+* The default Azure Monitor workspace limit is 1 million active times series and 1 million events per minute ingested.

+* There's no reduction in performance due to the amount of data in your Azure Monitor workspace. Multiple services can send data to the same account simultaneously. There is, however, a limit on how large an Azure Monitor workspace can scale as explained below.

+### Growing account capacity

+Azure Monitor workspaces have default quotas and limitations for metrics. As your product grows and you need more metrics, you can request an increase to 50 million events or active time series. If your capacity needs grow exceptionally large, and your data ingestion needs can no longer be met by a single Azure Monitor workspace, consider creating multiple Azure Monitor workspaces.

+### Multiple Azure Monitor workspaces

+When an Azure Monitor workspace reaches 80% of its maximum capacity, or depending on your current and forecasted metrics volume, it's recommended to split the Azure Monitor workspace into multiple workspaces. Split the workspace based on how the data in the workspace is used by your applications and business processes, and how you want to access that data in the future.

+

+In certain circumstances, splitting Azure Monitor workspace into multiple workspaces can be necessary. For example:

+* Monitoring data in sovereign clouds ΓÇô Create Azure Monitor workspace(s) in each sovereign cloud.

+* Compliance or regulatory requirements that mandate storage of data in specific regions ΓÇô Create an Azure Monitor workspace per region as per requirements. There may be a need to manage the scale of metrics for large services or financial institutions with regional accounts.

+* Separating metric data in test, pre-production, and production environments

+>[!Note]

+> A single query cannot access multiple Azure Monitor workspaces. Keep data that you want to retrieve in a single query in same workspace. For presentation purposes, setting up Grafana with each workspace as a dedicated data source will allow for querying multiple workspaces in a single Grafana panel.

+## Limitations

+See [Azure Monitor service limits](../service-limits.md#prometheus-metrics) for performance related service limits for Azure Monitor managed service for Prometheus.

+- Private Links aren't supported for Prometheus metrics collection into Azure monitor workspace.

+- Azure monitor workspaces are currently only supported in public clouds.

+- Azure monitor workspaces don't currently support being moved into a different subscription or resource group once created.

+- [Manage an Azure Monitor workspace (preview)](./azure-monitor-workspace-manage.md)

+Date list was last updated: 01/24/2023.

+## Microsoft.AAD/DomainServices

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|\DirectoryServices(NTDS)\LDAP Searches/sec |Yes |NTDS - LDAP Searches/sec |CountPerSecond |Average |This metric indicates the average number of searches per second for the NTDS object. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\DirectoryServices(NTDS)\LDAP Successful Binds/sec |Yes |NTDS - LDAP Successful Binds/sec |CountPerSecond |Average |This metric indicates the number of LDAP successful binds per second for the NTDS object. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\DNS\Total Query Received/sec |Yes |DNS - Total Query Received/sec |CountPerSecond |Average |This metric indicates the average number of queries received by DNS server in each second. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\DNS\Total Response Sent/sec |Yes |Total Response Sent/sec |CountPerSecond |Average |This metric indicates the average number of responses sent by DNS server in each second. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\Memory\% Committed Bytes In Use |Yes |% Committed Bytes In Use |Percent |Average |This metric indicates the ratio of Memory\Committed Bytes to the Memory\Commit Limit. Committed memory is the physical memory in use for which space has been reserved in the paging file should it need to be written to disk. The commit limit is determined by the size of the paging file. If the paging file is enlarged, the commit limit increases, and the ratio is reduced. This counter displays the current percentage value only; it is not an average. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\Process(dns)\% Processor Time |Yes |% Processor Time (dns) |Percent |Average |This metric indicates the percentage of elapsed time that all of dns process threads used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\Process(lsass)\% Processor Time |Yes |% Processor Time (lsass) |Percent |Average |This metric indicates the percentage of elapsed time that all of lsass process threads used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\Processor(_Total)\% Processor Time |Yes |Total Processor Time |Percent |Average |This metric indicates the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the percentage of time that the processor spends executing the idle thread and then subtracting that value from 100%. (Each processor has an idle thread that consumes cycles when no other threads are ready to run). This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. It should be noted that the accounting calculation of whether the processor is idle is performed at an internal sampling interval of the system clock (10ms). On todays fast processors, % Processor Time can therefore underestimate the processor utilization as the processor may be spending a lot of time servicing threads between the system clock sampling interval. Workload based timer applications are one example of applications which are more likely to be measured inaccurately as timers are signaled just after the sample is taken. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\Security System-Wide Statistics\Kerberos Authentications |Yes |Kerberos Authentications |CountPerSecond |Average |This metric indicates the number of times that clients use a ticket to authenticate to this computer per second. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+|\Security System-Wide Statistics\NTLM Authentications |Yes |NTLM Authentications |CountPerSecond |Average |This metric indicates the number of NTLM authentications processed per second for the Active Directory on this domain controller or for local accounts on this member server. It is backed by performance counter data from the domain controller, and can be filtered or splitted by role instance. |DataCenter, Tenant, Role, RoleInstance, ScaleUnit |

+## microsoft.aadiam/azureADMetrics

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|CACompliantDeviceSuccessCount |Yes |CACompliantDeviceSuccessCount |Count |Count |CA compliant device scuccess count for Azure AD |No Dimensions |

+|CAManagedDeviceSuccessCount |No |CAManagedDeviceSuccessCount |Count |Count |CA domain join device success count for Azure AD |No Dimensions |

+|MFAAttemptCount |No |MFAAttemptCount |Count |Count |MFA attempt count for Azure AD |No Dimensions |

+|MFAFailureCount |No |MFAFailureCount |Count |Count |MFA failure count for Azure AD |No Dimensions |

+|MFASuccessCount |No |MFASuccessCount |Count |Count |MFA success count for Azure AD |No Dimensions |

+|SamlFailureCount |Yes |SamlFailureCount |Count |Count |Saml token failure count for relying party scenario |No Dimensions |

+|SamlSuccessCount |Yes |SamlSuccessCount |Count |Count |Saml token success count for relying party scenario |No Dimensions |

+## Microsoft.AnalysisServices/servers

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|CleanerCurrentPrice |Yes |Memory: Cleaner Current Price |Count |Average |Current price of memory, $/byte/time, normalized to 1000. |ServerResourceType |

+|CleanerMemoryNonshrinkable |Yes |Memory: Cleaner Memory nonshrinkable |Bytes |Average |Amount of memory, in bytes, not subject to purging by the background cleaner. |ServerResourceType |

+|CleanerMemoryShrinkable |Yes |Memory: Cleaner Memory shrinkable |Bytes |Average |Amount of memory, in bytes, subject to purging by the background cleaner. |ServerResourceType |

+|CommandPoolBusyThreads |Yes |Threads: Command pool busy threads |Count |Average |Number of busy threads in the command thread pool. |ServerResourceType |

+|CommandPoolIdleThreads |Yes |Threads: Command pool idle threads |Count |Average |Number of idle threads in the command thread pool. |ServerResourceType |

+|CommandPoolJobQueueLength |Yes |Command Pool Job Queue Length |Count |Average |Number of jobs in the queue of the command thread pool. |ServerResourceType |

+|CurrentConnections |Yes |Connection: Current connections |Count |Average |Current number of client connections established. |ServerResourceType |

+|CurrentUserSessions |Yes |Current User Sessions |Count |Average |Current number of user sessions established. |ServerResourceType |

+|LongParsingBusyThreads |Yes |Threads: Long parsing busy threads |Count |Average |Number of busy threads in the long parsing thread pool. |ServerResourceType |

+|LongParsingIdleThreads |Yes |Threads: Long parsing idle threads |Count |Average |Number of idle threads in the long parsing thread pool. |ServerResourceType |

+|LongParsingJobQueueLength |Yes |Threads: Long parsing job queue length |Count |Average |Number of jobs in the queue of the long parsing thread pool. |ServerResourceType |

+|mashup_engine_memory_metric |Yes |M Engine Memory |Bytes |Average |Memory usage by mashup engine processes |ServerResourceType |

+|mashup_engine_private_bytes_metric |Yes |M Engine Private Bytes |Bytes |Average |Private bytes usage by mashup engine processes. |ServerResourceType |

+|mashup_engine_qpu_metric |Yes |M Engine QPU |Count |Average |QPU usage by mashup engine processes |ServerResourceType |

+|mashup_engine_virtual_bytes_metric |Yes |M Engine Virtual Bytes |Bytes |Average |Virtual bytes usage by mashup engine processes. |ServerResourceType |

+|memory_metric |Yes |Memory |Bytes |Average |Memory. Range 0-25 GB for S1, 0-50 GB for S2 and 0-100 GB for S4 |ServerResourceType |

+|memory_thrashing_metric |Yes |Memory Thrashing |Percent |Average |Average memory thrashing. |ServerResourceType |

+|MemoryLimitHard |Yes |Memory: Memory Limit Hard |Bytes |Average |Hard memory limit, from configuration file. |ServerResourceType |

+|MemoryLimitHigh |Yes |Memory: Memory Limit High |Bytes |Average |High memory limit, from configuration file. |ServerResourceType |

+|MemoryLimitLow |Yes |Memory: Memory Limit Low |Bytes |Average |Low memory limit, from configuration file. |ServerResourceType |

+|MemoryLimitVertiPaq |Yes |Memory: Memory Limit VertiPaq |Bytes |Average |In-memory limit, from configuration file. |ServerResourceType |

+|MemoryUsage |Yes |Memory: Memory Usage |Bytes |Average |Memory usage of the server process as used in calculating cleaner memory price. Equal to counter Process\PrivateBytes plus the size of memory-mapped data, ignoring any memory which was mapped or allocated by the xVelocity in-memory analytics engine (VertiPaq) in excess of the xVelocity engine Memory Limit. |ServerResourceType |

+|private_bytes_metric |Yes |Private Bytes |Bytes |Average |Private bytes. |ServerResourceType |

+|ProcessingPoolBusyIOJobThreads |Yes |Threads: Processing pool busy I/O job threads |Count |Average |Number of threads running I/O jobs in the processing thread pool. |ServerResourceType |

+|ProcessingPoolBusyNonIOThreads |Yes |Threads: Processing pool busy non-I/O threads |Count |Average |Number of threads running non-I/O jobs in the processing thread pool. |ServerResourceType |

+|ProcessingPoolIdleIOJobThreads |Yes |Threads: Processing pool idle I/O job threads |Count |Average |Number of idle threads for I/O jobs in the processing thread pool. |ServerResourceType |

+|ProcessingPoolIdleNonIOThreads |Yes |Threads: Processing pool idle non-I/O threads |Count |Average |Number of idle threads in the processing thread pool dedicated to non-I/O jobs. |ServerResourceType |

+|ProcessingPoolIOJobQueueLength |Yes |Threads: Processing pool I/O job queue length |Count |Average |Number of I/O jobs in the queue of the processing thread pool. |ServerResourceType |

+|ProcessingPoolJobQueueLength |Yes |Processing Pool Job Queue Length |Count |Average |Number of non-I/O jobs in the queue of the processing thread pool. |ServerResourceType |

+|qpu_metric |Yes |QPU |Count |Average |QPU. Range 0-100 for S1, 0-200 for S2 and 0-400 for S4 |ServerResourceType |

+|QueryPoolBusyThreads |Yes |Query Pool Busy Threads |Count |Average |Number of busy threads in the query thread pool. |ServerResourceType |

+|QueryPoolIdleThreads |Yes |Threads: Query pool idle threads |Count |Average |Number of idle threads for I/O jobs in the processing thread pool. |ServerResourceType |

+|QueryPoolJobQueueLength |Yes |Threads: Query pool job queue length |Count |Average |Number of jobs in the queue of the query thread pool. |ServerResourceType |

+|Quota |Yes |Memory: Quota |Bytes |Average |Current memory quota, in bytes. Memory quota is also known as a memory grant or memory reservation. |ServerResourceType |

+|QuotaBlocked |Yes |Memory: Quota Blocked |Count |Average |Current number of quota requests that are blocked until other memory quotas are freed. |ServerResourceType |

+|RowsConvertedPerSec |Yes |Processing: Rows converted per sec |CountPerSecond |Average |Rate of rows converted during processing. |ServerResourceType |

+|RowsReadPerSec |Yes |Processing: Rows read per sec |CountPerSecond |Average |Rate of rows read from all relational databases. |ServerResourceType |

+|RowsWrittenPerSec |Yes |Processing: Rows written per sec |CountPerSecond |Average |Rate of rows written during processing. |ServerResourceType |

+|ShortParsingBusyThreads |Yes |Threads: Short parsing busy threads |Count |Average |Number of busy threads in the short parsing thread pool. |ServerResourceType |

+|ShortParsingIdleThreads |Yes |Threads: Short parsing idle threads |Count |Average |Number of idle threads in the short parsing thread pool. |ServerResourceType |

+|ShortParsingJobQueueLength |Yes |Threads: Short parsing job queue length |Count |Average |Number of jobs in the queue of the short parsing thread pool. |ServerResourceType |

+|SuccessfullConnectionsPerSec |Yes |Successful Connections Per Sec |CountPerSecond |Average |Rate of successful connection completions. |ServerResourceType |

+|TotalConnectionFailures |Yes |Total Connection Failures |Count |Average |Total failed connection attempts. |ServerResourceType |

+|TotalConnectionRequests |Yes |Total Connection Requests |Count |Average |Total connection requests. These are arrivals. |ServerResourceType |

+|VertiPaqNonpaged |Yes |Memory: VertiPaq Nonpaged |Bytes |Average |Bytes of memory locked in the working set for use by the in-memory engine. |ServerResourceType |

+|VertiPaqPaged |Yes |Memory: VertiPaq Paged |Bytes |Average |Bytes of paged memory in use for in-memory data. |ServerResourceType |

+|virtual_bytes_metric |Yes |Virtual Bytes |Bytes |Average |Virtual bytes. |ServerResourceType |

+## Microsoft.ApiManagement/service

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|BackendDuration |Yes |Duration of Backend Requests |MilliSeconds |Average |Duration of Backend Requests in milliseconds |Location, Hostname |

+|Capacity |Yes |Capacity |Percent |Average |Utilization metric for ApiManagement service. Note: For skus other than Premium, 'Max' aggregation will show the value as 0. |Location |

+|ConnectionAttempts |Yes |WebSocket Connection Attempts (Preview) |Count |Total |Count of WebSocket connection attempts based on selected source and destination |Location, Source, Destination, State |

+|Duration |Yes |Overall Duration of Gateway Requests |MilliSeconds |Average |Overall Duration of Gateway Requests in milliseconds |Location, Hostname |

+|EventHubDroppedEvents |Yes |Dropped EventHub Events |Count |Total |Number of events skipped because of queue size limit reached |Location |

+|EventHubRejectedEvents |Yes |Rejected EventHub Events |Count |Total |Number of rejected EventHub events (wrong configuration or unauthorized) |Location |

+|EventHubSuccessfulEvents |Yes |Successful EventHub Events |Count |Total |Number of successful EventHub events |Location |

+|EventHubThrottledEvents |Yes |Throttled EventHub Events |Count |Total |Number of throttled EventHub events |Location |

+|EventHubTimedoutEvents |Yes |Timed Out EventHub Events |Count |Total |Number of timed out EventHub events |Location |

+|EventHubTotalBytesSent |Yes |Size of EventHub Events |Bytes |Total |Total size of EventHub events in bytes |Location |

+|EventHubTotalEvents |Yes |Total EventHub Events |Count |Total |Number of events sent to EventHub |Location |

+|EventHubTotalFailedEvents |Yes |Failed EventHub Events |Count |Total |Number of failed EventHub events |Location |

+|FailedRequests |Yes |Failed Gateway Requests (Deprecated) |Count |Total |Number of failures in gateway requests - Use multi-dimension request metric with GatewayResponseCodeCategory dimension instead |Location, Hostname |

+|NetworkConnectivity |Yes |Network Connectivity Status of Resources (Preview) |Count |Average |Network Connectivity status of dependent resource types from API Management service |Location, ResourceType |

+|OtherRequests |Yes |Other Gateway Requests (Deprecated) |Count |Total |Number of other gateway requests - Use multi-dimension request metric with GatewayResponseCodeCategory dimension instead |Location, Hostname |

+|Requests |Yes |Requests |Count |Total |Gateway request metrics with multiple dimensions |Location, Hostname, LastErrorReason, BackendResponseCode, GatewayResponseCode, BackendResponseCodeCategory, GatewayResponseCodeCategory |

+|SuccessfulRequests |Yes |Successful Gateway Requests (Deprecated) |Count |Total |Number of successful gateway requests - Use multi-dimension request metric with GatewayResponseCodeCategory dimension instead |Location, Hostname |

+|TotalRequests |Yes |Total Gateway Requests (Deprecated) |Count |Total |Number of gateway requests - Use multi-dimension request metric with GatewayResponseCodeCategory dimension instead |Location, Hostname |

+|UnauthorizedRequests |Yes |Unauthorized Gateway Requests (Deprecated) |Count |Total |Number of unauthorized gateway requests - Use multi-dimension request metric with GatewayResponseCodeCategory dimension instead |Location, Hostname |

+|WebSocketMessages |Yes |WebSocket Messages (Preview) |Count |Total |Count of WebSocket messages based on selected source and destination |Location, Source, Destination |

+## Microsoft.App/containerapps

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|CoresQuotaUsed |Yes |Reserved Cores |Count |Maximum |Number of reserved cores for container app revisions |revisionName |

+|Replicas |Yes |Replica Count |Count |Maximum |Number of replicas count of container app |revisionName |

+|Requests |Yes |Requests |Count |Total |Requests processed |revisionName, podName, statusCodeCategory, statusCode |

+|RestartCount |Yes |Replica Restart Count |Count |Maximum |Restart count of container app replicas |revisionName, podName |

+|RxBytes |Yes |Network In Bytes |Bytes |Total |Network received bytes |revisionName, podName |

+|TotalCoresQuotaUsed |Yes |Total Reserved Cores |Count |Average |Number of total reserved cores for the container app |No Dimensions |

+|TxBytes |Yes |Network Out Bytes |Bytes |Total |Network transmitted bytes |revisionName, podName |

+|UsageNanoCores |Yes |CPU Usage |NanoCores |Average |CPU consumed by the container app, in nano cores. 1,000,000,000 nano cores = 1 core |revisionName, podName |

+|WorkingSetBytes |Yes |Memory Working Set Bytes |Bytes |Average |Container App working set memory used in bytes. |revisionName, podName |

+## Microsoft.App/managedEnvironments

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|EnvCoresQuotaLimit |Yes |Cores Quota Limit |Count |Average |The cores quota limit of managed environment |No Dimensions |

+|EnvCoresQuotaUtilization |Yes |Percentage Cores Used Out Of Limit |Percent |Average |The cores quota utilization of managed environment |No Dimensions |

+## Microsoft.AppConfiguration/configurationStores

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|DailyStorageUsage |Yes |DailyStorageUsage |Percent |Maximum |Total storage usage of the store in percentage. Updated at minimum every 24 hours. |No Dimensions |

+|HttpIncomingRequestCount |Yes |HttpIncomingRequestCount |Count |Total |Total number of incoming http requests. |StatusCode, Authentication, Endpoint |

+|HttpIncomingRequestDuration |Yes |HttpIncomingRequestDuration |Count |Average |Latency on an http request. |StatusCode, Authentication, Endpoint |

+|ThrottledHttpRequestCount |Yes |ThrottledHttpRequestCount |Count |Total |Throttled http requests. |Endpoint |

+## Microsoft.AppPlatform/Spring

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|active-timer-count |Yes |active-timer-count |Count |Average |Number of timers that are currently active |Deployment, AppName, Pod |

+|alloc-rate |Yes |alloc-rate |Bytes |Average |Number of bytes allocated in the managed heap |Deployment, AppName, Pod |

+|AppCpuUsage |Yes |App CPU Usage (Deprecated) |Percent |Average |The recent CPU usage for the app. This metric is being deprecated. Please use "App CPU Usage" with metric id "PodCpuUsage". |Deployment, AppName, Pod |

+|assembly-count |Yes |assembly-count |Count |Average |Number of Assemblies Loaded |Deployment, AppName, Pod |

+|cpu-usage |Yes |cpu-usage |Percent |Average |% time the process has utilized the CPU |Deployment, AppName, Pod |

+|current-requests |Yes |current-requests |Count |Average |Total number of requests in processing in the lifetime of the process |Deployment, AppName, Pod |

+|exception-count |Yes |exception-count |Count |Total |Number of Exceptions |Deployment, AppName, Pod |

+|failed-requests |Yes |failed-requests |Count |Average |Total number of failed requests in the lifetime of the process |Deployment, AppName, Pod |

+|GatewayHttpServerRequestsMilliSecondsMax |Yes |Max time of requests |Milliseconds |Maximum |The max time of requests |Pod, httpStatusCode, outcome, httpMethod |

+|GatewayHttpServerRequestsMilliSecondsSum |Yes |Total time of requests |Milliseconds |Total |The total time of requests |Pod, httpStatusCode, outcome, httpMethod |

+|GatewayHttpServerRequestsSecondsCount |Yes |Request count |Count |Total |The number of requests |Pod, httpStatusCode, outcome, httpMethod |

+|GatewayJvmGcLiveDataSizeBytes |Yes |jvm.gc.live.data.size |Bytes |Average |Size of old generation memory pool after a full GC |Pod |

+|GatewayJvmGcMaxDataSizeBytes |Yes |jvm.gc.max.data.size |Bytes |Maximum |Max size of old generation memory pool |Pod |

+|GatewayJvmGcMemoryAllocatedBytesTotal |Yes |jvm.gc.memory.allocated |Bytes |Maximum |Incremented for an increase in the size of the young generation memory pool after one GC to before the next |Pod |

+|GatewayJvmGcMemoryPromotedBytesTotal |Yes |jvm.gc.memory.promoted |Bytes |Maximum |Count of positive increases in the size of the old generation memory pool before GC to after GC |Pod |

+|GatewayJvmGcPauseSecondsCount |Yes |jvm.gc.pause.total.count |Count |Total |GC Pause Count |Pod |

+|GatewayJvmGcPauseSecondsMax |Yes |jvm.gc.pause.max.time |Seconds |Maximum |GC Pause Max Time |Pod |

+|GatewayJvmGcPauseSecondsSum |Yes |jvm.gc.pause.total.time |Seconds |Total |GC Pause Total Time |Pod |

+|GatewayJvmMemoryCommittedBytes |Yes |jvm.memory.committed |Bytes |Average |Memory assigned to JVM in bytes |Pod |

+|GatewayJvmMemoryUsedBytes |Yes |jvm.memory.used |Bytes |Average |Memory Used in bytes |Pod |

+|GatewayProcessCpuUsage |Yes |process.cpu.usage |Percent |Average |The recent CPU usage for the JVM process |Pod |

+|GatewayRatelimitThrottledCount |Yes |Throttled requests count |Count |Total |The count of the throttled requests |Pod |

+|GatewaySystemCpuUsage |Yes |system.cpu.usage |Percent |Average |The recent CPU usage for the whole system |Pod |

+|gc-heap-size |Yes |gc-heap-size |Count |Average |Total heap size reported by the GC (MB) |Deployment, AppName, Pod |

+|gen-0-gc-count |Yes |gen-0-gc-count |Count |Average |Number of Gen 0 GCs |Deployment, AppName, Pod |

+|gen-0-size |Yes |gen-0-size |Bytes |Average |Gen 0 Heap Size |Deployment, AppName, Pod |

+|gen-1-gc-count |Yes |gen-1-gc-count |Count |Average |Number of Gen 1 GCs |Deployment, AppName, Pod |

+|gen-1-size |Yes |gen-1-size |Bytes |Average |Gen 1 Heap Size |Deployment, AppName, Pod |

+|gen-2-gc-count |Yes |gen-2-gc-count |Count |Average |Number of Gen 2 GCs |Deployment, AppName, Pod |

+|gen-2-size |Yes |gen-2-size |Bytes |Average |Gen 2 Heap Size |Deployment, AppName, Pod |

+|IngressBytesReceived |Yes |Bytes Received |Bytes |Average |Count of bytes received by Azure Spring Apps from the clients |Hostname, HttpStatus |

+|IngressBytesReceivedRate |Yes |Throughput In (bytes/s) |BytesPerSecond |Average |Bytes received per second by Azure Spring Apps from the clients |Hostname, HttpStatus |

+|IngressBytesSent |Yes |Bytes Sent |Bytes |Average |Count of bytes sent by Azure Spring Apps to the clients |Hostname, HttpStatus |

+|IngressBytesSentRate |Yes |Throughput Out (bytes/s) |BytesPerSecond |Average |Bytes sent per second by Azure Spring Apps to the clients |Hostname, HttpStatus |

+|IngressFailedRequests |Yes |Failed Requests |Count |Average |Count of failed requests by Azure Spring Apps from the clients |Hostname, HttpStatus |

+|IngressRequests |Yes |Requests |Count |Average |Count of requests by Azure Spring Apps from the clients |Hostname, HttpStatus |

+|IngressResponseStatus |Yes |Response Status |Count |Average |HTTP response status returned by Azure Spring Apps. The response status code distribution can be further categorized to show responses in 2xx, 3xx, 4xx, and 5xx categories |Hostname, HttpStatus |

+|IngressResponseTime |Yes |Response Time |Seconds |Average |Http response time return by Azure Spring Apps |Hostname, HttpStatus |

+|jvm.gc.live.data.size |Yes |jvm.gc.live.data.size |Bytes |Average |Size of old generation memory pool after a full GC |Deployment, AppName, Pod |

+|jvm.gc.max.data.size |Yes |jvm.gc.max.data.size |Bytes |Average |Max size of old generation memory pool |Deployment, AppName, Pod |

+|jvm.gc.memory.allocated |Yes |jvm.gc.memory.allocated |Bytes |Maximum |Incremented for an increase in the size of the young generation memory pool after one GC to before the next |Deployment, AppName, Pod |

+|jvm.gc.memory.promoted |Yes |jvm.gc.memory.promoted |Bytes |Maximum |Count of positive increases in the size of the old generation memory pool before GC to after GC |Deployment, AppName, Pod |

+|jvm.gc.pause.total.count |Yes |jvm.gc.pause.total.count |Count |Total |GC Pause Count |Deployment, AppName, Pod |

+|jvm.gc.pause.total.time |Yes |jvm.gc.pause.total.time |Milliseconds |Total |GC Pause Total Time |Deployment, AppName, Pod |

+|jvm.memory.committed |Yes |jvm.memory.committed |Bytes |Average |Memory assigned to JVM in bytes |Deployment, AppName, Pod |

+|jvm.memory.max |Yes |jvm.memory.max |Bytes |Maximum |The maximum amount of memory in bytes that can be used for memory management |Deployment, AppName, Pod |

+|jvm.memory.used |Yes |jvm.memory.used |Bytes |Average |App Memory Used in bytes |Deployment, AppName, Pod |

+|loh-size |Yes |loh-size |Bytes |Average |LOH Heap Size |Deployment, AppName, Pod |

+|monitor-lock-contention-count |Yes |monitor-lock-contention-count |Count |Average |Number of times there were contention when trying to take the monitor lock |Deployment, AppName, Pod |

+|PodCpuUsage |Yes |App CPU Usage |Percent |Average |The recent CPU usage for the app |Deployment, AppName, Pod |

+|PodMemoryUsage |Yes |App Memory Usage |Percent |Average |The recent Memory usage for the app |Deployment, AppName, Pod |

+|PodNetworkIn |Yes |App Network In |Bytes |Average |Cumulative count of bytes received in the app |Deployment, AppName, Pod |

+|PodNetworkOut |Yes |App Network Out |Bytes |Average |Cumulative count of bytes sent from the app |Deployment, AppName, Pod |

+|process.cpu.usage |Yes |process.cpu.usage |Percent |Average |The recent CPU usage for the JVM process |Deployment, AppName, Pod |

+|requests-per-second |Yes |requests-rate |Count |Average |Request rate |Deployment, AppName, Pod |

+|system.cpu.usage |Yes |system.cpu.usage |Percent |Average |The recent CPU usage for the whole system |Deployment, AppName, Pod |

+|threadpool-completed-items-count |Yes |threadpool-completed-items-count |Count |Average |ThreadPool Completed Work Items Count |Deployment, AppName, Pod |

+|threadpool-queue-length |Yes |threadpool-queue-length |Count |Average |ThreadPool Work Items Queue Length |Deployment, AppName, Pod |

+|threadpool-thread-count |Yes |threadpool-thread-count |Count |Average |Number of ThreadPool Threads |Deployment, AppName, Pod |

+|time-in-gc |Yes |time-in-gc |Percent |Average |% time in GC since the last GC |Deployment, AppName, Pod |

+|tomcat.global.error |Yes |tomcat.global.error |Count |Total |Tomcat Global Error |Deployment, AppName, Pod |

+|tomcat.global.received |Yes |tomcat.global.received |Bytes |Total |Tomcat Total Received Bytes |Deployment, AppName, Pod |

+|tomcat.global.request.avg.time |Yes |tomcat.global.request.avg.time |Milliseconds |Average |Tomcat Request Average Time |Deployment, AppName, Pod |

+|tomcat.global.request.max |Yes |tomcat.global.request.max |Milliseconds |Maximum |Tomcat Request Max Time |Deployment, AppName, Pod |

+|tomcat.global.request.total.count |Yes |tomcat.global.request.total.count |Count |Total |Tomcat Request Total Count |Deployment, AppName, Pod |

+|tomcat.global.request.total.time |Yes |tomcat.global.request.total.time |Milliseconds |Total |Tomcat Request Total Time |Deployment, AppName, Pod |

+|tomcat.global.sent |Yes |tomcat.global.sent |Bytes |Total |Tomcat Total Sent Bytes |Deployment, AppName, Pod |

+|tomcat.sessions.active.current |Yes |tomcat.sessions.active.current |Count |Total |Tomcat Session Active Count |Deployment, AppName, Pod |

+|tomcat.sessions.active.max |Yes |tomcat.sessions.active.max |Count |Total |Tomcat Session Max Active Count |Deployment, AppName, Pod |

+|tomcat.sessions.alive.max |Yes |tomcat.sessions.alive.max |Milliseconds |Maximum |Tomcat Session Max Alive Time |Deployment, AppName, Pod |

+|tomcat.sessions.created |Yes |tomcat.sessions.created |Count |Total |Tomcat Session Created Count |Deployment, AppName, Pod |

+|tomcat.sessions.expired |Yes |tomcat.sessions.expired |Count |Total |Tomcat Session Expired Count |Deployment, AppName, Pod |

+|tomcat.sessions.rejected |Yes |tomcat.sessions.rejected |Count |Total |Tomcat Session Rejected Count |Deployment, AppName, Pod |

+|tomcat.threads.config.max |Yes |tomcat.threads.config.max |Count |Total |Tomcat Config Max Thread Count |Deployment, AppName, Pod |

+|tomcat.threads.current |Yes |tomcat.threads.current |Count |Total |Tomcat Current Thread Count |Deployment, AppName, Pod |

+|total-requests |Yes |total-requests |Count |Average |Total number of requests in the lifetime of the process |Deployment, AppName, Pod |

+|working-set |Yes |working-set |Count |Average |Amount of working set used by the process (MB) |Deployment, AppName, Pod |

+## Microsoft.Automation/automationAccounts

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|HybridWorkerPing |Yes |Hybrid Worker Ping |Count |Count |The number of pings from the hybrid worker |HybridWorkerGroup, HybridWorker, HybridWorkerVersion |

+|TotalJob |Yes |Total Jobs |Count |Total |The total number of jobs |Runbook, Status |

+|TotalUpdateDeploymentMachineRuns |Yes |Total Update Deployment Machine Runs |Count |Total |Total software update deployment machine runs in a software update deployment run |Status, TargetComputer, SoftwareUpdateConfigurationName, SoftwareUpdateConfigurationRunId |

+|TotalUpdateDeploymentRuns |Yes |Total Update Deployment Runs |Count |Total |Total software update deployment runs |Status, SoftwareUpdateConfigurationName |

+## microsoft.avs/privateClouds

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|CapacityLatest |Yes |Datastore Disk Total Capacity |Bytes |Average |The total capacity of disk in the datastore |dsname |

+|DiskUsedPercentage |Yes | Percentage Datastore Disk Used |Percent |Average |Percent of available disk used in Datastore |dsname |

+|EffectiveCpuAverage |Yes |Percentage CPU |Percent |Average |Percentage of Used CPU resources in Cluster |clustername |

+|EffectiveMemAverage |Yes |Average Effective Memory |Bytes |Average |Total available amount of machine memory in cluster |clustername |

+|OverheadAverage |Yes |Average Memory Overhead |Bytes |Average |Host physical memory consumed by the virtualization infrastructure |clustername |

+|TotalMbAverage |Yes |Average Total Memory |Bytes |Average |Total memory in cluster |clustername |

+|UsageAverage |Yes |Average Memory Usage |Percent |Average |Memory usage as percentage of total configured or available memory |clustername |

+|UsedLatest |Yes |Datastore Disk Used |Bytes |Average |The total amount of disk used in the datastore |dsname |

+## Microsoft.Batch/batchaccounts

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|CoreCount |No |Dedicated Core Count |Count |Total |Total number of dedicated cores in the batch account |No Dimensions |

+|CreatingNodeCount |No |Creating Node Count |Count |Total |Number of nodes being created |No Dimensions |

+|IdleNodeCount |No |Idle Node Count |Count |Total |Number of idle nodes |No Dimensions |

+|JobDeleteCompleteEvent |Yes |Job Delete Complete Events |Count |Total |Total number of jobs that have been successfully deleted. |jobId |

+|JobDeleteStartEvent |Yes |Job Delete Start Events |Count |Total |Total number of jobs that have been requested to be deleted. |jobId |

+|JobDisableCompleteEvent |Yes |Job Disable Complete Events |Count |Total |Total number of jobs that have been successfully disabled. |jobId |

+|JobDisableStartEvent |Yes |Job Disable Start Events |Count |Total |Total number of jobs that have been requested to be disabled. |jobId |

+|JobStartEvent |Yes |Job Start Events |Count |Total |Total number of jobs that have been successfully started. |jobId |

+|JobTerminateCompleteEvent |Yes |Job Terminate Complete Events |Count |Total |Total number of jobs that have been successfully terminated. |jobId |

+|JobTerminateStartEvent |Yes |Job Terminate Start Events |Count |Total |Total number of jobs that have been requested to be terminated. |jobId |

+|LeavingPoolNodeCount |No |Leaving Pool Node Count |Count |Total |Number of nodes leaving the Pool |No Dimensions |

+|LowPriorityCoreCount |No |LowPriority Core Count |Count |Total |Total number of low-priority cores in the batch account |No Dimensions |

+|OfflineNodeCount |No |Offline Node Count |Count |Total |Number of offline nodes |No Dimensions |

+|PoolCreateEvent |Yes |Pool Create Events |Count |Total |Total number of pools that have been created |poolId |

+|PoolDeleteCompleteEvent |Yes |Pool Delete Complete Events |Count |Total |Total number of pool deletes that have completed |poolId |

+|PoolDeleteStartEvent |Yes |Pool Delete Start Events |Count |Total |Total number of pool deletes that have started |poolId |

+|PoolResizeCompleteEvent |Yes |Pool Resize Complete Events |Count |Total |Total number of pool resizes that have completed |poolId |

+|PoolResizeStartEvent |Yes |Pool Resize Start Events |Count |Total |Total number of pool resizes that have started |poolId |

+|PreemptedNodeCount |No |Preempted Node Count |Count |Total |Number of preempted nodes |No Dimensions |

+|RebootingNodeCount |No |Rebooting Node Count |Count |Total |Number of rebooting nodes |No Dimensions |

+|ReimagingNodeCount |No |Reimaging Node Count |Count |Total |Number of reimaging nodes |No Dimensions |

+|RunningNodeCount |No |Running Node Count |Count |Total |Number of running nodes |No Dimensions |

+|StartingNodeCount |No |Starting Node Count |Count |Total |Number of nodes starting |No Dimensions |

+|StartTaskFailedNodeCount |No |Start Task Failed Node Count |Count |Total |Number of nodes where the Start Task has failed |No Dimensions |

+|TaskCompleteEvent |Yes |Task Complete Events |Count |Total |Total number of tasks that have completed |poolId, jobId |

+|TaskFailEvent |Yes |Task Fail Events |Count |Total |Total number of tasks that have completed in a failed state |poolId, jobId |

+|TaskStartEvent |Yes |Task Start Events |Count |Total |Total number of tasks that have started |poolId, jobId |

+|TotalLowPriorityNodeCount |No |Low-Priority Node Count |Count |Total |Total number of low-priority nodes in the batch account |No Dimensions |

+|TotalNodeCount |No |Dedicated Node Count |Count |Total |Total number of dedicated nodes in the batch account |No Dimensions |

+|UnusableNodeCount |No |Unusable Node Count |Count |Total |Number of unusable nodes |No Dimensions |

+|WaitingForStartTaskNodeCount |No |Waiting For Start Task Node Count |Count |Total |Number of nodes waiting for the Start Task to complete |No Dimensions |

+## microsoft.bing/accounts

+<!-- Data source : naam-->

+|BlockedCalls |Yes |Blocked Calls |Count |Total |Number of calls that exceeded the rate or quota limit |ApiName, ServingRegion, StatusCode |

+|ClientErrors |Yes |Client Errors |Count |Total |Number of calls with any client error (HTTP status code 4xx) |ApiName, ServingRegion, StatusCode |

+|DataIn |Yes |Data In |Bytes |Total |Incoming request Content-Length in bytes |ApiName, ServingRegion, StatusCode |

+|DataOut |Yes |Data Out |Bytes |Total |Outgoing response Content-Length in bytes |ApiName, ServingRegion, StatusCode |

+|Latency |Yes |Latency |Milliseconds |Average |Latency in milliseconds |ApiName, ServingRegion, StatusCode |

+|ServerErrors |Yes |Server Errors |Count |Total |Number of calls with any server error (HTTP status code 5xx) |ApiName, ServingRegion, StatusCode |

+|SuccessfulCalls |Yes |Successful Calls |Count |Total |Number of successful calls (HTTP status code 2xx) |ApiName, ServingRegion, StatusCode |

+|TotalCalls |Yes |Total Calls |Count |Total |Total number of calls |ApiName, ServingRegion, StatusCode |

+|TotalErrors |Yes |Total Errors |Count |Total |Number of calls with any error (HTTP status code 4xx or 5xx) |ApiName, ServingRegion, StatusCode |

+## microsoft.botservice/botservices

+<!-- Data source : naam-->

+|RequestLatency |Yes |Request Latency |Milliseconds |Total |Time taken by the server to process the request |Operation, Authentication, Protocol, DataCenter |

+|RequestsTraffic |Yes |Requests Traffic |Percent |Count |Number of Requests Made |Operation, Authentication, Protocol, StatusCode, StatusCodeClass, DataCenter |

+## Microsoft.BotService/botServices/channels

+<!-- Data source : arm-->

+|RequestLatency |Yes |Requests Latencies |Milliseconds |Average |How long it takes to get request response |Operation, Authentication, Protocol, ResourceId, Region |

+|RequestsTraffic |Yes |Requests Traffic |Count |Average |Number of requests within a given period of time |Operation, Authentication, Protocol, ResourceId, Region, StatusCode, StatusCodeClass, StatusText |

+## Microsoft.BotService/botServices/connections

+<!-- Data source : arm-->

+|RequestLatency |Yes |Requests Latencies |Milliseconds |Average |How long it takes to get request response |Operation, Authentication, Protocol, ResourceId, Region |

+|RequestsTraffic |Yes |Requests Traffic |Count |Average |Number of requests within a given period of time |Operation, Authentication, Protocol, ResourceId, Region, StatusCode, StatusCodeClass, StatusText |

+## Microsoft.BotService/checknameavailability

+<!-- Data source : arm-->

+|RequestLatency |Yes |Requests Latencies |Milliseconds |Average |How long it takes to get request response |Operation, Authentication, Protocol, ResourceId, Region |

+|RequestsTraffic |Yes |Requests Traffic |Count |Average |Number of requests within a given period of time |Operation, Authentication, Protocol, ResourceId, Region, StatusCode, StatusCodeClass, StatusText |

+## Microsoft.BotService/hostsettings

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|RequestLatency |Yes |Requests Latencies |Milliseconds |Average |How long it takes to get request response |Operation, Authentication, Protocol, ResourceId, Region |

+|RequestsTraffic |Yes |Requests Traffic |Count |Average |Number of requests within a given period of time |Operation, Authentication, Protocol, ResourceId, Region, StatusCode, StatusCodeClass, StatusText |

+## Microsoft.BotService/listauthserviceproviders

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|RequestLatency |Yes |Requests Latencies |Milliseconds |Average |How long it takes to get request response |Operation, Authentication, Protocol, ResourceId, Region |

+|RequestsTraffic |Yes |Requests Traffic |Count |Average |Number of requests within a given period of time |Operation, Authentication, Protocol, ResourceId, Region, StatusCode, StatusCodeClass, StatusText |

+## Microsoft.BotService/listqnamakerendpointkeys

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|RequestLatency |Yes |Requests Latencies |Milliseconds |Average |How long it takes to get request response |Operation, Authentication, Protocol, ResourceId, Region |

+|RequestsTraffic |Yes |Requests Traffic |Count |Average |Number of requests within a given period of time |Operation, Authentication, Protocol, ResourceId, Region, StatusCode, StatusCodeClass, StatusText |

+## Microsoft.Cache/redis

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|allcachehits |Yes |Cache Hits (Instance Based) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allcachemisses |Yes |Cache Misses (Instance Based) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allcacheRead |Yes |Cache Read (Instance Based) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allcacheWrite |Yes |Cache Write (Instance Based) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allconnectedclients |Yes |Connected Clients (Instance Based) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allConnectionsClosedPerSecond |Yes |Connections Closed Per Second (Instance Based) |CountPerSecond |Maximum |The number of instantaneous connections closed per second on the cache via port 6379 or 6380 (SSL). For more details, see https://aka.ms/redis/metrics. |ShardId, Primary, Ssl |

+|allConnectionsCreatedPerSecond |Yes |Connections Created Per Second (Instance Based) |CountPerSecond |Maximum |The number of instantaneous connections created per second on the cache via port 6379 or 6380 (SSL). For more details, see https://aka.ms/redis/metrics. |ShardId, Primary, Ssl |

+|allevictedkeys |Yes |Evicted Keys (Instance Based) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allexpiredkeys |Yes |Expired Keys (Instance Based) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allgetcommands |Yes |Gets (Instance Based) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|alloperationsPerSecond |Yes |Operations Per Second (Instance Based) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allpercentprocessortime |Yes |CPU (Instance Based) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allserverLoad |Yes |Server Load (Instance Based) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allsetcommands |Yes |Sets (Instance Based) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|alltotalcommandsprocessed |Yes |Total Operations (Instance Based) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|alltotalkeys |Yes |Total Keys (Instance Based) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allusedmemory |Yes |Used Memory (Instance Based) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allusedmemorypercentage |Yes |Used Memory Percentage (Instance Based) |Percent |Maximum |The percentage of cache memory used for key/value pairs. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|allusedmemoryRss |Yes |Used Memory RSS (Instance Based) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |ShardId, Port, Primary |

+|cachehits |Yes |Cache Hits |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|cachehits0 |Yes |Cache Hits (Shard 0) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits1 |Yes |Cache Hits (Shard 1) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits2 |Yes |Cache Hits (Shard 2) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits3 |Yes |Cache Hits (Shard 3) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits4 |Yes |Cache Hits (Shard 4) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits5 |Yes |Cache Hits (Shard 5) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits6 |Yes |Cache Hits (Shard 6) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits7 |Yes |Cache Hits (Shard 7) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits8 |Yes |Cache Hits (Shard 8) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachehits9 |Yes |Cache Hits (Shard 9) |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheLatency |Yes |Cache Latency Microseconds (Preview) |Count |Average |The latency to the cache in microseconds. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|cachemisses |Yes |Cache Misses |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|cachemisses0 |Yes |Cache Misses (Shard 0) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses1 |Yes |Cache Misses (Shard 1) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses2 |Yes |Cache Misses (Shard 2) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses3 |Yes |Cache Misses (Shard 3) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses4 |Yes |Cache Misses (Shard 4) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses5 |Yes |Cache Misses (Shard 5) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses6 |Yes |Cache Misses (Shard 6) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses7 |Yes |Cache Misses (Shard 7) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses8 |Yes |Cache Misses (Shard 8) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemisses9 |Yes |Cache Misses (Shard 9) |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cachemissrate |Yes |Cache Miss Rate |Percent |Total |The % of get requests that miss. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|cacheRead |Yes |Cache Read |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |ShardId |

+|cacheRead0 |Yes |Cache Read (Shard 0) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead1 |Yes |Cache Read (Shard 1) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead2 |Yes |Cache Read (Shard 2) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead3 |Yes |Cache Read (Shard 3) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead4 |Yes |Cache Read (Shard 4) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead5 |Yes |Cache Read (Shard 5) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead6 |Yes |Cache Read (Shard 6) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead7 |Yes |Cache Read (Shard 7) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead8 |Yes |Cache Read (Shard 8) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheRead9 |Yes |Cache Read (Shard 9) |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite |Yes |Cache Write |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |ShardId |

+|cacheWrite0 |Yes |Cache Write (Shard 0) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite1 |Yes |Cache Write (Shard 1) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite2 |Yes |Cache Write (Shard 2) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite3 |Yes |Cache Write (Shard 3) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite4 |Yes |Cache Write (Shard 4) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite5 |Yes |Cache Write (Shard 5) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite6 |Yes |Cache Write (Shard 6) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite7 |Yes |Cache Write (Shard 7) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite8 |Yes |Cache Write (Shard 8) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|cacheWrite9 |Yes |Cache Write (Shard 9) |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients |Yes |Connected Clients |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|connectedclients0 |Yes |Connected Clients (Shard 0) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients1 |Yes |Connected Clients (Shard 1) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients2 |Yes |Connected Clients (Shard 2) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients3 |Yes |Connected Clients (Shard 3) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients4 |Yes |Connected Clients (Shard 4) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients5 |Yes |Connected Clients (Shard 5) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients6 |Yes |Connected Clients (Shard 6) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients7 |Yes |Connected Clients (Shard 7) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients8 |Yes |Connected Clients (Shard 8) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|connectedclients9 |Yes |Connected Clients (Shard 9) |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|errors |Yes |Errors |Count |Maximum |The number errors that occurred on the cache. For more details, see https://aka.ms/redis/metrics. |ShardId, ErrorType |

+|evictedkeys |Yes |Evicted Keys |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|evictedkeys0 |Yes |Evicted Keys (Shard 0) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys1 |Yes |Evicted Keys (Shard 1) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys2 |Yes |Evicted Keys (Shard 2) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys3 |Yes |Evicted Keys (Shard 3) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys4 |Yes |Evicted Keys (Shard 4) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys5 |Yes |Evicted Keys (Shard 5) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys6 |Yes |Evicted Keys (Shard 6) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys7 |Yes |Evicted Keys (Shard 7) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys8 |Yes |Evicted Keys (Shard 8) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|evictedkeys9 |Yes |Evicted Keys (Shard 9) |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys |Yes |Expired Keys |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|expiredkeys0 |Yes |Expired Keys (Shard 0) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys1 |Yes |Expired Keys (Shard 1) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys2 |Yes |Expired Keys (Shard 2) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys3 |Yes |Expired Keys (Shard 3) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys4 |Yes |Expired Keys (Shard 4) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys5 |Yes |Expired Keys (Shard 5) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys6 |Yes |Expired Keys (Shard 6) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys7 |Yes |Expired Keys (Shard 7) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys8 |Yes |Expired Keys (Shard 8) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|expiredkeys9 |Yes |Expired Keys (Shard 9) |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|GeoReplicationConnectivityLag |Yes |Geo-replication Connectivity Lag |Seconds |Average |[Preview] Time in seconds since last successful data synchronization with geo-primary cache. Value will continue to increase if the link status is down. For more details, see https://aka.ms/redis/georeplicationmetrics. |ShardId |

+|GeoReplicationDataSyncOffset |Yes |Geo-replication Data Sync Offset |Bytes |Average |[Preview] Approximate amount of data in bytes that needs to be synchronized to geo-secondary cache. For more details, see https://aka.ms/redis/georeplicationmetrics. |ShardId |

+|GeoReplicationFullSyncEventFinished |Yes |Geo-replication Full Sync Event Finished |Count |Count |[Preview] Fired on completion of a full synchronization event between geo-replicated caches. This metric reports 0 most of the time because geo-replication uses partial resynchronizations for any new data added after the initial full synchronization. For more details, see https://aka.ms/redis/georeplicationmetrics. |ShardId |

+|GeoReplicationFullSyncEventStarted |Yes |Geo-replication Full Sync Event Started |Count |Count |[Preview] Fired on initiation of a full synchronization event between geo-replicated caches. This metric reports 0 most of the time because geo-replication uses partial resynchronizations for any new data added after the initial full synchronization. For more details, see https://aka.ms/redis/georeplicationmetrics. |ShardId |

+|GeoReplicationHealthy |Yes |Geo-replication Healthy |Count |Minimum |[Preview] The health status of geo-replication link. 1 if healthy and 0 if disconnected or unhealthy. For more details, see https://aka.ms/redis/georeplicationmetrics. |ShardId |

+|getcommands |Yes |Gets |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|getcommands0 |Yes |Gets (Shard 0) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands1 |Yes |Gets (Shard 1) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands2 |Yes |Gets (Shard 2) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands3 |Yes |Gets (Shard 3) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands4 |Yes |Gets (Shard 4) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands5 |Yes |Gets (Shard 5) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands6 |Yes |Gets (Shard 6) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands7 |Yes |Gets (Shard 7) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands8 |Yes |Gets (Shard 8) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|getcommands9 |Yes |Gets (Shard 9) |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond |Yes |Operations Per Second |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|operationsPerSecond0 |Yes |Operations Per Second (Shard 0) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond1 |Yes |Operations Per Second (Shard 1) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond2 |Yes |Operations Per Second (Shard 2) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond3 |Yes |Operations Per Second (Shard 3) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond4 |Yes |Operations Per Second (Shard 4) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond5 |Yes |Operations Per Second (Shard 5) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond6 |Yes |Operations Per Second (Shard 6) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond7 |Yes |Operations Per Second (Shard 7) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond8 |Yes |Operations Per Second (Shard 8) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|operationsPerSecond9 |Yes |Operations Per Second (Shard 9) |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime |Yes |CPU |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|percentProcessorTime0 |Yes |CPU (Shard 0) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime1 |Yes |CPU (Shard 1) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime2 |Yes |CPU (Shard 2) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime3 |Yes |CPU (Shard 3) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime4 |Yes |CPU (Shard 4) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime5 |Yes |CPU (Shard 5) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime6 |Yes |CPU (Shard 6) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime7 |Yes |CPU (Shard 7) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime8 |Yes |CPU (Shard 8) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|percentProcessorTime9 |Yes |CPU (Shard 9) |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad |Yes |Server Load |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|serverLoad0 |Yes |Server Load (Shard 0) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad1 |Yes |Server Load (Shard 1) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad2 |Yes |Server Load (Shard 2) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad3 |Yes |Server Load (Shard 3) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad4 |Yes |Server Load (Shard 4) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad5 |Yes |Server Load (Shard 5) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad6 |Yes |Server Load (Shard 6) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad7 |Yes |Server Load (Shard 7) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad8 |Yes |Server Load (Shard 8) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|serverLoad9 |Yes |Server Load (Shard 9) |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands |Yes |Sets |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|setcommands0 |Yes |Sets (Shard 0) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands1 |Yes |Sets (Shard 1) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands2 |Yes |Sets (Shard 2) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands3 |Yes |Sets (Shard 3) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands4 |Yes |Sets (Shard 4) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands5 |Yes |Sets (Shard 5) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands6 |Yes |Sets (Shard 6) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands7 |Yes |Sets (Shard 7) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands8 |Yes |Sets (Shard 8) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|setcommands9 |Yes |Sets (Shard 9) |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed |Yes |Total Operations |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|totalcommandsprocessed0 |Yes |Total Operations (Shard 0) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed1 |Yes |Total Operations (Shard 1) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed2 |Yes |Total Operations (Shard 2) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed3 |Yes |Total Operations (Shard 3) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed4 |Yes |Total Operations (Shard 4) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed5 |Yes |Total Operations (Shard 5) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed6 |Yes |Total Operations (Shard 6) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed7 |Yes |Total Operations (Shard 7) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed8 |Yes |Total Operations (Shard 8) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalcommandsprocessed9 |Yes |Total Operations (Shard 9) |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys |Yes |Total Keys |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|totalkeys0 |Yes |Total Keys (Shard 0) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys1 |Yes |Total Keys (Shard 1) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys2 |Yes |Total Keys (Shard 2) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys3 |Yes |Total Keys (Shard 3) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys4 |Yes |Total Keys (Shard 4) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys5 |Yes |Total Keys (Shard 5) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys6 |Yes |Total Keys (Shard 6) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys7 |Yes |Total Keys (Shard 7) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys8 |Yes |Total Keys (Shard 8) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|totalkeys9 |Yes |Total Keys (Shard 9) |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory |Yes |Used Memory |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|usedmemory0 |Yes |Used Memory (Shard 0) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory1 |Yes |Used Memory (Shard 1) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory2 |Yes |Used Memory (Shard 2) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory3 |Yes |Used Memory (Shard 3) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory4 |Yes |Used Memory (Shard 4) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory5 |Yes |Used Memory (Shard 5) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory6 |Yes |Used Memory (Shard 6) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory7 |Yes |Used Memory (Shard 7) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory8 |Yes |Used Memory (Shard 8) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemory9 |Yes |Used Memory (Shard 9) |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemorypercentage |Yes |Used Memory Percentage |Percent |Maximum |The percentage of cache memory used for key/value pairs. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|usedmemoryRss |Yes |Used Memory RSS |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |ShardId |

+|usedmemoryRss0 |Yes |Used Memory RSS (Shard 0) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss1 |Yes |Used Memory RSS (Shard 1) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss2 |Yes |Used Memory RSS (Shard 2) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss3 |Yes |Used Memory RSS (Shard 3) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss4 |Yes |Used Memory RSS (Shard 4) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss5 |Yes |Used Memory RSS (Shard 5) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss6 |Yes |Used Memory RSS (Shard 6) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss7 |Yes |Used Memory RSS (Shard 7) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss8 |Yes |Used Memory RSS (Shard 8) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+|usedmemoryRss9 |Yes |Used Memory RSS (Shard 9) |Bytes |Maximum |The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics. |No Dimensions |

+## Microsoft.Cache/redisEnterprise

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|cachehits |Yes |Cache Hits |Count |Total |The number of successful key lookups. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|cacheLatency |Yes |Cache Latency Microseconds (Preview) |Count |Average |The latency to the cache in microseconds. For more details, see https://aka.ms/redis/enterprise/metrics. |InstanceId |

+|cachemisses |Yes |Cache Misses |Count |Total |The number of failed key lookups. For more details, see https://aka.ms/redis/enterprise/metrics. |InstanceId |

+|cacheRead |Yes |Cache Read |BytesPerSecond |Maximum |The amount of data read from the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/enterprise/metrics. |InstanceId |

+|cacheWrite |Yes |Cache Write |BytesPerSecond |Maximum |The amount of data written to the cache in Megabytes per second (MB/s). For more details, see https://aka.ms/redis/enterprise/metrics. |InstanceId |

+|connectedclients |Yes |Connected Clients |Count |Maximum |The number of client connections to the cache. For more details, see https://aka.ms/redis/enterprise/metrics. |InstanceId |

+|errors |Yes |Errors |Count |Maximum |The number errors that occurred on the cache. For more details, see https://aka.ms/redis/enterprise/metrics. |InstanceId, ErrorType |

+|evictedkeys |Yes |Evicted Keys |Count |Total |The number of items evicted from the cache. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|expiredkeys |Yes |Expired Keys |Count |Total |The number of items expired from the cache. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|geoReplicationHealthy |Yes |Geo Replication Healthy |Count |Maximum |The health of geo replication in an Active Geo-Replication group. 0 represents Unhealthy and 1 represents Healthy. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|getcommands |Yes |Gets |Count |Total |The number of get operations from the cache. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|operationsPerSecond |Yes |Operations Per Second |Count |Maximum |The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|percentProcessorTime |Yes |CPU |Percent |Maximum |The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/enterprise/metrics. |InstanceId |

+|serverLoad |Yes |Server Load |Percent |Maximum |The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|setcommands |Yes |Sets |Count |Total |The number of set operations to the cache. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|totalcommandsprocessed |Yes |Total Operations |Count |Total |The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|totalkeys |Yes |Total Keys |Count |Maximum |The total number of items in the cache. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|usedmemory |Yes |Used Memory |Bytes |Maximum |The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/enterprise/metrics. |No Dimensions |

+|usedmemorypercentage |Yes |Used Memory Percentage |Percent |Maximum |The percentage of cache memory used for key/value pairs. For more details, see https://aka.ms/redis/enterprise/metrics. |InstanceId |

+## Microsoft.Cdn/cdnwebapplicationfirewallpolicies

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|WebApplicationFirewallRequestCount |Yes |Web Application Firewall Request Count |Count |Total |The number of client requests processed by the Web Application Firewall |PolicyName, RuleName, Action |

+## Microsoft.Cdn/profiles

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|ByteHitRatio |Yes |Byte Hit Ratio |Percent |Average |This is the ratio of the total bytes served from the cache compared to the total response bytes |Endpoint |

+|OriginHealthPercentage |Yes |Origin Health Percentage |Percent |Average |The percentage of successful health probes from AFDX to backends. |Origin, OriginGroup |

+|OriginLatency |Yes |Origin Latency |MilliSeconds |Average |The time calculated from when the request was sent by AFDX edge to the backend until AFDX received the last response byte from the backend. |Origin, Endpoint |

+|OriginRequestCount |Yes |Origin Request Count |Count |Total |The number of requests sent from AFDX to origin. |HttpStatus, HttpStatusGroup, Origin, Endpoint |

+|Percentage4XX |Yes |Percentage of 4XX |Percent |Average |The percentage of all the client requests for which the response status code is 4XX |Endpoint, ClientRegion, ClientCountry |

+|Percentage5XX |Yes |Percentage of 5XX |Percent |Average |The percentage of all the client requests for which the response status code is 5XX |Endpoint, ClientRegion, ClientCountry |

+|RequestCount |Yes |Request Count |Count |Total |The number of client requests served by the HTTP/S proxy |HttpStatus, HttpStatusGroup, ClientRegion, ClientCountry, Endpoint |

+|RequestSize |Yes |Request Size |Bytes |Total |The number of bytes sent as requests from clients to AFDX. |HttpStatus, HttpStatusGroup, ClientRegion, ClientCountry, Endpoint |

+|ResponseSize |Yes |Response Size |Bytes |Total |The number of bytes sent as responses from HTTP/S proxy to clients |HttpStatus, HttpStatusGroup, ClientRegion, ClientCountry, Endpoint |

+|TotalLatency |Yes |Total Latency |MilliSeconds |Average |The time calculated from when the client request was received by the HTTP/S proxy until the client acknowledged the last response byte from the HTTP/S proxy |HttpStatus, HttpStatusGroup, ClientRegion, ClientCountry, Endpoint |

+|WebApplicationFirewallRequestCount |Yes |Web Application Firewall Request Count |Count |Total |The number of client requests processed by the Web Application Firewall |PolicyName, RuleName, Action |

+## Microsoft.ClassicCompute/domainNames/slots/roles

+<!-- Data source : arm-->

+|Disk Read Bytes/Sec |No |Disk Read |BytesPerSecond |Average |Average bytes read from disk during monitoring period. |RoleInstanceId |

+|Disk Read Operations/Sec |Yes |Disk Read Operations/Sec |CountPerSecond |Average |Disk Read IOPS. |RoleInstanceId |

+|Disk Write Bytes/Sec |No |Disk Write |BytesPerSecond |Average |Average bytes written to disk during monitoring period. |RoleInstanceId |

+|Disk Write Operations/Sec |Yes |Disk Write Operations/Sec |CountPerSecond |Average |Disk Write IOPS. |RoleInstanceId |

+|Network In |Yes |Network In |Bytes |Total |The number of bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic). |RoleInstanceId |

+|Network Out |Yes |Network Out |Bytes |Total |The number of bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic). |RoleInstanceId |

+|Percentage CPU |Yes |Percentage CPU |Percent |Average |The percentage of allocated compute units that are currently in use by the Virtual Machine(s). |RoleInstanceId |

+## Microsoft.ClassicCompute/virtualMachines

+<!-- Data source : arm-->

+|Disk Read Bytes/Sec |No |Disk Read |BytesPerSecond |Average |Average bytes read from disk during monitoring period. |No Dimensions |

+|Disk Read Operations/Sec |Yes |Disk Read Operations/Sec |CountPerSecond |Average |Disk Read IOPS. |No Dimensions |

+|Disk Write Bytes/Sec |No |Disk Write |BytesPerSecond |Average |Average bytes written to disk during monitoring period. |No Dimensions |

+|Disk Write Operations/Sec |Yes |Disk Write Operations/Sec |CountPerSecond |Average |Disk Write IOPS. |No Dimensions |

+|Network In |Yes |Network In |Bytes |Total |The number of bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic). |No Dimensions |

+|Network Out |Yes |Network Out |Bytes |Total |The number of bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic). |No Dimensions |

+|Percentage CPU |Yes |Percentage CPU |Percent |Average |The percentage of allocated compute units that are currently in use by the Virtual Machine(s). |No Dimensions |

+## Microsoft.ClassicStorage/storageAccounts

+<!-- Data source : arm-->

+|Availability |Yes |Availability |Percent |Average |The percentage of availability for the storage service or the specified API operation. Availability is calculated by taking the TotalBillableRequests value and dividing it by the number of applicable requests, including those that produced unexpected errors. All unexpected errors result in reduced availability for the storage service or the specified API operation. |GeoType, ApiName, Authentication |

+|Egress |Yes |Egress |Bytes |Total |The amount of egress data, in bytes. This number includes egress from an external client into Azure Storage as well as egress within Azure. As a result, this number does not reflect billable egress. |GeoType, ApiName, Authentication |

+|Ingress |Yes |Ingress |Bytes |Total |The amount of ingress data, in bytes. This number includes ingress from an external client into Azure Storage as well as ingress within Azure. |GeoType, ApiName, Authentication |

+|SuccessE2ELatency |Yes |Success E2E Latency |Milliseconds |Average |The end-to-end latency of successful requests made to a storage service or the specified API operation, in milliseconds. This value includes the required processing time within Azure Storage to read the request, send the response, and receive acknowledgment of the response. |GeoType, ApiName, Authentication |

+|SuccessServerLatency |Yes |Success Server Latency |Milliseconds |Average |The latency used by Azure Storage to process a successful request, in milliseconds. This value does not include the network latency specified in SuccessE2ELatency. |GeoType, ApiName, Authentication |

+|Transactions |Yes |Transactions |Count |Total |The number of requests made to a storage service or the specified API operation. This number includes successful and failed requests, as well as requests which produced errors. Use ResponseType dimension for the number of different type of response. |ResponseType, GeoType, ApiName, Authentication |

+|UsedCapacity |No |Used capacity |Bytes |Average |Account used capacity |No Dimensions |

+## Microsoft.ClassicStorage/storageAccounts/blobServices

+<!-- Data source : arm-->

+|Availability |Yes |Availability |Percent |Average |The percentage of availability for the storage service or the specified API operation. Availability is calculated by taking the TotalBillableRequests value and dividing it by the number of applicable requests, including those that produced unexpected errors. All unexpected errors result in reduced availability for the storage service or the specified API operation. |GeoType, ApiName, Authentication |

+|BlobCapacity |No |Blob Capacity |Bytes |Average |The amount of storage used by the storage account's Blob service in bytes. |BlobType, Tier |

+|BlobCount |No |Blob Count |Count |Average |The number of Blob in the storage account's Blob service. |BlobType, Tier |

+|ContainerCount |No |Blob Container Count |Count |Average |The number of containers in the storage account's Blob service. |No Dimensions |

+|Egress |Yes |Egress |Bytes |Total |The amount of egress data, in bytes. This number includes egress from an external client into Azure Storage as well as egress within Azure. As a result, this number does not reflect billable egress. |GeoType, ApiName, Authentication |

+|IndexCapacity |No |Index Capacity |Bytes |Average |The amount of storage used by ADLS Gen2 (Hierarchical) Index in bytes. |No Dimensions |

+|Ingress |Yes |Ingress |Bytes |Total |The amount of ingress data, in bytes. This number includes ingress from an external client into Azure Storage as well as ingress within Azure. |GeoType, ApiName, Authentication |

+|SuccessE2ELatency |Yes |Success E2E Latency |Milliseconds |Average |The end-to-end latency of successful requests made to a storage service or the specified API operation, in milliseconds. This value includes the required processing time within Azure Storage to read the request, send the response, and receive acknowledgment of the response. |GeoType, ApiName, Authentication |

+|SuccessServerLatency |Yes |Success Server Latency |Milliseconds |Average |The latency used by Azure Storage to process a successful request, in milliseconds. This value does not include the network latency specified in SuccessE2ELatency. |GeoType, ApiName, Authentication |

+|Transactions |Yes |Transactions |Count |Total |The number of requests made to a storage service or the specified API operation. This number includes successful and failed requests, as well as requests which produced errors. Use ResponseType dimension for the number of different type of response. |ResponseType, GeoType, ApiName, Authentication |

+## Microsoft.ClassicStorage/storageAccounts/fileServices

+<!-- Data source : arm-->

+|Availability |Yes |Availability |Percent |Average |The percentage of availability for the storage service or the specified API operation. Availability is calculated by taking the TotalBillableRequests value and dividing it by the number of applicable requests, including those that produced unexpected errors. All unexpected errors result in reduced availability for the storage service or the specified API operation. |GeoType, ApiName, Authentication, FileShare |

+|Egress |Yes |Egress |Bytes |Total |The amount of egress data, in bytes. This number includes egress from an external client into Azure Storage as well as egress within Azure. As a result, this number does not reflect billable egress. |GeoType, ApiName, Authentication, FileShare |

+|FileCapacity |No |File Capacity |Bytes |Average |The amount of storage used by the storage account's File service in bytes. |FileShare |

+|FileCount |No |File Count |Count |Average |The number of file in the storage account's File service. |FileShare |

+|FileShareCount |No |File Share Count |Count |Average |The number of file shares in the storage account's File service. |No Dimensions |

+|FileShareQuota |No |File share quota size |Bytes |Average |The upper limit on the amount of storage that can be used by Azure Files Service in bytes. |FileShare |

+|FileShareSnapshotCount |No |File Share Snapshot Count |Count |Average |The number of snapshots present on the share in storage account's Files Service. |FileShare |

+|FileShareSnapshotSize |No |File Share Snapshot Size |Bytes |Average |The amount of storage used by the snapshots in storage account's File service in bytes. |FileShare |

+|Ingress |Yes |Ingress |Bytes |Total |The amount of ingress data, in bytes. This number includes ingress from an external client into Azure Storage as well as ingress within Azure. |GeoType, ApiName, Authentication, FileShare |

+|SuccessE2ELatency |Yes |Success E2E Latency |Milliseconds |Average |The end-to-end latency of successful requests made to a storage service or the specified API operation, in milliseconds. This value includes the required processing time within Azure Storage to read the request, send the response, and receive acknowledgment of the response. |GeoType, ApiName, Authentication, FileShare |

+|SuccessServerLatency |Yes |Success Server Latency |Milliseconds |Average |The latency used by Azure Storage to process a successful request, in milliseconds. This value does not include the network latency specified in SuccessE2ELatency. |GeoType, ApiName, Authentication, FileShare |

+|Transactions |Yes |Transactions |Count |Total |The number of requests made to a storage service or the specified API operation. This number includes successful and failed requests, as well as requests which produced errors. Use ResponseType dimension for the number of different type of response. |ResponseType, GeoType, ApiName, Authentication, FileShare |

+## Microsoft.ClassicStorage/storageAccounts/queueServices

+<!-- Data source : arm-->

+|Availability |Yes |Availability |Percent |Average |The percentage of availability for the storage service or the specified API operation. Availability is calculated by taking the TotalBillableRequests value and dividing it by the number of applicable requests, including those that produced unexpected errors. All unexpected errors result in reduced availability for the storage service or the specified API operation. |GeoType, ApiName, Authentication |

+|Egress |Yes |Egress |Bytes |Total |The amount of egress data, in bytes. This number includes egress from an external client into Azure Storage as well as egress within Azure. As a result, this number does not reflect billable egress. |GeoType, ApiName, Authentication |

+|Ingress |Yes |Ingress |Bytes |Total |The amount of ingress data, in bytes. This number includes ingress from an external client into Azure Storage as well as ingress within Azure. |GeoType, ApiName, Authentication |

+|QueueCapacity |Yes |Queue Capacity |Bytes |Average |The amount of storage used by the storage account's Queue service in bytes. |No Dimensions |

+|QueueCount |Yes |Queue Count |Count |Average |The number of queue in the storage account's Queue service. |No Dimensions |

+|QueueMessageCount |Yes |Queue Message Count |Count |Average |The approximate number of queue messages in the storage account's Queue service. |No Dimensions |

+|SuccessE2ELatency |Yes |Success E2E Latency |Milliseconds |Average |The end-to-end latency of successful requests made to a storage service or the specified API operation, in milliseconds. This value includes the required processing time within Azure Storage to read the request, send the response, and receive acknowledgment of the response. |GeoType, ApiName, Authentication |

+|SuccessServerLatency |Yes |Success Server Latency |Milliseconds |Average |The latency used by Azure Storage to process a successful request, in milliseconds. This value does not include the network latency specified in SuccessE2ELatency. |GeoType, ApiName, Authentication |

+|Transactions |Yes |Transactions |Count |Total |The number of requests made to a storage service or the specified API operation. This number includes successful and failed requests, as well as requests which produced errors. Use ResponseType dimension for the number of different type of response. |ResponseType, GeoType, ApiName, Authentication |

+## Microsoft.ClassicStorage/storageAccounts/tableServices

+<!-- Data source : arm-->

+|Availability |Yes |Availability |Percent |Average |The percentage of availability for the storage service or the specified API operation. Availability is calculated by taking the TotalBillableRequests value and dividing it by the number of applicable requests, including those that produced unexpected errors. All unexpected errors result in reduced availability for the storage service or the specified API operation. |GeoType, ApiName, Authentication |

+|Egress |Yes |Egress |Bytes |Total |The amount of egress data, in bytes. This number includes egress from an external client into Azure Storage as well as egress within Azure. As a result, this number does not reflect billable egress. |GeoType, ApiName, Authentication |

+|Ingress |Yes |Ingress |Bytes |Total |The amount of ingress data, in bytes. This number includes ingress from an external client into Azure Storage as well as ingress within Azure. |GeoType, ApiName, Authentication |

+|SuccessE2ELatency |Yes |Success E2E Latency |Milliseconds |Average |The end-to-end latency of successful requests made to a storage service or the specified API operation, in milliseconds. This value includes the required processing time within Azure Storage to read the request, send the response, and receive acknowledgment of the response. |GeoType, ApiName, Authentication |

+|SuccessServerLatency |Yes |Success Server Latency |Milliseconds |Average |The latency used by Azure Storage to process a successful request, in milliseconds. This value does not include the network latency specified in SuccessE2ELatency. |GeoType, ApiName, Authentication |

+|TableCapacity |No |Table Capacity |Bytes |Average |The amount of storage used by the storage account's Table service in bytes. |No Dimensions |

+|TableCount |No |Table Count |Count |Average |The number of table in the storage account's Table service. |No Dimensions |

+|TableEntityCount |No |Table Entity Count |Count |Average |The number of table entities in the storage account's Table service. |No Dimensions |

+|Transactions |Yes |Transactions |Count |Total |The number of requests made to a storage service or the specified API operation. This number includes successful and failed requests, as well as requests which produced errors. Use ResponseType dimension for the number of different type of response. |ResponseType, GeoType, ApiName, Authentication |

+## Microsoft.Cloudtest/hostedpools

+<!-- Data source : naam-->

+|Allocated |Yes |Allocated |Count |Average |Resources that are allocated |PoolId, SKU, Images, ProviderName |

+|AllocationDurationMs |Yes |AllocationDurationMs |Milliseconds |Average |Average time to allocate requests (ms) |PoolId, Type, ResourceRequestType, Image |

+|Count |Yes |Count |Count |Count |Number of requests in last dump |RequestType, Status, PoolId, Type, ErrorCode, FailureStage |

+|NotReady |Yes |NotReady |Count |Average |Resources that are not ready to be used |PoolId, SKU, Images, ProviderName |

+|PendingReimage |Yes |PendingReimage |Count |Average |Resources that are pending reimage |PoolId, SKU, Images, ProviderName |

+|PendingReturn |Yes |PendingReturn |Count |Average |Resources that are pending return |PoolId, SKU, Images, ProviderName |

+|Provisioned |Yes |Provisioned |Count |Average |Resources that are provisioned |PoolId, SKU, Images, ProviderName |

+|Ready |Yes |Ready |Count |Average |Resources that are ready to be used |PoolId, SKU, Images, ProviderName |

+|Starting |Yes |Starting |Count |Average |Resources that are starting |PoolId, SKU, Images, ProviderName |

+|Total |Yes |Total |Count |Average |Total Number of Resources |PoolId, SKU, Images, ProviderName |

+## Microsoft.Cloudtest/pools

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|Allocated |Yes |Allocated |Count |Average |Resources that are allocated |PoolId, SKU, Images, ProviderName |

+|AllocationDurationMs |Yes |AllocationDurationMs |Milliseconds |Average |Average time to allocate requests (ms) |PoolId, Type, ResourceRequestType, Image |

+|Count |Yes |Count |Count |Count |Number of requests in last dump |RequestType, Status, PoolId, Type, ErrorCode, FailureStage |

+|NotReady |Yes |NotReady |Count |Average |Resources that are not ready to be used |PoolId, SKU, Images, ProviderName |

+|PendingReimage |Yes |PendingReimage |Count |Average |Resources that are pending reimage |PoolId, SKU, Images, ProviderName |

+|PendingReturn |Yes |PendingReturn |Count |Average |Resources that are pending return |PoolId, SKU, Images, ProviderName |

+|Provisioned |Yes |Provisioned |Count |Average |Resources that are provisioned |PoolId, SKU, Images, ProviderName |

+|Ready |Yes |Ready |Count |Average |Resources that are ready to be used |PoolId, SKU, Images, ProviderName |

+|Starting |Yes |Starting |Count |Average |Resources that are starting |PoolId, SKU, Images, ProviderName |

+|Total |Yes |Total |Count |Average |Total Number of Resources |PoolId, SKU, Images, ProviderName |

+## Microsoft.ClusterStor/nodes

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|TotalCapacityAvailable |No |TotalCapacityAvailable |Bytes |Average |The total capacity available in lustre file system |filesystem_name, category, system |

+|TotalCapacityUsed |No |TotalCapacityUsed |Bytes |Average |The total capacity used in lustre file system |filesystem_name, category, system |

+|TotalRead |No |TotalRead |BytesPerSecond |Average |The total lustre file system read per second |filesystem_name, category, system |

+|TotalWrite |No |TotalWrite |BytesPerSecond |Average |The total lustre file system write per second |filesystem_name, category, system |

+## Microsoft.CodeSigning/codesigningaccounts

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|SignCompleted |Yes |SignCompleted |Count |Count |Completed Sign Request |CertType, Region, TenantId |

+|SignFailed |Yes |SignFailed |Count |Count |Failed Sign Request |CertType, Region, TenantId |

+## Microsoft.CognitiveServices/accounts

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|ActionFeatureIdOccurrences |Yes |Action Feature Occurrences |Count |Total |Number of times each action feature appears. |FeatureId, Mode, RunId |

+|ActionFeaturesPerEvent |Yes |Action Features Per Event |Count |Average |Average number of action features per event. |Mode, RunId |

+|ActionIdOccurrences |Yes |Action Occurrences |Count |Total |Number of times each action appears. |ActionId, Mode, RunId |

+|ActionNamespacesPerEvent |Yes |Action Namespaces Per Event |Count |Average |Average number of action namespaces per event. |Mode, RunId |

+|ActionsPerEvent |Yes |Actions Per Event |Count |Average |Number of actions per event. |Mode, RunId |

+|AdaFineTunedTokenTransaction |Yes |Processed Ada FineTuned Inference Tokens |Count |Total |Number of Inference Tokens Processed on an Ada FineTuned Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|AdaFineTunedTrainingHours |Yes |Processed Ada FineTuned Training Hours |Count |Total |Number of Training Hours Processed on an Ada FineTuned Model |ApiName, FeatureName, UsageChannel, Region |

+|AdaTokenTransaction |Yes |Processed Ada Inference Tokens |Count |Total |Number of Inference Tokens Processed on an Ada Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|AudioSecondsTranscribed |Yes |Audio Seconds Transcribed |Count |Total |Number of seconds transcribed |ApiName, FeatureName, UsageChannel, Region |

+|AudioSecondsTranslated |Yes |Audio Seconds Translated |Count |Total |Number of seconds translated |ApiName, FeatureName, UsageChannel, Region |

+|BabbageFineTunedTokenTransaction |Yes |Processed Babbage FineFuned Inference Tokens |Count |Total |Number of Inference Tokens processed on a Babbage FineFuned Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|BabbageFineTunedTrainingHours |Yes |Processed Babbage FineTuned Training Hours |Count |Total |Number of Training Hours Processed on a Babbage FineTuned Model |ApiName, FeatureName, UsageChannel, Region |

+|BabbageTokenTransaction |Yes |Processed Babbage Inference Tokens |Count |Total |Number of Inference Tokens Processed on a Babbage Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|BaselineEstimatorSlotReward |Yes |Baseline Estimator Slot Reward |Count |Average |Baseline Estimator Reward by slot. |SlotId, SlotIndex, Mode, RunId |

+|BaselineRandomEstimatorSlotReward |Yes |Baseline Random Estimator Slot Reward |Count |Average |Baseline Random Estimator Reward by slot. |SlotId, SlotIndex, Mode, RunId |

+|BaselineRandomEventCount |Yes |Baseline Random Event count |Count |Total |Estimation for baseline random event count. |Mode, RunId |

+|BaselineRandomReward |Yes |Baseline Random Reward |Count |Total |Estimation for baseline random reward. |Mode, RunId |

+|BlockedCalls |Yes |Blocked Calls |Count |Total |Number of calls that exceeded rate or quota limit. |ApiName, OperationName, Region, RatelimitKey |

+|CharactersTrained |Yes |Characters Trained (Deprecated) |Count |Total |Total number of characters trained. |ApiName, OperationName, Region |

+|CharactersTranslated |Yes |Characters Translated (Deprecated) |Count |Total |Total number of characters in incoming text request. |ApiName, OperationName, Region |

+|ClientErrors |Yes |Client Errors |Count |Total |Number of calls with client side error (HTTP response code 4xx). |ApiName, OperationName, Region, RatelimitKey |

+|CodeCushman001FineTunedTokenTransaction |Yes |Processed Code-Cushman-001 FineTuned Inference Tokens |Count |Total |Number of Inference Tokens Processed on a Code-Cushman-001 FineTuned Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|CodeCushman001FineTunedTrainingHours |Yes |Processed Code-Cushman-001 FineTuned Training Hours |Count |Total |Number of Training Hours Processed on a Code-Cushman-001 FineTuned Model |ApiName, FeatureName, UsageChannel, Region |

+|CodeCushman001TokenTransaction |Yes |Processed Code-Cushman-001 Inference Tokens |Count |Total |Number of Inference Tokens Processed on a Code-Cushman-001 Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|ComputerVisionTransactions |Yes |Computer Vision Transactions |Count |Total |Number of Computer Vision Transactions |ApiName, FeatureName, UsageChannel, Region |

+|ContextFeatureIdOccurrences |Yes |Context Feature Occurrences |Count |Total |Number of times each context feature appears. |FeatureId, Mode, RunId |

+|ContextFeaturesPerEvent |Yes |Context Features Per Event |Count |Average |Number of context features per event. |Mode, RunId |

+|ContextNamespacesPerEvent |Yes |Context Namespaces Per Event |Count |Average |Number of context namespaces per event. |Mode, RunId |

+|CurieFineTunedTokenTransaction |Yes |Processed Curie FineTuned Inference Tokens |Count |Total |Number of Inference Tokens processed on a Curie FineTuned Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|CurieFineTunedTrainingHours |Yes |Processed Curie FineTuned Training Hours |Count |Total |Number of Training Hours Processed on a Curie FineTuned Model |ApiName, FeatureName, UsageChannel, Region |

+|CurieTokenTransaction |Yes |Processed Curie Inference Tokens |Count |Total |Number of Inference Tokens Processed on a Curie Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|CustomVisionTrainingTime |Yes |Custom Vision Training Time |Seconds |Total |Custom Vision training time |ApiName, FeatureName, UsageChannel, Region |

+|CustomVisionTransactions |Yes |Custom Vision Transactions |Count |Total |Number of Custom Vision prediction transactions |ApiName, FeatureName, UsageChannel, Region |

+|DataIn |Yes |Data In |Bytes |Total |Size of incoming data in bytes. |ApiName, OperationName, Region |

+|DataOut |Yes |Data Out |Bytes |Total |Size of outgoing data in bytes. |ApiName, OperationName, Region |

+|DavinciFineTunedTokenTransaction |Yes |Processed Davinci FineTuned Inference Tokens |Count |Total |Number of Inference Tokens Processed on a Davinci FineTuned Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|DavinciFineTunedTrainingHours |Yes |Processed Davinci FineTuned Training Hours |Count |Total |Number of Training Hours Processed on a Davinci FineTuned Model |ApiName, FeatureName, UsageChannel, Region |

+|DavinciTokenTransaction |Yes |Processed Davinci Inference Tokens |Count |Total |Number of Inference Tokens Processed on a Davinci Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|DocumentCharactersTranslated |Yes |Document Characters Translated |Count |Total |Number of characters in document translation request. |ApiName, FeatureName, UsageChannel, Region |

+|DocumentCustomCharactersTranslated |Yes |Document Custom Characters Translated |Count |Total |Number of characters in custom document translation request. |ApiName, FeatureName, UsageChannel, Region |

+|FaceImagesTrained |Yes |Face Images Trained |Count |Total |Number of images trained. 1,000 images trained per transaction. |ApiName, FeatureName, UsageChannel, Region |

+|FacesStored |Yes |Faces Stored |Count |Total |Number of faces stored, prorated daily. The number of faces stored is reported daily. |ApiName, FeatureName, UsageChannel, Region |

+|FaceTransactions |Yes |Face Transactions |Count |Total |Number of API calls made to Face service |ApiName, FeatureName, UsageChannel, Region |

+|FeatureCardinality_Action |Yes |Feature Cardinality by Action |Count |Average |Feature Cardinality based on Action. |FeatureId, Mode, RunId |

+|FeatureCardinality_Context |Yes |Feature Cardinality by Context |Count |Average |Feature Cardinality based on Context. |FeatureId, Mode, RunId |

+|FeatureCardinality_Slot |Yes |Feature Cardinality by Slot |Count |Average |Feature Cardinality based on Slot. |FeatureId, Mode, RunId |

+|FineTunedTrainingHours |Yes |Processed FineTuned Training Hours |Count |Total |Number of Training Hours Processed on an OpenAI FineTuned Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|ImagesStored |Yes |Images Stored |Count |Total |Number of Custom Vision images stored. |ApiName, FeatureName, UsageChannel, Region |

+|Latency |Yes |Latency |MilliSeconds |Average |Latency in milliseconds. |ApiName, OperationName, Region, RatelimitKey |

+|LearnedEvents |Yes |Learned Events |Count |Total |Number of Learned Events. |IsMatchBaseline, Mode, RunId |

+|LUISSpeechRequests |Yes |LUIS Speech Requests |Count |Total |Number of LUIS speech to intent understanding requests |ApiName, FeatureName, UsageChannel, Region |

+|LUISTextRequests |Yes |LUIS Text Requests |Count |Total |Number of LUIS text requests |ApiName, FeatureName, UsageChannel, Region |

+|MatchedRewards |Yes |Matched Rewards |Count |Total |Number of Matched Rewards. |Mode, RunId |

+|NonActivatedEvents |Yes |Non Activated Events |Count |Total |Number of skipped events. |Mode, RunId |

+|NumberOfSlots |Yes |Slots |Count |Average |Number of slots per event. |Mode, RunId |

+|NumberofSpeakerProfiles |Yes |Number of Speaker Profiles |Count |Total |Number of speaker profiles enrolled. Prorated hourly. |ApiName, FeatureName, UsageChannel, Region |

+|ObservedRewards |Yes |Observed Rewards |Count |Total |Number of Observed Rewards. |Mode, RunId |

+|OnlineEstimatorSlotReward |Yes |Online Estimator Slot Reward |Count |Average |Online Estimator Reward by slot. |SlotId, SlotIndex, Mode, RunId |

+|OnlineEventCount |Yes |Online Event Count |Count |Total |Estimation for online event count. |Mode, RunId |

+|OnlineReward |Yes |Online Reward |Count |Total |Estimation for online reward. |Mode, RunId |

+|ProcessedCharacters |Yes |Processed Characters |Count |Total |Number of Characters processed by Immersive Reader. |ApiName, FeatureName, UsageChannel, Region |

+|ProcessedHealthTextRecords |Yes |Processed Health Text Records |Count |Total |Number of health text records processed |ApiName, FeatureName, UsageChannel, Region |

+|ProcessedImages |Yes |Processed Images |Count |Total |Number of images processed |ApiName, FeatureName, UsageChannel, Region |

+|ProcessedPages |Yes |Processed Pages |Count |Total |Number of pages processed |ApiName, FeatureName, UsageChannel, Region |

+|ProcessedTextRecords |Yes |Processed Text Records |Count |Total |Count of Text Records. |ApiName, FeatureName, UsageChannel, Region |

+|QuestionAnsweringTextRecords |Yes |QA Text Records |Count |Total |Number of text records processed |ApiName, FeatureName, UsageChannel, Region |

+|Ratelimit |Yes |Ratelimit |Count |Total |The current ratelimit of the ratelimit key. |Region, RatelimitKey |

+|Reward |Yes |Average Reward Per Event |Count |Average |Average reward per event. |BaselineAction, ChosenActionId, MatchesBaseline, NonDefaultReward, Mode, RunId |

+|ServerErrors |Yes |Server Errors |Count |Total |Number of calls with service internal error (HTTP response code 5xx). |ApiName, OperationName, Region, RatelimitKey |

+|SlotFeatureIdOccurrences |Yes |Slot Feature Occurrences |Count |Total |Number of times each slot feature appears. |FeatureId, Mode, RunId |

+|SlotFeaturesPerEvent |Yes |Slot Features Per Event |Count |Average |Average number of slot features per event. |Mode, RunId |

+|SlotIdOccurrences |Yes |Slot Occurrences |Count |Total |Number of times each slot appears. |SlotId, SlotIndex, Mode, RunId |

+|SlotNamespacesPerEvent |Yes |Slot Namespaces Per Event |Count |Average |Average number of slot namespaces per event. |Mode, RunId |

+|SlotReward |Yes |Slot Reward |Count |Average |Reward per slot. |BaselineActionId, ChosenActionId, MatchesBaseline, NonDefaultReward, SlotId, SlotIndex, Mode, RunId |

+|SpeakerRecognitionTransactions |Yes |Speaker Recognition Transactions |Count |Total |Number of speaker recognition transactions |ApiName, FeatureName, UsageChannel, Region |

+|SpeechModelHostingHours |Yes |Speech Model Hosting Hours |Count |Total |Number of speech model hosting hours |ApiName, FeatureName, UsageChannel, Region |

+|SpeechSessionDuration |Yes |Speech Session Duration (Deprecated) |Seconds |Total |Total duration of speech session in seconds. |ApiName, OperationName, Region |

+|SuccessfulCalls |Yes |Successful Calls |Count |Total |Number of successful calls. |ApiName, OperationName, Region, RatelimitKey |

+|SynthesizedCharacters |Yes |Synthesized Characters |Count |Total |Number of Characters. |ApiName, FeatureName, UsageChannel, Region |

+|TextAda001TokenTransaction |Yes |Processed Text Ada 001 Inference Tokens |Count |Total |Number of Inference Tokens processed on a text-ada-001 model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|TextBabbage001TokenTransaction |Yes |Processed Text Babbage 001 Inference Tokens |Count |Total |Number of Inference Tokens processed on a text-babbage-001 model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|TextCharactersTranslated |Yes |Text Characters Translated |Count |Total |Number of characters in incoming text translation request. |ApiName, FeatureName, UsageChannel, Region |

+|TextCurie001TokenTransaction |Yes |Processed Text Curie 001 Inference Tokens |Count |Total |Number of Inference Tokens Processed on a text-curie-001 Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|TextCustomCharactersTranslated |Yes |Text Custom Characters Translated |Count |Total |Number of characters in incoming custom text translation request. |ApiName, FeatureName, UsageChannel, Region |

+|TextDavinci001TokenTransaction |Yes |Processed Text Davinci 001 Inference Tokens |Count |Total |Number of Inference Tokens Processed on a text-davinci-001 Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|TextDavinci002TokenTransaction |Yes |Processed Text Davinci 002 Inference Tokens |Count |Total |Number of Inference Tokens Processed on a text-davinci-002 Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|TextTrainedCharacters |Yes |Text Trained Characters |Count |Total |Number of characters trained using text translation. |ApiName, FeatureName, UsageChannel, Region |

+|TokenTransaction |Yes |Processed Inference Tokens |Count |Total |Number of Inference Tokens Processed on an OpenAI Model |ApiName, ModelDeploymentName, FeatureName, UsageChannel, Region |

+|TotalCalls |Yes |Total Calls |Count |Total |Total number of calls. |ApiName, OperationName, Region, RatelimitKey |

+|TotalErrors |Yes |Total Errors |Count |Total |Total number of calls with error response (HTTP response code 4xx or 5xx). |ApiName, OperationName, Region, RatelimitKey |

+|TotalEvents |Yes |Total Events |Count |Total |Number of events. |Mode, RunId |

+|TotalTokenCalls |Yes |Total Token Calls |Count |Total |Total number of token calls. |ApiName, OperationName, Region |

+|TotalTransactions |Yes |Total Transactions (Deprecated) |Count |Total |Total number of transactions. |No Dimensions |

+|UserBaselineEventCount |Yes |User Baseline Event Count |Count |Total |Estimation for user defined baseline event count. |Mode, RunId |

+|UserBaselineReward |Yes |User Baseline Reward |Count |Total |Estimation for user defined baseline reward. |Mode, RunId |

+|VoiceModelHostingHours |Yes |Voice Model Hosting Hours |Count |Total |Number of Hours. |ApiName, FeatureName, UsageChannel, Region |

+|VoiceModelTrainingMinutes |Yes |Voice Model Training Minutes |Count |Total |Number of Minutes. |ApiName, FeatureName, UsageChannel, Region |

+## Microsoft.Communication/CommunicationServices

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|APIRequestAuthentication |No |Authentication API Requests |Count |Count |Count of all requests against the Communication Services Authentication endpoint. |Operation, StatusCode, StatusCodeClass |

+|APIRequestCallAutomation |Yes |Call Automation API Requests |Count |Count |Count of all requests against the Communication Call Automation endpoint. |Operation, StatusCode, StatusCodeClass |

+|APIRequestCallRecording |Yes |Call Recording API Requests |Count |Count |Count of all requests against the Communication Services Call Recording endpoint. |Operation, StatusCode, StatusCodeClass |

+|APIRequestChat |Yes |Chat API Requests |Count |Count |Count of all requests against the Communication Services Chat endpoint. |Operation, StatusCode, StatusCodeClass |

+|APIRequestNetworkTraversal |No |Network Traversal API Requests |Count |Count |Count of all requests against the Communication Services Network Traversal endpoint. |Operation, StatusCode, StatusCodeClass |

+|ApiRequestRooms |Yes |Rooms API Requests |Count |Count |Count of all requests against the Communication Services Rooms endpoint. |Operation, StatusCode, StatusCodeClass |

+|ApiRequests |Yes |Email Service API Requests |Count |Count |Email Communication Services API request metric for the data-plane API surface. |Operation, StatusCode, StatusCodeClass, StatusCodeReason |

+|APIRequestSMS |Yes |SMS API Requests |Count |Count |Count of all requests against the Communication Services SMS endpoint. |Operation, StatusCode, StatusCodeClass, ErrorCode, NumberType |

+|DeliveryStatusUpdate |Yes |Email Service Delivery Status Updates |Count |Count |Email Communication Services message delivery results. |MessageStatus, Result |

+|UserEngagement |Yes |Email Service User Engagement |Count |Count |Email Communication Services user engagement metrics. |EngagementType |

+## Microsoft.Compute/cloudservices

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|Available Memory Bytes |Yes |Available Memory Bytes (Preview) |Bytes |Average |Amount of physical memory, in bytes, immediately available for allocation to a process or for system use in the Virtual Machine |RoleInstanceId, RoleId |

+|Disk Read Bytes |Yes |Disk Read Bytes |Bytes |Total |Bytes read from disk during monitoring period |RoleInstanceId, RoleId |

+|Disk Read Operations/Sec |Yes |Disk Read Operations/Sec |CountPerSecond |Average |Disk Read IOPS |RoleInstanceId, RoleId |

+|Disk Write Bytes |Yes |Disk Write Bytes |Bytes |Total |Bytes written to disk during monitoring period |RoleInstanceId, RoleId |

+|Disk Write Operations/Sec |Yes |Disk Write Operations/Sec |CountPerSecond |Average |Disk Write IOPS |RoleInstanceId, RoleId |

+|Network In Total |Yes |Network In Total |Bytes |Total |The number of bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic) |RoleInstanceId, RoleId |

+|Network Out Total |Yes |Network Out Total |Bytes |Total |The number of bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic) |RoleInstanceId, RoleId |

+|Percentage CPU |Yes |Percentage CPU |Percent |Average |The percentage of allocated compute units that are currently in use by the Virtual Machine(s) |RoleInstanceId, RoleId |

+## Microsoft.Compute/cloudServices/roles

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|Available Memory Bytes |Yes |Available Memory Bytes (Preview) |Bytes |Average |Amount of physical memory, in bytes, immediately available for allocation to a process or for system use in the Virtual Machine |RoleInstanceId, RoleId |

+|Disk Read Bytes |Yes |Disk Read Bytes |Bytes |Total |Bytes read from disk during monitoring period |RoleInstanceId, RoleId |

+|Disk Read Operations/Sec |Yes |Disk Read Operations/Sec |CountPerSecond |Average |Disk Read IOPS |RoleInstanceId, RoleId |

+|Disk Write Bytes |Yes |Disk Write Bytes |Bytes |Total |Bytes written to disk during monitoring period |RoleInstanceId, RoleId |

+|Disk Write Operations/Sec |Yes |Disk Write Operations/Sec |CountPerSecond |Average |Disk Write IOPS |RoleInstanceId, RoleId |

+|Network In Total |Yes |Network In Total |Bytes |Total |The number of bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic) |RoleInstanceId, RoleId |

+|Network Out Total |Yes |Network Out Total |Bytes |Total |The number of bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic) |RoleInstanceId, RoleId |

+|Percentage CPU |Yes |Percentage CPU |Percent |Average |The percentage of allocated compute units that are currently in use by the Virtual Machine(s) |RoleInstanceId, RoleId |

+## microsoft.compute/disks

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|Composite Disk Read Bytes/sec |No |Disk Read Bytes/sec(Preview) |BytesPerSecond |Average |Bytes/sec read from disk during monitoring period, please note, this metric is in preview and is subject to change before becoming generally available |No Dimensions |

+|Composite Disk Read Operations/sec |No |Disk Read Operations/sec(Preview) |CountPerSecond |Average |Number of read IOs performed on a disk during monitoring period, please note, this metric is in preview and is subject to change before becoming generally available |No Dimensions |

+|Composite Disk Write Bytes/sec |No |Disk Write Bytes/sec(Preview) |BytesPerSecond |Average |Bytes/sec written to disk during monitoring period, please note, this metric is in preview and is subject to change before becoming generally available |No Dimensions |

+|Composite Disk Write Operations/sec |No |Disk Write Operations/sec(Preview) |CountPerSecond |Average |Number of Write IOs performed on a disk during monitoring period, please note, this metric is in preview and is subject to change before becoming generally available |No Dimensions |

+|DiskPaidBurstIOPS |No |Disk On-demand Burst Operations(Preview) |Count |Average |The accumulated operations of burst transactions used for disks with on-demand burst enabled. Emitted on an hour interval |No Dimensions |

+## Microsoft.Compute/virtualMachines

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|Available Memory Bytes |Yes |Available Memory Bytes (Preview) |Bytes |Average |Amount of physical memory, in bytes, immediately available for allocation to a process or for system use in the Virtual Machine |No Dimensions |

+|CPU Credits Consumed |Yes |CPU Credits Consumed |Count |Average |Total number of credits consumed by the Virtual Machine. Only available on B-series burstable VMs |No Dimensions |

+|CPU Credits Remaining |Yes |CPU Credits Remaining |Count |Average |Total number of credits available to burst. Only available on B-series burstable VMs |No Dimensions |

+|Data Disk Bandwidth Consumed Percentage |Yes |Data Disk Bandwidth Consumed Percentage |Percent |Average |Percentage of data disk bandwidth consumed per minute |LUN |

+|Data Disk IOPS Consumed Percentage |Yes |Data Disk IOPS Consumed Percentage |Percent |Average |Percentage of data disk I/Os consumed per minute |LUN |

+|Data Disk Max Burst Bandwidth |Yes |Data Disk Max Burst Bandwidth |Count |Average |Maximum bytes per second throughput Data Disk can achieve with bursting |LUN |

+|Data Disk Max Burst IOPS |Yes |Data Disk Max Burst IOPS |Count |Average |Maximum IOPS Data Disk can achieve with bursting |LUN |

+|Data Disk Queue Depth |Yes |Data Disk Queue Depth |Count |Average |Data Disk Queue Depth(or Queue Length) |LUN |

+|Data Disk Read Bytes/sec |Yes |Data Disk Read Bytes/Sec |BytesPerSecond |Average |Bytes/Sec read from a single disk during monitoring period |LUN |

+|Data Disk Read Operations/Sec |Yes |Data Disk Read Operations/Sec |CountPerSecond |Average |Read IOPS from a single disk during monitoring period |LUN |

+|Data Disk Target Bandwidth |Yes |Data Disk Target Bandwidth |Count |Average |Baseline bytes per second throughput Data Disk can achieve without bursting |LUN |

+|Data Disk Target IOPS |Yes |Data Disk Target IOPS |Count |Average |Baseline IOPS Data Disk can achieve without bursting |LUN |

+|Data Disk Used Burst BPS Credits Percentage |Yes |Data Disk Used Burst BPS Credits Percentage |Percent |Average |Percentage of Data Disk burst bandwidth credits used so far |LUN |

+|Data Disk Used Burst IO Credits Percentage |Yes |Data Disk Used Burst IO Credits Percentage |Percent |Average |Percentage of Data Disk burst I/O credits used so far |LUN |

+|Data Disk Write Bytes/sec |Yes |Data Disk Write Bytes/Sec |BytesPerSecond |Average |Bytes/Sec written to a single disk during monitoring period |LUN |

+|Data Disk Write Operations/Sec |Yes |Data Disk Write Operations/Sec |CountPerSecond |Average |Write IOPS from a single disk during monitoring period |LUN |

+|Disk Read Bytes |Yes |Disk Read Bytes |Bytes |Total |Bytes read from disk during monitoring period |No Dimensions |

+|Disk Read Operations/Sec |Yes |Disk Read Operations/Sec |CountPerSecond |Average |Disk Read IOPS |No Dimensions |

+|Disk Write Bytes |Yes |Disk Write Bytes |Bytes |Total |Bytes written to disk during monitoring period |No Dimensions |

+|Disk Write Operations/Sec |Yes |Disk Write Operations/Sec |CountPerSecond |Average |Disk Write IOPS |No Dimensions |

+|Inbound Flows |Yes |Inbound Flows |Count |Average |Inbound Flows are number of current flows in the inbound direction (traffic going into the VM) |No Dimensions |

+|Inbound Flows Maximum Creation Rate |Yes |Inbound Flows Maximum Creation Rate |CountPerSecond |Average |The maximum creation rate of inbound flows (traffic going into the VM) |No Dimensions |

+|Network In |Yes |Network In Billable (Deprecated) |Bytes |Total |The number of billable bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic) (Deprecated) |No Dimensions |

+|Network In Total |Yes |Network In Total |Bytes |Total |The number of bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic) |No Dimensions |

+|Network Out |Yes |Network Out Billable (Deprecated) |Bytes |Total |The number of billable bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic) (Deprecated) |No Dimensions |

+|Network Out Total |Yes |Network Out Total |Bytes |Total |The number of bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic) |No Dimensions |

+|OS Disk Bandwidth Consumed Percentage |Yes |OS Disk Bandwidth Consumed Percentage |Percent |Average |Percentage of operating system disk bandwidth consumed per minute |LUN |

+|OS Disk IOPS Consumed Percentage |Yes |OS Disk IOPS Consumed Percentage |Percent |Average |Percentage of operating system disk I/Os consumed per minute |LUN |

+|OS Disk Max Burst Bandwidth |Yes |OS Disk Max Burst Bandwidth |Count |Average |Maximum bytes per second throughput OS Disk can achieve with bursting |LUN |

+|OS Disk Max Burst IOPS |Yes |OS Disk Max Burst IOPS |Count |Average |Maximum IOPS OS Disk can achieve with bursting |LUN |

+|OS Disk Queue Depth |Yes |OS Disk Queue Depth |Count |Average |OS Disk Queue Depth(or Queue Length) |No Dimensions |

+|OS Disk Read Bytes/sec |Yes |OS Disk Read Bytes/Sec |BytesPerSecond |Average |Bytes/Sec read from a single disk during monitoring period for OS disk |No Dimensions |

+|OS Disk Read Operations/Sec |Yes |OS Disk Read Operations/Sec |CountPerSecond |Average |Read IOPS from a single disk during monitoring period for OS disk |No Dimensions |

+|OS Disk Target Bandwidth |Yes |OS Disk Target Bandwidth |Count |Average |Baseline bytes per second throughput OS Disk can achieve without bursting |LUN |

+|OS Disk Target IOPS |Yes |OS Disk Target IOPS |Count |Average |Baseline IOPS OS Disk can achieve without bursting |LUN |

+|OS Disk Used Burst BPS Credits Percentage |Yes |OS Disk Used Burst BPS Credits Percentage |Percent |Average |Percentage of OS Disk burst bandwidth credits used so far |LUN |

+|OS Disk Used Burst IO Credits Percentage |Yes |OS Disk Used Burst IO Credits Percentage |Percent |Average |Percentage of OS Disk burst I/O credits used so far |LUN |

+|OS Disk Write Bytes/sec |Yes |OS Disk Write Bytes/Sec |BytesPerSecond |Average |Bytes/Sec written to a single disk during monitoring period for OS disk |No Dimensions |

+|OS Disk Write Operations/Sec |Yes |OS Disk Write Operations/Sec |CountPerSecond |Average |Write IOPS from a single disk during monitoring period for OS disk |No Dimensions |

+|Outbound Flows |Yes |Outbound Flows |Count |Average |Outbound Flows are number of current flows in the outbound direction (traffic going out of the VM) |No Dimensions |

+|Outbound Flows Maximum Creation Rate |Yes |Outbound Flows Maximum Creation Rate |CountPerSecond |Average |The maximum creation rate of outbound flows (traffic going out of the VM) |No Dimensions |

+|Percentage CPU |Yes |Percentage CPU |Percent |Average |The percentage of allocated compute units that are currently in use by the Virtual Machine(s) |No Dimensions |

+|Premium Data Disk Cache Read Hit |Yes |Premium Data Disk Cache Read Hit |Percent |Average |Premium Data Disk Cache Read Hit |LUN |

+|Premium Data Disk Cache Read Miss |Yes |Premium Data Disk Cache Read Miss |Percent |Average |Premium Data Disk Cache Read Miss |LUN |

+|Premium OS Disk Cache Read Hit |Yes |Premium OS Disk Cache Read Hit |Percent |Average |Premium OS Disk Cache Read Hit |No Dimensions |

+|Premium OS Disk Cache Read Miss |Yes |Premium OS Disk Cache Read Miss |Percent |Average |Premium OS Disk Cache Read Miss |No Dimensions |

+|VM Cached Bandwidth Consumed Percentage |Yes |VM Cached Bandwidth Consumed Percentage |Percent |Average |Percentage of cached disk bandwidth consumed by the VM |No Dimensions |

+|VM Cached IOPS Consumed Percentage |Yes |VM Cached IOPS Consumed Percentage |Percent |Average |Percentage of cached disk IOPS consumed by the VM |No Dimensions |

+|VM Local Used Burst BPS Credits Percentage |Yes |VM Cached Used Burst BPS Credits Percentage |Percent |Average |Percentage of Cached Burst BPS Credits used by the VM. |No Dimensions |

+|VM Local Used Burst IO Credits Percentage |Yes |VM Cached Used Burst IO Credits Percentage |Percent |Average |Percentage of Cached Burst IO Credits used by the VM. |No Dimensions |

+|VM Remote Used Burst BPS Credits Percentage |Yes |VM Uncached Used Burst BPS Credits Percentage |Percent |Average |Percentage of Uncached Burst BPS Credits used by the VM. |No Dimensions |

+|VM Remote Used Burst IO Credits Percentage |Yes |VM Uncached Used Burst IO Credits Percentage |Percent |Average |Percentage of Uncached Burst IO Credits used by the VM. |No Dimensions |

+|VM Uncached Bandwidth Consumed Percentage |Yes |VM Uncached Bandwidth Consumed Percentage |Percent |Average |Percentage of uncached disk bandwidth consumed by the VM |No Dimensions |

+|VM Uncached IOPS Consumed Percentage |Yes |VM Uncached IOPS Consumed Percentage |Percent |Average |Percentage of uncached disk IOPS consumed by the VM |No Dimensions |

+|VmAvailabilityMetric |Yes |VM Availability Metric (Preview) |Count |Average |Measure of Availability of Virtual machines over time. |No Dimensions |

+## Microsoft.Compute/virtualmachineScaleSets

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|Available Memory Bytes |Yes |Available Memory Bytes (Preview) |Bytes |Average |Amount of physical memory, in bytes, immediately available for allocation to a process or for system use in the Virtual Machine |VMName |

+|CPU Credits Consumed |Yes |CPU Credits Consumed |Count |Average |Total number of credits consumed by the Virtual Machine. Only available on B-series burstable VMs |No Dimensions |

+|CPU Credits Remaining |Yes |CPU Credits Remaining |Count |Average |Total number of credits available to burst. Only available on B-series burstable VMs |No Dimensions |

+|Data Disk Bandwidth Consumed Percentage |Yes |Data Disk Bandwidth Consumed Percentage |Percent |Average |Percentage of data disk bandwidth consumed per minute |LUN, VMName |

+|Data Disk IOPS Consumed Percentage |Yes |Data Disk IOPS Consumed Percentage |Percent |Average |Percentage of data disk I/Os consumed per minute |LUN, VMName |

+|Data Disk Max Burst Bandwidth |Yes |Data Disk Max Burst Bandwidth |Count |Average |Maximum bytes per second throughput Data Disk can achieve with bursting |LUN, VMName |

+|Data Disk Max Burst IOPS |Yes |Data Disk Max Burst IOPS |Count |Average |Maximum IOPS Data Disk can achieve with bursting |LUN, VMName |

+|Data Disk Queue Depth |Yes |Data Disk Queue Depth |Count |Average |Data Disk Queue Depth(or Queue Length) |LUN, VMName |

+|Data Disk Read Bytes/sec |Yes |Data Disk Read Bytes/Sec |BytesPerSecond |Average |Bytes/Sec read from a single disk during monitoring period |LUN, VMName |

+|Data Disk Read Operations/Sec |Yes |Data Disk Read Operations/Sec |CountPerSecond |Average |Read IOPS from a single disk during monitoring period |LUN, VMName |

+|Data Disk Target Bandwidth |Yes |Data Disk Target Bandwidth |Count |Average |Baseline bytes per second throughput Data Disk can achieve without bursting |LUN, VMName |

+|Data Disk Target IOPS |Yes |Data Disk Target IOPS |Count |Average |Baseline IOPS Data Disk can achieve without bursting |LUN, VMName |

+|Data Disk Used Burst BPS Credits Percentage |Yes |Data Disk Used Burst BPS Credits Percentage |Percent |Average |Percentage of Data Disk burst bandwidth credits used so far |LUN, VMName |

+|Data Disk Used Burst IO Credits Percentage |Yes |Data Disk Used Burst IO Credits Percentage |Percent |Average |Percentage of Data Disk burst I/O credits used so far |LUN, VMName |

+|Data Disk Write Bytes/sec |Yes |Data Disk Write Bytes/Sec |BytesPerSecond |Average |Bytes/Sec written to a single disk during monitoring period |LUN, VMName |

+|Data Disk Write Operations/Sec |Yes |Data Disk Write Operations/Sec |CountPerSecond |Average |Write IOPS from a single disk during monitoring period |LUN, VMName |

+|Disk Read Bytes |Yes |Disk Read Bytes |Bytes |Total |Bytes read from disk during monitoring period |VMName |

+|Disk Read Operations/Sec |Yes |Disk Read Operations/Sec |CountPerSecond |Average |Disk Read IOPS |VMName |

+|Disk Write Bytes |Yes |Disk Write Bytes |Bytes |Total |Bytes written to disk during monitoring period |VMName |

+|Disk Write Operations/Sec |Yes |Disk Write Operations/Sec |CountPerSecond |Average |Disk Write IOPS |VMName |

+|Inbound Flows |Yes |Inbound Flows |Count |Average |Inbound Flows are number of current flows in the inbound direction (traffic going into the VM) |VMName |

+|Inbound Flows Maximum Creation Rate |Yes |Inbound Flows Maximum Creation Rate |CountPerSecond |Average |The maximum creation rate of inbound flows (traffic going into the VM) |VMName |

+|Network In |Yes |Network In Billable (Deprecated) |Bytes |Total |The number of billable bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic) (Deprecated) |VMName |

+|Network In Total |Yes |Network In Total |Bytes |Total |The number of bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic) |VMName |

+|Network Out |Yes |Network Out Billable (Deprecated) |Bytes |Total |The number of billable bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic) (Deprecated) |VMName |

+|Network Out Total |Yes |Network Out Total |Bytes |Total |The number of bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic) |VMName |

+|OS Disk Bandwidth Consumed Percentage |Yes |OS Disk Bandwidth Consumed Percentage |Percent |Average |Percentage of operating system disk bandwidth consumed per minute |LUN, VMName |

+|OS Disk IOPS Consumed Percentage |Yes |OS Disk IOPS Consumed Percentage |Percent |Average |Percentage of operating system disk I/Os consumed per minute |LUN, VMName |

+|OS Disk Max Burst Bandwidth |Yes |OS Disk Max Burst Bandwidth |Count |Average |Maximum bytes per second throughput OS Disk can achieve with bursting |LUN, VMName |

+|OS Disk Max Burst IOPS |Yes |OS Disk Max Burst IOPS |Count |Average |Maximum IOPS OS Disk can achieve with bursting |LUN, VMName |

+|OS Disk Queue Depth |Yes |OS Disk Queue Depth |Count |Average |OS Disk Queue Depth(or Queue Length) |VMName |

+|OS Disk Read Bytes/sec |Yes |OS Disk Read Bytes/Sec |BytesPerSecond |Average |Bytes/Sec read from a single disk during monitoring period for OS disk |VMName |

+|OS Disk Read Operations/Sec |Yes |OS Disk Read Operations/Sec |CountPerSecond |Average |Read IOPS from a single disk during monitoring period for OS disk |VMName |

+|OS Disk Target Bandwidth |Yes |OS Disk Target Bandwidth |Count |Average |Baseline bytes per second throughput OS Disk can achieve without bursting |LUN, VMName |

+|OS Disk Target IOPS |Yes |OS Disk Target IOPS |Count |Average |Baseline IOPS OS Disk can achieve without bursting |LUN, VMName |

+|OS Disk Used Burst BPS Credits Percentage |Yes |OS Disk Used Burst BPS Credits Percentage |Percent |Average |Percentage of OS Disk burst bandwidth credits used so far |LUN, VMName |

+|OS Disk Used Burst IO Credits Percentage |Yes |OS Disk Used Burst IO Credits Percentage |Percent |Average |Percentage of OS Disk burst I/O credits used so far |LUN, VMName |

+|OS Disk Write Bytes/sec |Yes |OS Disk Write Bytes/Sec |BytesPerSecond |Average |Bytes/Sec written to a single disk during monitoring period for OS disk |VMName |

+|OS Disk Write Operations/Sec |Yes |OS Disk Write Operations/Sec |CountPerSecond |Average |Write IOPS from a single disk during monitoring period for OS disk |VMName |

+|Outbound Flows |Yes |Outbound Flows |Count |Average |Outbound Flows are number of current flows in the outbound direction (traffic going out of the VM) |VMName |

+|Outbound Flows Maximum Creation Rate |Yes |Outbound Flows Maximum Creation Rate |CountPerSecond |Average |The maximum creation rate of outbound flows (traffic going out of the VM) |VMName |

+|Percentage CPU |Yes |Percentage CPU |Percent |Average |The percentage of allocated compute units that are currently in use by the Virtual Machine(s) |VMName |

+|Premium Data Disk Cache Read Hit |Yes |Premium Data Disk Cache Read Hit |Percent |Average |Premium Data Disk Cache Read Hit |LUN, VMName |

+|Premium Data Disk Cache Read Miss |Yes |Premium Data Disk Cache Read Miss |Percent |Average |Premium Data Disk Cache Read Miss |LUN, VMName |

+|Premium OS Disk Cache Read Hit |Yes |Premium OS Disk Cache Read Hit |Percent |Average |Premium OS Disk Cache Read Hit |VMName |

+|Premium OS Disk Cache Read Miss |Yes |Premium OS Disk Cache Read Miss |Percent |Average |Premium OS Disk Cache Read Miss |VMName |

+|VM Cached Bandwidth Consumed Percentage |Yes |VM Cached Bandwidth Consumed Percentage |Percent |Average |Percentage of cached disk bandwidth consumed by the VM |VMName |

+|VM Cached IOPS Consumed Percentage |Yes |VM Cached IOPS Consumed Percentage |Percent |Average |Percentage of cached disk IOPS consumed by the VM |VMName |

+|VM Local Used Burst BPS Credits Percentage |Yes |VM Cached Used Burst BPS Credits Percentage |Percent |Average |Percentage of Cached Burst BPS Credits used by the VM. |VMName |

+|VM Local Used Burst IO Credits Percentage |Yes |VM Cached Used Burst IO Credits Percentage |Percent |Average |Percentage of Cached Burst IO Credits used by the VM. |VMName |

+|VM Remote Used Burst BPS Credits Percentage |Yes |VM Uncached Used Burst BPS Credits Percentage |Percent |Average |Percentage of Uncached Burst BPS Credits used by the VM. |VMName |

+|VM Remote Used Burst IO Credits Percentage |Yes |VM Uncached Used Burst IO Credits Percentage |Percent |Average |Percentage of Uncached Burst IO Credits used by the VM. |VMName |

+|VM Uncached Bandwidth Consumed Percentage |Yes |VM Uncached Bandwidth Consumed Percentage |Percent |Average |Percentage of uncached disk bandwidth consumed by the VM |VMName |

+|VM Uncached IOPS Consumed Percentage |Yes |VM Uncached IOPS Consumed Percentage |Percent |Average |Percentage of uncached disk IOPS consumed by the VM |VMName |

+|VmAvailabilityMetric |Yes |VM Availability Metric (Preview) |Count |Average |Measure of Availability of Virtual machines over time. |VMName |

+## Microsoft.Compute/virtualMachineScaleSets/virtualMachines

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|Available Memory Bytes |Yes |Available Memory Bytes (Preview) |Bytes |Average |Amount of physical memory, in bytes, immediately available for allocation to a process or for system use in the Virtual Machine |No Dimensions |

+|CPU Credits Consumed |Yes |CPU Credits Consumed |Count |Average |Total number of credits consumed by the Virtual Machine. Only available on B-series burstable VMs |No Dimensions |

+|CPU Credits Remaining |Yes |CPU Credits Remaining |Count |Average |Total number of credits available to burst. Only available on B-series burstable VMs |No Dimensions |

+|Data Disk Bandwidth Consumed Percentage |Yes |Data Disk Bandwidth Consumed Percentage |Percent |Average |Percentage of data disk bandwidth consumed per minute |LUN |

+|Data Disk IOPS Consumed Percentage |Yes |Data Disk IOPS Consumed Percentage |Percent |Average |Percentage of data disk I/Os consumed per minute |LUN |

+|Data Disk Max Burst Bandwidth |Yes |Data Disk Max Burst Bandwidth |Count |Average |Maximum bytes per second throughput Data Disk can achieve with bursting |LUN |

+|Data Disk Max Burst IOPS |Yes |Data Disk Max Burst IOPS |Count |Average |Maximum IOPS Data Disk can achieve with bursting |LUN |

+|Data Disk Queue Depth |Yes |Data Disk Queue Depth |Count |Average |Data Disk Queue Depth(or Queue Length) |LUN |

+|Data Disk Read Bytes/sec |Yes |Data Disk Read Bytes/Sec |BytesPerSecond |Average |Bytes/Sec read from a single disk during monitoring period |LUN |

+|Data Disk Read Operations/Sec |Yes |Data Disk Read Operations/Sec |CountPerSecond |Average |Read IOPS from a single disk during monitoring period |LUN |

+|Data Disk Target Bandwidth |Yes |Data Disk Target Bandwidth |Count |Average |Baseline bytes per second throughput Data Disk can achieve without bursting |LUN |

+|Data Disk Target IOPS |Yes |Data Disk Target IOPS |Count |Average |Baseline IOPS Data Disk can achieve without bursting |LUN |

+|Data Disk Used Burst BPS Credits Percentage |Yes |Data Disk Used Burst BPS Credits Percentage |Percent |Average |Percentage of Data Disk burst bandwidth credits used so far |LUN |

+|Data Disk Used Burst IO Credits Percentage |Yes |Data Disk Used Burst IO Credits Percentage |Percent |Average |Percentage of Data Disk burst I/O credits used so far |LUN |

+|Data Disk Write Bytes/sec |Yes |Data Disk Write Bytes/Sec |BytesPerSecond |Average |Bytes/Sec written to a single disk during monitoring period |LUN |

+|Data Disk Write Operations/Sec |Yes |Data Disk Write Operations/Sec |CountPerSecond |Average |Write IOPS from a single disk during monitoring period |LUN |

+|Disk Read Bytes |Yes |Disk Read Bytes |Bytes |Total |Bytes read from disk during monitoring period |No Dimensions |

+|Disk Read Operations/Sec |Yes |Disk Read Operations/Sec |CountPerSecond |Average |Disk Read IOPS |No Dimensions |

+|Disk Write Bytes |Yes |Disk Write Bytes |Bytes |Total |Bytes written to disk during monitoring period |No Dimensions |

+|Disk Write Operations/Sec |Yes |Disk Write Operations/Sec |CountPerSecond |Average |Disk Write IOPS |No Dimensions |

+|Inbound Flows |Yes |Inbound Flows |Count |Average |Inbound Flows are number of current flows in the inbound direction (traffic going into the VM) |No Dimensions |

+|Inbound Flows Maximum Creation Rate |Yes |Inbound Flows Maximum Creation Rate |CountPerSecond |Average |The maximum creation rate of inbound flows (traffic going into the VM) |No Dimensions |

+|Network In |Yes |Network In Billable (Deprecated) |Bytes |Total |The number of billable bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic) (Deprecated) |No Dimensions |

+|Network In Total |Yes |Network In Total |Bytes |Total |The number of bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic) |No Dimensions |

+|Network Out |Yes |Network Out Billable (Deprecated) |Bytes |Total |The number of billable bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic) (Deprecated) |No Dimensions |

+|Network Out Total |Yes |Network Out Total |Bytes |Total |The number of bytes out on all network interfaces by the Virtual Machine(s) (Outgoing Traffic) |No Dimensions |

+|OS Disk Bandwidth Consumed Percentage |Yes |OS Disk Bandwidth Consumed Percentage |Percent |Average |Percentage of operating system disk bandwidth consumed per minute |LUN |

+|OS Disk IOPS Consumed Percentage |Yes |OS Disk IOPS Consumed Percentage |Percent |Average |Percentage of operating system disk I/Os consumed per minute |LUN |

+|OS Disk Max Burst Bandwidth |Yes |OS Disk Max Burst Bandwidth |Count |Average |Maximum bytes per second throughput OS Disk can achieve with bursting |LUN |

+|OS Disk Max Burst IOPS |Yes |OS Disk Max Burst IOPS |Count |Average |Maximum IOPS OS Disk can achieve with bursting |LUN |

+|OS Disk Queue Depth |Yes |OS Disk Queue Depth |Count |Average |OS Disk Queue Depth(or Queue Length) |No Dimensions |

+|OS Disk Read Bytes/sec |Yes |OS Disk Read Bytes/Sec |BytesPerSecond |Average |Bytes/Sec read from a single disk during monitoring period for OS disk |No Dimensions |

+|OS Disk Read Operations/Sec |Yes |OS Disk Read Operations/Sec |CountPerSecond |Average |Read IOPS from a single disk during monitoring period for OS disk |No Dimensions |

+|OS Disk Target Bandwidth |Yes |OS Disk Target Bandwidth |Count |Average |Baseline bytes per second throughput OS Disk can achieve without bursting |LUN |

+|OS Disk Target IOPS |Yes |OS Disk Target IOPS |Count |Average |Baseline IOPS OS Disk can achieve without bursting |LUN |

+|OS Disk Used Burst BPS Credits Percentage |Yes |OS Disk Used Burst BPS Credits Percentage |Percent |Average |Percentage of OS Disk burst bandwidth credits used so far |LUN |

+|OS Disk Used Burst IO Credits Percentage |Yes |OS Disk Used Burst IO Credits Percentage |Percent |Average |Percentage of OS Disk burst I/O credits used so far |LUN |

+|OS Disk Write Bytes/sec |Yes |OS Disk Write Bytes/Sec |BytesPerSecond |Average |Bytes/Sec written to a single disk during monitoring period for OS disk |No Dimensions |

+|OS Disk Write Operations/Sec |Yes |OS Disk Write Operations/Sec |CountPerSecond |Average |Write IOPS from a single disk during monitoring period for OS disk |No Dimensions |

+|Outbound Flows |Yes |Outbound Flows |Count |Average |Outbound Flows are number of current flows in the outbound direction (traffic going out of the VM) |No Dimensions |

+|Outbound Flows Maximum Creation Rate |Yes |Outbound Flows Maximum Creation Rate |CountPerSecond |Average |The maximum creation rate of outbound flows (traffic going out of the VM) |No Dimensions |

+|Percentage CPU |Yes |Percentage CPU |Percent |Average |The percentage of allocated compute units that are currently in use by the Virtual Machine(s) |No Dimensions |

+|Premium Data Disk Cache Read Hit |Yes |Premium Data Disk Cache Read Hit |Percent |Average |Premium Data Disk Cache Read Hit |LUN |

+|Premium Data Disk Cache Read Miss |Yes |Premium Data Disk Cache Read Miss |Percent |Average |Premium Data Disk Cache Read Miss |LUN |

+|Premium OS Disk Cache Read Hit |Yes |Premium OS Disk Cache Read Hit |Percent |Average |Premium OS Disk Cache Read Hit |No Dimensions |

+|Premium OS Disk Cache Read Miss |Yes |Premium OS Disk Cache Read Miss |Percent |Average |Premium OS Disk Cache Read Miss |No Dimensions |

+|VM Cached Bandwidth Consumed Percentage |Yes |VM Cached Bandwidth Consumed Percentage |Percent |Average |Percentage of cached disk bandwidth consumed by the VM |No Dimensions |

+|VM Cached IOPS Consumed Percentage |Yes |VM Cached IOPS Consumed Percentage |Percent |Average |Percentage of cached disk IOPS consumed by the VM |No Dimensions |

+|VM Uncached Bandwidth Consumed Percentage |Yes |VM Uncached Bandwidth Consumed Percentage |Percent |Average |Percentage of uncached disk bandwidth consumed by the VM |No Dimensions |

+|VM Uncached IOPS Consumed Percentage |Yes |VM Uncached IOPS Consumed Percentage |Percent |Average |Percentage of uncached disk IOPS consumed by the VM |No Dimensions |

+## Microsoft.ConnectedCache/CacheNodes

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|egressbps |Yes |Egress Mbps |BitsPerSecond |Average |Egress Throughput |cachenodeid |

+|hitRatio |Yes |Cache Efficiency |Percent |Average |Cache Efficiency |cachenodeid |

+|hits |Yes |Hits |Count |Count |Count of hits |cachenodeid |

+|hitsbps |Yes |Hit Mbps |BitsPerSecond |Average |Hit Throughput |cachenodeid |

+|misses |Yes |Misses |Count |Count |Count of misses |cachenodeid |

+|missesbps |Yes |Miss Mbps |BitsPerSecond |Average |Miss Throughput |cachenodeid |

+## Microsoft.ConnectedCache/ispCustomers

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|egressbps |Yes |Egress Mbps |BitsPerSecond |Average |Egress Throughput |cachenodeid |

+|hitRatio |Yes |Hit Ratio |Percent |Average |Cache hit ratio is a measurement of how many content requests a cache is able to fill successfully, compared to how many requests it receives. |cachenodeid |

+|hits |Yes |Hits |Count |Count |Count of hits |cachenodeid |

+|hitsbps |Yes |Hit Mbps |BitsPerSecond |Average |Hit Throughput |cachenodeid |

+|inboundbps |Yes |Inbound |BitsPerSecond |Average |Inbound Throughput |cachenodeid |

+|misses |Yes |Misses |Count |Count |Count of misses |cachenodeid |

+|missesbps |Yes |Miss Mbps |BitsPerSecond |Average |Miss Throughput |cachenodeid |

+|outboundbps |Yes |Outbound |BitsPerSecond |Average |Outbound Throughput |cachenodeid |

+## Microsoft.ConnectedVehicle/platformAccounts

+<!-- Data source : naam-->

+|ClaimsProviderRequestLatency |Yes |Claims request execution time |Milliseconds |Average |The average execution time of requests to the customer claims provider endpoint in milliseconds. |IsSuccessful, FailureCategory |

+|ClaimsProviderRequests |Yes |Claims provider requests |Count |Total |Number of requests to claims provider |IsSuccessful, FailureCategory |

+|ConnectionServiceRequestRuntime |Yes |Vehicle connection service request execution time |Milliseconds |Average |Vehicle connection request execution time average in milliseconds |IsSuccessful, FailureCategory |

+|ConnectionServiceRequests |Yes |Vehicle connection service requests |Count |Total |Total number of vehicle connection requests |IsSuccessful, FailureCategory |

+|DataPipelineMessageCount |Yes |Data pipeline message count |Count |Total |The total number of messages sent to the MCVP data pipeline for storage. |IsSuccessful, FailureCategory |

+|ExtensionInvocationCount |Yes |Extension invocation count |Count |Total |Total number of times an extension was called. |ExtensionName, IsSuccessful, FailureCategory |

+|ExtensionInvocationRuntime |Yes |Extension invocation execution time |Milliseconds |Average |Average execution time spent inside an extension in milliseconds. |ExtensionName, IsSuccessful, FailureCategory |

+|MessagesInCount |Yes |Messages received count |Count |Total |The total number of vehicle-sourced publishes. |IsSuccessful, FailureCategory |

+|MessagesOutCount |Yes |Messages sent count |Count |Total |The total number of cloud-sourced publishes. |IsSuccessful, FailureCategory |

+|ProvisionerServiceRequestRuntime |Yes |Vehicle provision execution time |Milliseconds |Average |The average execution time of vehicle provision requests in milliseconds |IsSuccessful, FailureCategory |

+|ProvisionerServiceRequests |Yes |Vehicle provision service requests |Count |Total |Total number of vehicle provision requests |IsSuccessful, FailureCategory |

+|StateStoreReadRequestLatency |Yes |State store read execution time |Milliseconds |Average |State store read request execution time average in milliseconds. |ExtensionName, IsSuccessful, FailureCategory |

+|StateStoreReadRequests |Yes |State store read requests |Count |Total |Number of read requests to state store |ExtensionName, IsSuccessful, FailureCategory |

+|StateStoreWriteRequestLatency |Yes |State store write execution time |Milliseconds |Average |State store write request execution time average in milliseconds. |ExtensionName, IsSuccessful, FailureCategory |

+|StateStoreWriteRequests |Yes |State store write requests |Count |Total |Number of write requests to state store |ExtensionName, IsSuccessful, FailureCategory |

+## Microsoft.ContainerInstance/containerGroups

+<!-- Data source : arm-->

+|CpuUsage |Yes |CPU Usage |Count |Average |CPU usage on all cores in millicores. |containerName |

+|MemoryUsage |Yes |Memory Usage |Bytes |Average |Total memory usage in byte. |containerName |

+|NetworkBytesReceivedPerSecond |Yes |Network Bytes Received Per Second |Bytes |Average |The network bytes received per second. |No Dimensions |

+|NetworkBytesTransmittedPerSecond |Yes |Network Bytes Transmitted Per Second |Bytes |Average |The network bytes transmitted per second. |No Dimensions |

+## Microsoft.ContainerRegistry/registries

+<!-- Data source : naam-->

+|AgentPoolCPUTime |Yes |AgentPool CPU Time |Seconds |Total |AgentPool CPU Time in seconds |No Dimensions |

+|RunDuration |Yes |Run Duration |MilliSeconds |Total |Run Duration in milliseconds |No Dimensions |

+|StorageUsed |Yes |Storage used |Bytes |Average |The amount of storage used by the container registry. For a registry account, it's the sum of capacity used by all the repositories within a registry. It's sum of capacity used by shared layers, manifest files, and replica copies in each of its repositories. |Geolocation |

+|SuccessfulPullCount |Yes |Successful Pull Count |Count |Total |Number of successful image pulls |No Dimensions |

+|SuccessfulPushCount |Yes |Successful Push Count |Count |Total |Number of successful image pushes |No Dimensions |

+|TotalPullCount |Yes |Total Pull Count |Count |Total |Number of image pulls in total |No Dimensions |

+|TotalPushCount |Yes |Total Push Count |Count |Total |Number of image pushes in total |No Dimensions |

+## Microsoft.ContainerService/managedClusters

+<!-- Data source : naam-->

+|apiserver_current_inflight_requests |No |Inflight Requests |Count |Average |Maximum number of currently used inflight requests on the apiserver per request kind in the last second |requestKind |

+|cluster_autoscaler_cluster_safe_to_autoscale |No |Cluster Health |Count |Average |Determines whether or not cluster autoscaler will take action on the cluster |No Dimensions |

+|cluster_autoscaler_scale_down_in_cooldown |No |Scale Down Cooldown |Count |Average |Determines if the scale down is in cooldown - No nodes will be removed during this timeframe |No Dimensions |

+|cluster_autoscaler_unneeded_nodes_count |No |Unneeded Nodes |Count |Average |Cluster auotscaler marks those nodes as candidates for deletion and are eventually deleted |No Dimensions |

+|cluster_autoscaler_unschedulable_pods_count |No |Unschedulable Pods |Count |Average |Number of pods that are currently unschedulable in the cluster |No Dimensions |

+|kube_node_status_allocatable_cpu_cores |No |Total number of available cpu cores in a managed cluster |Count |Average |Total number of available cpu cores in a managed cluster |No Dimensions |

+|kube_node_status_allocatable_memory_bytes |No |Total amount of available memory in a managed cluster |Bytes |Average |Total amount of available memory in a managed cluster |No Dimensions |

+|kube_node_status_condition |No |Statuses for various node conditions |Count |Average |Statuses for various node conditions |condition, status, status2, node |

+|kube_pod_status_phase |No |Number of pods by phase |Count |Average |Number of pods by phase |phase, namespace, pod |

+|kube_pod_status_ready |No |Number of pods in Ready state |Count |Average |Number of pods in Ready state |namespace, pod, condition |

+|node_cpu_usage_millicores |Yes |CPU Usage Millicores |MilliCores |Average |Aggregated measurement of CPU utilization in millicores across the cluster |node, nodepool |

+|node_cpu_usage_percentage |Yes |CPU Usage Percentage |Percent |Average |Aggregated average CPU utilization measured in percentage across the cluster |node, nodepool |

+|node_disk_usage_bytes |Yes |Disk Used Bytes |Bytes |Average |Disk space used in bytes by device |node, nodepool, device |

+|node_disk_usage_percentage |Yes |Disk Used Percentage |Percent |Average |Disk space used in percent by device |node, nodepool, device |

+|node_memory_rss_bytes |Yes |Memory RSS Bytes |Bytes |Average |Container RSS memory used in bytes |node, nodepool |

+|node_memory_rss_percentage |Yes |Memory RSS Percentage |Percent |Average |Container RSS memory used in percent |node, nodepool |

+|node_memory_working_set_bytes |Yes |Memory Working Set Bytes |Bytes |Average |Container working set memory used in bytes |node, nodepool |

+|node_memory_working_set_percentage |Yes |Memory Working Set Percentage |Percent |Average |Container working set memory used in percent |node, nodepool |

+|node_network_in_bytes |Yes |Network In Bytes |Bytes |Average |Network received bytes |node, nodepool |

+|node_network_out_bytes |Yes |Network Out Bytes |Bytes |Average |Network transmitted bytes |node, nodepool |

+## Microsoft.CustomProviders/resourceproviders

+<!-- Data source : arm-->

+|FailedRequests |Yes |Failed Requests |Count |Total |Gets the available logs for Custom Resource Providers |HttpMethod, CallPath, StatusCode |

+|SuccessfullRequests |Yes |Successful Requests |Count |Total |Successful requests made by the custom provider |HttpMethod, CallPath, StatusCode |

+## Microsoft.Dashboard/grafana

+<!-- Data source : naam-->

+|HttpRequestCount |No |HttpRequestCount |Count |Count |Number of HTTP requests to Azure Managed Grafana server |No Dimensions |

+## Microsoft.DataBoxEdge/dataBoxEdgeDevices

+<!-- Data source : arm-->

+|AvailableCapacity |Yes |Available Capacity |Bytes |Average |The available capacity in bytes during the reporting period. |No Dimensions |

+|BytesUploadedToCloud |Yes |Cloud Bytes Uploaded (Device) |Bytes |Average |The total number of bytes that is uploaded to Azure from a device during the reporting period. |No Dimensions |

+|BytesUploadedToCloudPerShare |Yes |Cloud Bytes Uploaded (Share) |Bytes |Average |The total number of bytes that is uploaded to Azure from a share during the reporting period. |Share |

+|CloudReadThroughput |Yes |Cloud Download Throughput |BytesPerSecond |Average |The cloud download throughput to Azure during the reporting period. |No Dimensions |

+|CloudReadThroughputPerShare |Yes |Cloud Download Throughput (Share) |BytesPerSecond |Average |The download throughput to Azure from a share during the reporting period. |Share |

+|CloudUploadThroughput |Yes |Cloud Upload Throughput |BytesPerSecond |Average |The cloud upload throughput to Azure during the reporting period. |No Dimensions |

+|CloudUploadThroughputPerShare |Yes |Cloud Upload Throughput (Share) |BytesPerSecond |Average |The upload throughput to Azure from a share during the reporting period. |Share |

+|HyperVMemoryUtilization |Yes |Edge Compute - Memory Usage |Percent |Average |Amount of RAM in Use |InstanceName |

+|HyperVVirtualProcessorUtilization |Yes |Edge Compute - Percentage CPU |Percent |Average |Percent CPU Usage |InstanceName |

+|NICReadThroughput |Yes |Read Throughput (Network) |BytesPerSecond |Average |The read throughput of the network interface on the device in the reporting period for all volumes in the gateway. |InstanceName |

+|NICWriteThroughput |Yes |Write Throughput (Network) |BytesPerSecond |Average |The write throughput of the network interface on the device in the reporting period for all volumes in the gateway. |InstanceName |

+|TotalCapacity |Yes |Total Capacity |Bytes |Average |The total capacity of the device in bytes during the reporting period. |No Dimensions |

+## Microsoft.DataCollaboration/workspaces

+<!-- Data source : arm-->

+|ComputationCount |Yes |Created Computations |Count |Maximum |Number of created computations |ComputationName |

+|DataAssetCount |Yes |Created Data Assets |Count |Maximum |Number of created data assets |DataAssetName |

+|PipelineCount |Yes |Created Pipelines |Count |Maximum |Number of created pipelines |PipelineName |

+|PipelineCount |Yes |Created Pipelines |Count |Maximum |Number of created pipelines |PipelineName |

+|ProposalCount |Yes |Created Proposals |Count |Maximum |Number of created proposals |ProposalName |

+|ScriptCount |Yes |Created Scripts |Count |Maximum |Number of created scripts |ScriptName |

+## Microsoft.DataFactory/datafactories

+<!-- Data source : arm-->

+|FailedRuns |Yes |Failed Runs |Count |Total |Failed Runs |pipelineName, activityName |

+|SuccessfulRuns |Yes |Successful Runs |Count |Total |Successful Runs |pipelineName, activityName |

+## Microsoft.DataFactory/factories

+<!-- Data source : arm-->

+|ActivityCancelledRuns |Yes |Cancelled activity runs metrics |Count |Total |Cancelled activity runs metrics |ActivityType, PipelineName, FailureType, Name |

+|ActivityFailedRuns |Yes |Failed activity runs metrics |Count |Total |Failed activity runs metrics |ActivityType, PipelineName, FailureType, Name |

+|ActivitySucceededRuns |Yes |Succeeded activity runs metrics |Count |Total |Succeeded activity runs metrics |ActivityType, PipelineName, FailureType, Name |

+|FactorySizeInGbUnits |Yes |Total factory size (GB unit) |Count |Maximum |Total factory size (GB unit) |No Dimensions |

+|IntegrationRuntimeAvailableMemory |Yes |Integration runtime available memory |Bytes |Average |Integration runtime available memory |IntegrationRuntimeName, NodeName |

+|IntegrationRuntimeAvailableNodeNumber |Yes |Integration runtime available node count |Count |Average |Integration runtime available node count |IntegrationRuntimeName |

+|IntegrationRuntimeAverageTaskPickupDelay |Yes |Integration runtime queue duration |Seconds |Average |Integration runtime queue duration |IntegrationRuntimeName |

+|IntegrationRuntimeCpuPercentage |Yes |Integration runtime CPU utilization |Percent |Average |Integration runtime CPU utilization |IntegrationRuntimeName, NodeName |

+|IntegrationRuntimeQueueLength |Yes |Integration runtime queue length |Count |Average |Integration runtime queue length |IntegrationRuntimeName |

+|MaxAllowedFactorySizeInGbUnits |Yes |Maximum allowed factory size (GB unit) |Count |Maximum |Maximum allowed factory size (GB unit) |No Dimensions |

+|MaxAllowedResourceCount |Yes |Maximum allowed entities count |Count |Maximum |Maximum allowed entities count |No Dimensions |

+|PipelineCancelledRuns |Yes |Cancelled pipeline runs metrics |Count |Total |Cancelled pipeline runs metrics |FailureType, CancelledBy, Name |

+|PipelineElapsedTimeRuns |Yes |Elapsed Time Pipeline Runs Metrics |Count |Total |Elapsed Time Pipeline Runs Metrics |RunId, Name |

+|PipelineFailedRuns |Yes |Failed pipeline runs metrics |Count |Total |Failed pipeline runs metrics |FailureType, Name |

+|PipelineSucceededRuns |Yes |Succeeded pipeline runs metrics |Count |Total |Succeeded pipeline runs metrics |FailureType, Name |

+|ResourceCount |Yes |Total entities count |Count |Maximum |Total entities count |No Dimensions |

+|SSISIntegrationRuntimeStartCancel |Yes |Cancelled SSIS integration runtime start metrics |Count |Total |Cancelled SSIS integration runtime start metrics |IntegrationRuntimeName |

+|SSISIntegrationRuntimeStartFailed |Yes |Failed SSIS integration runtime start metrics |Count |Total |Failed SSIS integration runtime start metrics |IntegrationRuntimeName |

+|SSISIntegrationRuntimeStartSucceeded |Yes |Succeeded SSIS integration runtime start metrics |Count |Total |Succeeded SSIS integration runtime start metrics |IntegrationRuntimeName |

+|SSISIntegrationRuntimeStopStuck |Yes |Stuck SSIS integration runtime stop metrics |Count |Total |Stuck SSIS integration runtime stop metrics |IntegrationRuntimeName |

+|SSISIntegrationRuntimeStopSucceeded |Yes |Succeeded SSIS integration runtime stop metrics |Count |Total |Succeeded SSIS integration runtime stop metrics |IntegrationRuntimeName |

+|SSISPackageExecutionCancel |Yes |Cancelled SSIS package execution metrics |Count |Total |Cancelled SSIS package execution metrics |IntegrationRuntimeName |

+|SSISPackageExecutionFailed |Yes |Failed SSIS package execution metrics |Count |Total |Failed SSIS package execution metrics |IntegrationRuntimeName |

+|SSISPackageExecutionSucceeded |Yes |Succeeded SSIS package execution metrics |Count |Total |Succeeded SSIS package execution metrics |IntegrationRuntimeName |

+|TriggerCancelledRuns |Yes |Cancelled trigger runs metrics |Count |Total |Cancelled trigger runs metrics |Name, FailureType |

+|TriggerFailedRuns |Yes |Failed trigger runs metrics |Count |Total |Failed trigger runs metrics |Name, FailureType |

+|TriggerSucceededRuns |Yes |Succeeded trigger runs metrics |Count |Total |Succeeded trigger runs metrics |Name, FailureType |

+## Microsoft.DataLakeAnalytics/accounts

+<!-- Data source : naam-->

+|JobAUEndedCancelled |Yes |Cancelled AU Time |Seconds |Total |Total AU time for cancelled jobs. |No Dimensions |

+|JobAUEndedFailure |Yes |Failed AU Time |Seconds |Total |Total AU time for failed jobs. |No Dimensions |

+|JobAUEndedSuccess |Yes |Successful AU Time |Seconds |Total |Total AU time for successful jobs. |No Dimensions |

+|JobEndedCancelled |Yes |Cancelled Jobs |Count |Total |Count of cancelled jobs. |No Dimensions |

+|JobEndedFailure |Yes |Failed Jobs |Count |Total |Count of failed jobs. |No Dimensions |

+|JobEndedSuccess |Yes |Successful Jobs |Count |Total |Count of successful jobs. |No Dimensions |

+|JobStage |Yes |Jobs in Stage |Count |Total |Number of jobs in each stage. |No Dimensions |

+## Microsoft.DataLakeStore/accounts

+<!-- Data source : arm-->

+|DataRead |Yes |Data Read |Bytes |Total |Total amount of data read from the account. |No Dimensions |

+|DataWritten |Yes |Data Written |Bytes |Total |Total amount of data written to the account. |No Dimensions |

+|ReadRequests |Yes |Read Requests |Count |Total |Count of data read requests to the account. |No Dimensions |

+|TotalStorage |Yes |Total Storage |Bytes |Maximum |Total amount of data stored in the account. |No Dimensions |

+|WriteRequests |Yes |Write Requests |Count |Total |Count of data write requests to the account. |No Dimensions |

+## Microsoft.DataProtection/BackupVaults

+<!-- Data source : naam-->

+|BackupHealthEvent |Yes |Backup Health Events (preview) |Count |Count |The count of health events pertaining to backup job health |dataSourceURL, backupInstanceUrl, dataSourceType, healthStatus, backupInstanceName |

+|RestoreHealthEvent |Yes |Restore Health Events (preview) |Count |Count |The count of health events pertaining to restore job health |dataSourceURL, backupInstanceUrl, dataSourceType, healthStatus, backupInstanceName |

+## Microsoft.DataShare/accounts

+<!-- Data source : arm-->

+|FailedShareSubscriptionSynchronizations |Yes |Received Share Failed Snapshots |Count |Count |Number of received share failed snapshots in the account |No Dimensions |

+|FailedShareSynchronizations |Yes |Sent Share Failed Snapshots |Count |Count |Number of sent share failed snapshots in the account |No Dimensions |

+|ShareCount |Yes |Sent Shares |Count |Maximum |Number of sent shares in the account |ShareName |

+|ShareSubscriptionCount |Yes |Received Shares |Count |Maximum |Number of received shares in the account |ShareSubscriptionName |

+|SucceededShareSubscriptionSynchronizations |Yes |Received Share Succeeded Snapshots |Count |Count |Number of received share succeeded snapshots in the account |No Dimensions |

+|SucceededShareSynchronizations |Yes |Sent Share Succeeded Snapshots |Count |Count |Number of sent share succeeded snapshots in the account |No Dimensions |

+## Microsoft.DBforMariaDB/servers

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|active_connections |Yes |Active Connections |Count |Average |Active Connections |No Dimensions |

+|backup_storage_used |Yes |Backup Storage used |Bytes |Average |Backup Storage used |No Dimensions |

+|connections_failed |Yes |Failed Connections |Count |Total |Failed Connections |No Dimensions |

+|cpu_percent |Yes |CPU percent |Percent |Average |CPU percent |No Dimensions |

+|io_consumption_percent |Yes |IO percent |Percent |Average |IO percent |No Dimensions |

+|memory_percent |Yes |Memory percent |Percent |Average |Memory percent |No Dimensions |

+|network_bytes_egress |Yes |Network Out |Bytes |Total |Network Out across active connections |No Dimensions |

+|network_bytes_ingress |Yes |Network In |Bytes |Total |Network In across active connections |No Dimensions |

+|seconds_behind_master |Yes |Replication lag in seconds |Count |Maximum |Replication lag in seconds |No Dimensions |

+|serverlog_storage_limit |Yes |Server Log storage limit |Bytes |Maximum |Server Log storage limit |No Dimensions |

+|serverlog_storage_percent |Yes |Server Log storage percent |Percent |Average |Server Log storage percent |No Dimensions |

+|serverlog_storage_usage |Yes |Server Log storage used |Bytes |Average |Server Log storage used |No Dimensions |

+|storage_limit |Yes |Storage limit |Bytes |Maximum |Storage limit |No Dimensions |

+|storage_percent |Yes |Storage percent |Percent |Average |Storage percent |No Dimensions |

+|storage_used |Yes |Storage used |Bytes |Average |Storage used |No Dimensions |

+## Microsoft.DBforMySQL/flexibleServers

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|aborted_connections |Yes |Aborted Connections |Count |Total |Aborted Connections |No Dimensions |

+|active_connections |Yes |Active Connections |Count |Maximum |Active Connections |No Dimensions |

+|backup_storage_used |Yes |Backup Storage Used |Bytes |Maximum |Backup Storage Used |No Dimensions |

+|Com_alter_table |Yes |Com Alter Table |Count |Total |The number of times ALTER TABLE statement has been executed. |No Dimensions |

+|Com_create_db |Yes |Com Create DB |Count |Total |The number of times CREATE DB statement has been executed. |No Dimensions |

+|Com_create_table |Yes |Com Create Table |Count |Total |The number of times CREATE TABLE statement has been executed. |No Dimensions |

+|Com_delete |Yes |Com Delete |Count |Total |The number of times DELETE statement has been executed. |No Dimensions |

+|Com_drop_db |Yes |Com Drop DB |Count |Total |The number of times DROP DB statement has been executed. |No Dimensions |

+|Com_drop_table |Yes |Com Drop Table |Count |Total |The number of times DROP TABLE statement has been executed. |No Dimensions |

+|Com_insert |Yes |Com Insert |Count |Total |The number of times INSERT statement has been executed. |No Dimensions |

+|Com_select |Yes |Com Select |Count |Total |The number of times SELECT statement has been executed. |No Dimensions |

+|Com_update |Yes |Com Update |Count |Total |The number of times UPDATE statement has been executed. |No Dimensions |

+|cpu_credits_consumed |Yes |CPU Credits Consumed |Count |Maximum |CPU Credits Consumed |No Dimensions |

+|cpu_credits_remaining |Yes |CPU Credits Remaining |Count |Maximum |CPU Credits Remaining |No Dimensions |

+|cpu_percent |Yes |Host CPU Percent |Percent |Maximum |Host CPU Percent |No Dimensions |

+|HA_IO_status |Yes |HA IO Status |Count |Maximum |Status for replication IO thread running |No Dimensions |

+|HA_SQL_status |Yes |HA SQL Status |Count |Maximum |Status for replication SQL thread running |No Dimensions |

+|Innodb_buffer_pool_pages_data |Yes |InnoDB Buffer Pool Pages Data |Count |Total |The number of pages in the InnoDB buffer pool containing data. |No Dimensions |

+|Innodb_buffer_pool_pages_dirty |Yes |InnoDB Buffer Pool Pages Dirty |Count |Total |The current number of dirty pages in the InnoDB buffer pool. |No Dimensions |

+|Innodb_buffer_pool_pages_free |Yes |InnoDB Buffer Pool Pages Free |Count |Total |The number of free pages in the InnoDB buffer pool. |No Dimensions |

+|Innodb_buffer_pool_read_requests |Yes |InnoDB Buffer Pool Read Requests |Count |Total |The number of logical read requests. |No Dimensions |

+|Innodb_buffer_pool_reads |Yes |InnoDB Buffer Pool Reads |Count |Total |The number of logical reads that InnoDB could not satisfy from the buffer pool, and had to read directly from disk. |No Dimensions |

+|io_consumption_percent |Yes |IO Percent |Percent |Maximum |IO Percent |No Dimensions |

+|memory_percent |Yes |Host Memory Percent |Percent |Maximum |Host Memory Percent |No Dimensions |

+|network_bytes_egress |Yes |Host Network Out |Bytes |Total |Host Network egress in bytes |No Dimensions |

+|network_bytes_ingress |Yes |Host Network In |Bytes |Total |Host Network ingress in bytes |No Dimensions |

+|Queries |Yes |Queries |Count |Total |Queries |No Dimensions |

+|Replica_IO_Running |No |Replica IO Status |Count |Maximum |Status for replication IO thread running |No Dimensions |

+|Replica_SQL_Running |No |Replica SQL Status |Count |Maximum |Status for replication SQL thread running |No Dimensions |

+|replication_lag |Yes |Replication Lag In Seconds |Seconds |Maximum |Replication lag in seconds |No Dimensions |

+|serverlog_storage_limit |Yes |Serverlog Storage Limit |Bytes |Maximum |Serverlog Storage Limit |No Dimensions |

+|serverlog_storage_percent |Yes |Serverlog Storage Percent |Percent |Maximum |Serverlog Storage Percent |No Dimensions |

+|serverlog_storage_usage |Yes |Serverlog Storage Used |Bytes |Maximum |Serverlog Storage Used |No Dimensions |

+|Slow_queries |Yes |Slow Queries |Count |Total |The number of queries that have taken more than long_query_time seconds. |No Dimensions |

+|storage_io_count |Yes |IO Count |Count |Total |The number of I/O consumed. |No Dimensions |

+|storage_limit |Yes |Storage Limit |Bytes |Maximum |Storage Limit |No Dimensions |

+|storage_percent |Yes |Storage Percent |Percent |Maximum |Storage Percent |No Dimensions |

+|storage_throttle_count |Yes |Storage Throttle Count |Count |Maximum |Storage throttle count. |No Dimensions |

+|storage_used |Yes |Storage Used |Bytes |Maximum |Storage Used |No Dimensions |

+|total_connections |Yes |Total Connections |Count |Total |Total Connections |No Dimensions |

+## Microsoft.DBforMySQL/servers

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|active_connections |Yes |Active Connections |Count |Average |Active Connections |No Dimensions |

+|backup_storage_used |Yes |Backup Storage used |Bytes |Average |Backup Storage used |No Dimensions |

+|connections_failed |Yes |Failed Connections |Count |Total |Failed Connections |No Dimensions |

+|cpu_percent |Yes |CPU percent |Percent |Average |CPU percent |No Dimensions |

+|io_consumption_percent |Yes |IO percent |Percent |Average |IO percent |No Dimensions |

+|memory_percent |Yes |Memory percent |Percent |Average |Memory percent |No Dimensions |

+|network_bytes_egress |Yes |Network Out |Bytes |Total |Network Out across active connections |No Dimensions |

+|network_bytes_ingress |Yes |Network In |Bytes |Total |Network In across active connections |No Dimensions |

+|seconds_behind_master |Yes |Replication lag in seconds |Count |Maximum |Replication lag in seconds |No Dimensions |

+|serverlog_storage_limit |Yes |Server Log storage limit |Bytes |Maximum |Server Log storage limit |No Dimensions |

+|serverlog_storage_percent |Yes |Server Log storage percent |Percent |Average |Server Log storage percent |No Dimensions |

+|serverlog_storage_usage |Yes |Server Log storage used |Bytes |Average |Server Log storage used |No Dimensions |

+|storage_limit |Yes |Storage limit |Bytes |Maximum |Storage limit |No Dimensions |

+|storage_percent |Yes |Storage percent |Percent |Average |Storage percent |No Dimensions |

+|storage_used |Yes |Storage used |Bytes |Average |Storage used |No Dimensions |

+## Microsoft.DBforPostgreSQL/flexibleServers

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|active_connections |Yes |Active Connections |Count |Average |Active Connections |No Dimensions |

+|backup_storage_used |Yes |Backup Storage Used |Bytes |Average |Backup Storage Used |No Dimensions |

+|blks_hit |Yes |Disk Blocks Hit (Preview) |Count |Total |Number of times disk blocks were found already in the buffer cache, so that a read was not necessary |DatabaseName |

+|blks_read |Yes |Disk Blocks Read (Preview) |Count |Total |Number of disk blocks read in this database |DatabaseName |

+|connections_failed |Yes |Failed Connections |Count |Total |Failed Connections |No Dimensions |

+|connections_succeeded |Yes |Succeeded Connections |Count |Total |Succeeded Connections |No Dimensions |

+|cpu_credits_consumed |Yes |CPU Credits Consumed |Count |Average |Total number of credits consumed by the database server |No Dimensions |

+|cpu_credits_remaining |Yes |CPU Credits Remaining |Count |Average |Total number of credits available to burst |No Dimensions |

+|cpu_percent |Yes |CPU percent |Percent |Average |CPU percent |No Dimensions |

+|deadlocks |Yes |Deadlocks (Preview) |Count |Total |Number of deadlocks detected in this database |DatabaseName |

+|disk_bandwidth_consumed_percentage |Yes |Disk Bandwidth Consumed Percentage (Preview) |Percent |Average |Percentage of disk bandwidth consumed per minute |No Dimensions |

+|disk_iops_consumed_percentage |Yes |Disk IOPS Consumed Percentage (Preview) |Percent |Average |Percentage of disk I/Os consumed per minute |No Dimensions |

+|disk_queue_depth |Yes |Disk Queue Depth |Count |Average |Number of outstanding I/O operations to the data disk |No Dimensions |

+|iops |Yes |IOPS |Count |Average |IO Operations per second |No Dimensions |

+|logical_replication_delay_in_bytes |Yes |Max Logical Replication Lag (Preview) |Bytes |Maximum |Maximum lag across all logical replication slots |No Dimensions |

+|longest_query_time_sec |Yes |Oldest Query (Preview) |Seconds |Maximum |The age in seconds of the longest query that is currently running |No Dimensions |

+|longest_transaction_time_sec |Yes |Oldest Transaction (Preview) |Seconds |Maximum |The age in seconds of the longest transaction (including idle transactions) |No Dimensions |

+|max_connections |Yes |Max Connections (Preview) |Count |Maximum |Max connections |No Dimensions |

+|maximum_used_transactionIDs |Yes |Maximum Used Transaction IDs |Count |Average |Maximum Used Transaction IDs |No Dimensions |

+|memory_percent |Yes |Memory percent |Percent |Average |Memory percent |No Dimensions |

+|network_bytes_egress |Yes |Network Out |Bytes |Total |Network Out across active connections |No Dimensions |

+|network_bytes_ingress |Yes |Network In |Bytes |Total |Network In across active connections |No Dimensions |

+|numbackends |Yes |Backends (Preview) |Count |Maximum |Number of backends connected to this database |DatabaseName |

+|oldest_backend_time_sec |Yes |Oldest Backend (Preview) |Seconds |Maximum |The age in seconds of the oldest backend (irrespective of the state) |No Dimensions |

+|oldest_backend_xmin |Yes |Oldest xmin (Preview) |Count |Maximum |The actual value of the oldest xmin. |No Dimensions |

+|oldest_backend_xmin_age |Yes |Oldest xmin Age (Preview) |Count |Maximum |Age in units of the oldest xmin. It indicated how many transactions passed since oldest xmin |No Dimensions |

+|physical_replication_delay_in_bytes |Yes |Max Physical Replication Lag (Preview) |Bytes |Maximum |Maximum lag across all asynchronous physical replication slots |No Dimensions |

+|physical_replication_delay_in_seconds |Yes |Read Replica Lag (Preview) |Seconds |Maximum |Read Replica lag in seconds |No Dimensions |

+|read_iops |Yes |Read IOPS |Count |Average |Number of data disk I/O read operations per second |No Dimensions |

+|read_throughput |Yes |Read Throughput Bytes/Sec |Count |Average |Bytes read per second from the data disk during monitoring period |No Dimensions |

+|sessions_by_state |Yes |Sessions by State (Preview) |Count |Maximum |Overall state of the backends |State |

+|sessions_by_wait_event_type |Yes |Sessions by WaitEventType (Preview) |Count |Maximum |Sessions by the type of event for which the backend is waiting |WaitEventType |

+|storage_free |Yes |Storage Free |Bytes |Average |Storage Free |No Dimensions |

+|storage_percent |Yes |Storage percent |Percent |Average |Storage percent |No Dimensions |

+|storage_used |Yes |Storage used |Bytes |Average |Storage used |No Dimensions |

+|temp_bytes |Yes |Temporary Files Size (Preview) |Bytes |Total |Total amount of data written to temporary files by queries in this database |DatabaseName |

+|temp_files |Yes |Temporary Files (Preview) |Count |Total |Number of temporary files created by queries in this database |DatabaseName |

+|tup_deleted |Yes |Tuples Deleted (Preview) |Count |Total |Number of rows deleted by queries in this database |DatabaseName |

+|tup_fetched |Yes |Tuples Fetched (Preview) |Count |Total |Number of rows fetched by queries in this database |DatabaseName |

+|tup_inserted |Yes |Tuples Inserted (Preview) |Count |Total |Number of rows inserted by queries in this database |DatabaseName |

+|tup_returned |Yes |Tuples Returned (Preview) |Count |Total |Number of rows returned by queries in this database |DatabaseName |

+|tup_updated |Yes |Tuples Updated (Preview) |Count |Total |Number of rows updated by queries in this database |DatabaseName |

+|txlogs_storage_used |Yes |Transaction Log Storage Used |Bytes |Average |Transaction Log Storage Used |No Dimensions |

+|write_iops |Yes |Write IOPS |Count |Average |Number of data disk I/O write operations per second |No Dimensions |

+|write_throughput |Yes |Write Throughput Bytes/Sec |Count |Average |Bytes written per second to the data disk during monitoring period |No Dimensions |

+|xact_commit |Yes |Transactions Committed (Preview) |Count |Total |Number of transactions in this database that have been committed |DatabaseName |

+|xact_rollback |Yes |Transactions Rolled Back (Preview) |Count |Total |Number of transactions in this database that have been rolled back |DatabaseName |

+|xact_total |Yes |Total Transactions (Preview) |Count |Total |Number of total transactions executed in this database |DatabaseName |

+## Microsoft.DBForPostgreSQL/serverGroupsv2

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|active_connections |Yes |Active Connections |Count |Average |Active Connections |ServerName |

+|apps_reserved_memory_percent |Yes |Reserved Memory percent |Percent |Average |Percentage of Commit Memory Limit Reserved by Applications |ServerName |

+|cpu_credits_consumed |Yes |CPU Credits Consumed |Count |Average |Total number of credits consumed by the node. Only available when burstable compute is provisioned on the node. |ServerName |

+|cpu_credits_remaining |Yes |CPU Credits Remaining |Count |Average |Total number of credits available to burst. Only available when burstable compute is provisioned on the node. |ServerName |

+|cpu_percent |Yes |CPU percent |Percent |Average |CPU percent |ServerName |

+|iops |Yes |IOPS |Count |Average |IO operations per second |ServerName |

+|memory_percent |Yes |Memory percent |Percent |Average |Memory percent |ServerName |

+|network_bytes_egress |Yes |Network Out |Bytes |Total |Network Out across active connections |ServerName |

+|network_bytes_ingress |Yes |Network In |Bytes |Total |Network In across active connections |ServerName |

+|replication_lag |Yes |Replication lag |MilliSeconds |Average |Allows to see how much read replica nodes are behind their counterparts in the primary cluster |ServerName |

+|storage_percent |Yes |Storage percent |Percent |Average |Storage percent |ServerName |

+|storage_used |Yes |Storage used |Bytes |Average |Storage used |ServerName |

+|vm_cached_bandwidth_percent |Yes |VM Cached Bandwidth Consumed Percentage |Percent |Average |Percentage of cached disk bandwidth consumed by the VM |ServerName |

+|vm_cached_iops_percent |Yes |VM Cached IOPS Consumed Percentage |Percent |Average |Percentage of cached disk IOPS consumed by the VM |ServerName |

+|vm_uncached_bandwidth_percent |Yes |VM Uncached Bandwidth Consumed Percentage |Percent |Average |Percentage of uncached disk bandwidth consumed by the VM |ServerName |

+|vm_uncached_iops_percent |Yes |VM Uncached IOPS Consumed Percentage |Percent |Average |Percentage of uncached disk IOPS consumed by the VM |ServerName |

+## Microsoft.DBforPostgreSQL/servers

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|active_connections |Yes |Active Connections |Count |Average |Active Connections |No Dimensions |

+|backup_storage_used |Yes |Backup Storage Used |Bytes |Average |Backup Storage Used |No Dimensions |

+|connections_failed |Yes |Failed Connections |Count |Total |Failed Connections |No Dimensions |

+|cpu_percent |Yes |CPU percent |Percent |Average |CPU percent |No Dimensions |

+|io_consumption_percent |Yes |IO percent |Percent |Average |IO percent |No Dimensions |

+|memory_percent |Yes |Memory percent |Percent |Average |Memory percent |No Dimensions |

+|network_bytes_egress |Yes |Network Out |Bytes |Total |Network Out across active connections |No Dimensions |

+|network_bytes_ingress |Yes |Network In |Bytes |Total |Network In across active connections |No Dimensions |

+|pg_replica_log_delay_in_bytes |Yes |Max Lag Across Replicas |Bytes |Maximum |Lag in bytes of the most lagging replica |No Dimensions |

+|pg_replica_log_delay_in_seconds |Yes |Replica Lag |Seconds |Maximum |Replica lag in seconds |No Dimensions |

+|serverlog_storage_limit |Yes |Server Log storage limit |Bytes |Maximum |Server Log storage limit |No Dimensions |

+|serverlog_storage_percent |Yes |Server Log storage percent |Percent |Average |Server Log storage percent |No Dimensions |

+|serverlog_storage_usage |Yes |Server Log storage used |Bytes |Average |Server Log storage used |No Dimensions |

+|storage_limit |Yes |Storage limit |Bytes |Maximum |Storage limit |No Dimensions |

+|storage_percent |Yes |Storage percent |Percent |Average |Storage percent |No Dimensions |

+|storage_used |Yes |Storage used |Bytes |Average |Storage used |No Dimensions |

+## Microsoft.DBforPostgreSQL/serversv2

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|active_connections |Yes |Active Connections |Count |Average |Active Connections |No Dimensions |

+|cpu_percent |Yes |CPU percent |Percent |Average |CPU percent |No Dimensions |

+|iops |Yes |IOPS |Count |Average |IO Operations per second |No Dimensions |

+|memory_percent |Yes |Memory percent |Percent |Average |Memory percent |No Dimensions |

+|network_bytes_egress |Yes |Network Out |Bytes |Total |Network Out across active connections |No Dimensions |

+|network_bytes_ingress |Yes |Network In |Bytes |Total |Network In across active connections |No Dimensions |

+|storage_percent |Yes |Storage percent |Percent |Average |Storage percent |No Dimensions |

+|storage_used |Yes |Storage used |Bytes |Average |Storage used |No Dimensions |

+## Microsoft.Devices/IotHubs

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|c2d.commands.egress.abandon.success |Yes |C2D messages abandoned |Count |Total |Number of cloud-to-device messages abandoned by the device |No Dimensions |

+|c2d.commands.egress.complete.success |Yes |C2D message deliveries completed |Count |Total |Number of cloud-to-device message deliveries completed successfully by the device |No Dimensions |

+|c2d.commands.egress.reject.success |Yes |C2D messages rejected |Count |Total |Number of cloud-to-device messages rejected by the device |No Dimensions |

+|c2d.methods.failure |Yes |Failed direct method invocations |Count |Total |The count of all failed direct method calls. |No Dimensions |

+|c2d.methods.requestSize |Yes |Request size of direct method invocations |Bytes |Average |The average, min, and max of all successful direct method requests. |No Dimensions |

+|c2d.methods.responseSize |Yes |Response size of direct method invocations |Bytes |Average |The average, min, and max of all successful direct method responses. |No Dimensions |

+|c2d.methods.success |Yes |Successful direct method invocations |Count |Total |The count of all successful direct method calls. |No Dimensions |

+|c2d.twin.read.failure |Yes |Failed twin reads from back end |Count |Total |The count of all failed back-end-initiated twin reads. |No Dimensions |

+|c2d.twin.read.size |Yes |Response size of twin reads from back end |Bytes |Average |The average, min, and max of all successful back-end-initiated twin reads. |No Dimensions |

+|c2d.twin.read.success |Yes |Successful twin reads from back end |Count |Total |The count of all successful back-end-initiated twin reads. |No Dimensions |

+|c2d.twin.update.failure |Yes |Failed twin updates from back end |Count |Total |The count of all failed back-end-initiated twin updates. |No Dimensions |

+|c2d.twin.update.size |Yes |Size of twin updates from back end |Bytes |Average |The average, min, and max size of all successful back-end-initiated twin updates. |No Dimensions |

+|c2d.twin.update.success |Yes |Successful twin updates from back end |Count |Total |The count of all successful back-end-initiated twin updates. |No Dimensions |

+|C2DMessagesExpired |Yes |C2D Messages Expired |Count |Total |Number of expired cloud-to-device messages |No Dimensions |

+|configurations |Yes |Configuration Metrics |Count |Total |Metrics for Configuration Operations |No Dimensions |

+|connectedDeviceCount |No |Connected devices |Count |Average |Number of devices connected to your IoT hub |No Dimensions |

+|d2c.endpoints.egress.builtIn.events |Yes |Routing: messages delivered to messages/events |Count |Total |The number of times IoT Hub routing successfully delivered messages to the built-in endpoint (messages/events). |No Dimensions |

+|d2c.endpoints.egress.eventHubs |Yes |Routing: messages delivered to Event Hub |Count |Total |The number of times IoT Hub routing successfully delivered messages to Event Hub endpoints. |No Dimensions |

+|d2c.endpoints.egress.serviceBusQueues |Yes |Routing: messages delivered to Service Bus Queue |Count |Total |The number of times IoT Hub routing successfully delivered messages to Service Bus queue endpoints. |No Dimensions |

+|d2c.endpoints.egress.serviceBusTopics |Yes |Routing: messages delivered to Service Bus Topic |Count |Total |The number of times IoT Hub routing successfully delivered messages to Service Bus topic endpoints. |No Dimensions |

+|d2c.endpoints.egress.storage |Yes |Routing: messages delivered to storage |Count |Total |The number of times IoT Hub routing successfully delivered messages to storage endpoints. |No Dimensions |

+|d2c.endpoints.egress.storage.blobs |Yes |Routing: blobs delivered to storage |Count |Total |The number of times IoT Hub routing delivered blobs to storage endpoints. |No Dimensions |

+|d2c.endpoints.egress.storage.bytes |Yes |Routing: data delivered to storage |Bytes |Total |The amount of data (bytes) IoT Hub routing delivered to storage endpoints. |No Dimensions |

+|d2c.endpoints.latency.builtIn.events |Yes |Routing: message latency for messages/events |MilliSeconds |Average |The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into the built-in endpoint (messages/events). |No Dimensions |

+|d2c.endpoints.latency.eventHubs |Yes |Routing: message latency for Event Hub |MilliSeconds |Average |The average latency (milliseconds) between message ingress to IoT Hub and message ingress into an Event Hub endpoint. |No Dimensions |

+|d2c.endpoints.latency.serviceBusQueues |Yes |Routing: message latency for Service Bus Queue |MilliSeconds |Average |The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into a Service Bus queue endpoint. |No Dimensions |

+|d2c.endpoints.latency.serviceBusTopics |Yes |Routing: message latency for Service Bus Topic |MilliSeconds |Average |The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into a Service Bus topic endpoint. |No Dimensions |

+|d2c.endpoints.latency.storage |Yes |Routing: message latency for storage |MilliSeconds |Average |The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into a storage endpoint. |No Dimensions |

+|d2c.telemetry.egress.dropped |Yes |Routing: telemetry messages dropped |Count |Total |The number of times messages were dropped by IoT Hub routing due to dead endpoints. This value does not count messages delivered to fallback route as dropped messages are not delivered there. |No Dimensions |

+|d2c.telemetry.egress.fallback |Yes |Routing: messages delivered to fallback |Count |Total |The number of times IoT Hub routing delivered messages to the endpoint associated with the fallback route. |No Dimensions |

+|d2c.telemetry.egress.invalid |Yes |Routing: telemetry messages incompatible |Count |Total |The number of times IoT Hub routing failed to deliver messages due to an incompatibility with the endpoint. This value does not include retries. |No Dimensions |

+|d2c.telemetry.egress.orphaned |Yes |Routing: telemetry messages orphaned |Count |Total |The number of times messages were orphaned by IoT Hub routing because they didn't match any routing rules (including the fallback rule). |No Dimensions |

+|d2c.telemetry.egress.success |Yes |Routing: telemetry messages delivered |Count |Total |The number of times messages were successfully delivered to all endpoints using IoT Hub routing. If a message is routed to multiple endpoints, this value increases by one for each successful delivery. If a message is delivered to the same endpoint multiple times, this value increases by one for each successful delivery. |No Dimensions |

+|d2c.telemetry.ingress.allProtocol |Yes |Telemetry message send attempts |Count |Total |Number of device-to-cloud telemetry messages attempted to be sent to your IoT hub |No Dimensions |

+|d2c.telemetry.ingress.sendThrottle |Yes |Number of throttling errors |Count |Total |Number of throttling errors due to device throughput throttles |No Dimensions |

+|d2c.telemetry.ingress.success |Yes |Telemetry messages sent |Count |Total |Number of device-to-cloud telemetry messages sent successfully to your IoT hub |No Dimensions |

+|d2c.twin.read.failure |Yes |Failed twin reads from devices |Count |Total |The count of all failed device-initiated twin reads. |No Dimensions |

+|d2c.twin.read.size |Yes |Response size of twin reads from devices |Bytes |Average |The average, min, and max of all successful device-initiated twin reads. |No Dimensions |

+|d2c.twin.read.success |Yes |Successful twin reads from devices |Count |Total |The count of all successful device-initiated twin reads. |No Dimensions |

+|d2c.twin.update.failure |Yes |Failed twin updates from devices |Count |Total |The count of all failed device-initiated twin updates. |No Dimensions |

+|d2c.twin.update.size |Yes |Size of twin updates from devices |Bytes |Average |The average, min, and max size of all successful device-initiated twin updates. |No Dimensions |

+|d2c.twin.update.success |Yes |Successful twin updates from devices |Count |Total |The count of all successful device-initiated twin updates. |No Dimensions |

+|dailyMessageQuotaUsed |Yes |Total number of messages used |Count |Maximum |Number of total messages used today |No Dimensions |

+|deviceDataUsage |Yes |Total device data usage |Bytes |Total |Bytes transferred to and from any devices connected to IotHub |No Dimensions |

+|deviceDataUsageV2 |Yes |Total device data usage (preview) |Bytes |Total |Bytes transferred to and from any devices connected to IotHub |No Dimensions |

+|devices.connectedDevices.allProtocol |Yes |Connected devices (deprecated) |Count |Total |Number of devices connected to your IoT hub |No Dimensions |

+|devices.totalDevices |Yes |Total devices (deprecated) |Count |Total |Number of devices registered to your IoT hub |No Dimensions |

+|EventGridDeliveries |Yes |Event Grid deliveries |Count |Total |The number of IoT Hub events published to Event Grid. Use the Result dimension for the number of successful and failed requests. EventType dimension shows the type of event (https://aka.ms/ioteventgrid). |Result, EventType |

+|EventGridLatency |Yes |Event Grid latency |MilliSeconds |Average |The average latency (milliseconds) from when the Iot Hub event was generated to when the event was published to Event Grid. This number is an average between all event types. Use the EventType dimension to see latency of a specific type of event. |EventType |

+|jobs.cancelJob.failure |Yes |Failed job cancellations |Count |Total |The count of all failed calls to cancel a job. |No Dimensions |

+|jobs.cancelJob.success |Yes |Successful job cancellations |Count |Total |The count of all successful calls to cancel a job. |No Dimensions |

+|jobs.completed |Yes |Completed jobs |Count |Total |The count of all completed jobs. |No Dimensions |

+|jobs.createDirectMethodJob.failure |Yes |Failed creations of method invocation jobs |Count |Total |The count of all failed creation of direct method invocation jobs. |No Dimensions |

+|jobs.createDirectMethodJob.success |Yes |Successful creations of method invocation jobs |Count |Total |The count of all successful creation of direct method invocation jobs. |No Dimensions |

+|jobs.createTwinUpdateJob.failure |Yes |Failed creations of twin update jobs |Count |Total |The count of all failed creation of twin update jobs. |No Dimensions |

+|jobs.createTwinUpdateJob.success |Yes |Successful creations of twin update jobs |Count |Total |The count of all successful creation of twin update jobs. |No Dimensions |

+|jobs.failed |Yes |Failed jobs |Count |Total |The count of all failed jobs. |No Dimensions |

+|jobs.listJobs.failure |Yes |Failed calls to list jobs |Count |Total |The count of all failed calls to list jobs. |No Dimensions |

+|jobs.listJobs.success |Yes |Successful calls to list jobs |Count |Total |The count of all successful calls to list jobs. |No Dimensions |

+|jobs.queryJobs.failure |Yes |Failed job queries |Count |Total |The count of all failed calls to query jobs. |No Dimensions |

+|jobs.queryJobs.success |Yes |Successful job queries |Count |Total |The count of all successful calls to query jobs. |No Dimensions |

+|RoutingDataSizeInBytesDelivered |Yes |Routing Delivery Message Size in Bytes (preview) |Bytes |Total |The total size in bytes of messages delivered by IoT hub to an endpoint. You can use the EndpointName and EndpointType dimensions to view the size of the messages in bytes delivered to your different endpoints. The metric value increases for every message delivered, including if the message is delivered to multiple endpoints or if the message is delivered to the same endpoint multiple times. |EndpointType, EndpointName, RoutingSource |

+|RoutingDeliveries |Yes |Routing Deliveries (preview) |Count |Total |The number of times IoT Hub attempted to deliver messages to all endpoints using routing. To see the number of successful or failed attempts, use the Result dimension. To see the reason of failure, like invalid, dropped, or orphaned, use the FailureReasonCategory dimension. You can also use the EndpointName and EndpointType dimensions to understand how many messages were delivered to your different endpoints. The metric value increases by one for each delivery attempt, including if the message is delivered to multiple endpoints or if the message is delivered to the same endpoint multiple times. |EndpointType, EndpointName, FailureReasonCategory, Result, RoutingSource |

+|RoutingDeliveryLatency |Yes |Routing Delivery Latency (preview) |MilliSeconds |Average |The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into an endpoint. You can use the EndpointName and EndpointType dimensions to understand the latency to your different endpoints. |EndpointType, EndpointName, RoutingSource |

+|totalDeviceCount |No |Total devices |Count |Average |Number of devices registered to your IoT hub |No Dimensions |

+|twinQueries.failure |Yes |Failed twin queries |Count |Total |The count of all failed twin queries. |No Dimensions |

+|twinQueries.resultSize |Yes |Twin queries result size |Bytes |Average |The average, min, and max of the result size of all successful twin queries. |No Dimensions |

+|twinQueries.success |Yes |Successful twin queries |Count |Total |The count of all successful twin queries. |No Dimensions |

+## Microsoft.Devices/provisioningServices

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|AttestationAttempts |Yes |Attestation attempts |Count |Total |Number of device attestations attempted |ProvisioningServiceName, Status, Protocol |

+|DeviceAssignments |Yes |Devices assigned |Count |Total |Number of devices assigned to an IoT hub |ProvisioningServiceName, IotHubName |

+|RegistrationAttempts |Yes |Registration attempts |Count |Total |Number of device registrations attempted |ProvisioningServiceName, IotHubName, Status |

+## Microsoft.DigitalTwins/digitalTwinsInstances

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|ApiRequests |Yes |API Requests |Count |Total |The number of API requests made for Digital Twins read, write, delete and query operations. |Operation, Authentication, Protocol, StatusCode, StatusCodeClass, StatusText |

+|ApiRequestsFailureRate |Yes |API Requests Failure Rate |Percent |Average |The percentage of API requests that the service receives for your instance that return an internal error (500) response code for Digital Twins read, write, delete and query operations. |Operation, Authentication, Protocol |

+|ApiRequestsLatency |Yes |API Requests Latency |Milliseconds |Average |The response time for API requests, i.e. from when the request is received by Azure Digital Twins until the service sends a success/fail result for Digital Twins read, write, delete and query operations. |Operation, Authentication, Protocol, StatusCode, StatusCodeClass, StatusText |

+|BillingApiOperations |Yes |Billing API Operations |Count |Total |Billing metric for the count of all API requests made against the Azure Digital Twins service. |MeterId |

+|BillingMessagesProcessed |Yes |Billing Messages Processed |Count |Total |Billing metric for the number of messages sent out from Azure Digital Twins to external endpoints. |MeterId |

+|BillingQueryUnits |Yes |Billing Query Units |Count |Total |The number of Query Units, an internally computed measure of service resource usage, consumed to execute queries. |MeterId |

+|BulkOperationEntityCount |Yes |Bulk Operation Entity Count (preview) |Count |Total |The number of twins, models, or relationships processed by a bulk operation. |Operation, Result |

+|BulkOperationLatency |Yes |Bulk Operation Latency (preview) |Milliseconds |Average |Total time taken for a bulk operation to complete. |Operation, Authentication, Protocol |

+|DataHistoryRouting |Yes |Data History Messages Routed (preview) |Count |Total |The number of messages routed to a time series database. |EndpointType, Result |

+|DataHistoryRoutingFailureRate |Yes |Data History Routing Failure Rate (preview) |Percent |Average |The percentage of events that result in an error as they are routed from Azure Digital Twins to a time series database. |EndpointType |

+|DataHistoryRoutingLatency |Yes |Data History Routing Latency (preview) |Milliseconds |Average |Time elapsed between an event getting routed from Azure Digital Twins to when it is posted to a time series database. |EndpointType, Result |

+|IngressEvents |Yes |Ingress Events |Count |Total |The number of incoming telemetry events into Azure Digital Twins. |Result |

+|IngressEventsFailureRate |Yes |Ingress Events Failure Rate |Percent |Average |The percentage of incoming telemetry events for which the service returns an internal error (500) response code. |No Dimensions |

+|IngressEventsLatency |Yes |Ingress Events Latency |Milliseconds |Average |The time from when an event arrives to when it is ready to be egressed by Azure Digital Twins, at which point the service sends a success/fail result. |Result |

+|ModelCount |Yes |Model Count |Count |Total |Total number of models in the Azure Digital Twins instance. Use this metric to determine if you are approaching the service limit for max number of models allowed per instance. |No Dimensions |

+|Routing |Yes |Messages Routed |Count |Total |The number of messages routed to an endpoint Azure service such as Event Hub, Service Bus or Event Grid. |EndpointType, Result |

+|RoutingFailureRate |Yes |Routing Failure Rate |Percent |Average |The percentage of events that result in an error as they are routed from Azure Digital Twins to an endpoint Azure service such as Event Hub, Service Bus or Event Grid. |EndpointType |

+|RoutingLatency |Yes |Routing Latency |Milliseconds |Average |Time elapsed between an event getting routed from Azure Digital Twins to when it is posted to the endpoint Azure service such as Event Hub, Service Bus or Event Grid. |EndpointType, Result |

+|TwinCount |Yes |Twin Count |Count |Total |Total number of twins in the Azure Digital Twins instance. Use this metric to determine if you are approaching the service limit for max number of twins allowed per instance. |No Dimensions |

+## Microsoft.DocumentDB/cassandraClusters

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|cassandra_cache_capacity |No |capacity |Bytes |Total |Cache capacity in bytes. |cassandra_datacenter, cassandra_node, cache_name |

+|cassandra_cache_entries |No |entries |Count |Total |Total number of cache entries. |cassandra_datacenter, cassandra_node, cache_name |

+|cassandra_cache_hit_rate |No |hit rate |Percent |Average |All time cache hit rate. |cassandra_datacenter, cassandra_node, cache_name |

+|cassandra_cache_hits |No |hits |Count |Total |Total number of cache hits. |cassandra_datacenter, cassandra_node, cache_name |

+|cassandra_cache_miss_latency_histogram |No |cache miss latency average (microseconds) |Count |Average |Average cache miss latency (in microseconds). |cassandra_datacenter, cassandra_node, quantile |

+|cassandra_cache_miss_latency_p99 |No |cache miss latency p99 (microseconds) |Count |Average |p99 Latency of misses. |cassandra_datacenter, cassandra_node, cache_name |

+|cassandra_cache_requests |No |requests |Count |Total |Total number of cache requests. |cassandra_datacenter, cassandra_node, cache_name |

+|cassandra_cache_size |No |occupied cache size |Bytes |Total |Total size of occupied cache, in bytes. |cassandra_datacenter, cassandra_node, cache_name |

+|cassandra_client_auth_failure |No |auth failure (deprecated) |Count |Total |Number of failed client authentication requests. |cassandra_datacenter, cassandra_node |

+|cassandra_client_auth_failure2 |No |auth failure |Count |Total |Number of failed client authentication requests. |cassandra_datacenter, cassandra_node |

+|cassandra_client_auth_success |No |auth success |Count |Total |Number of successful client authentication requests. |cassandra_datacenter, cassandra_node |

+|cassandra_client_request_condition_not_met |No |condition not met |Count |Total |Number of transaction preconditions did not match current values. |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_client_request_contention_histogram |No |contention average |Count |Average |How many contended reads/writes were encountered in average. |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_client_request_contention_histogram_p99 |No |contention p99 |Count |Average |p99 How many contended writes were encountered. |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_client_request_failures |No |failures (deprecated) |Count |Total |Number of transaction failures encountered. |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_client_request_failures2 |No |failures |Count |Total |Number of transaction failures encountered. |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_client_request_latency_histogram |No |client request latency average (microseconds) |Count |Average |Average client request latency (in microseconds). |cassandra_datacenter, cassandra_node, quantile, request_type |

+|cassandra_client_request_latency_p99 |No |client request latency p99 (microseconds) |Count |Average |p99 client request latency (in microseconds). |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_client_request_timeouts |No |timeouts (deprecated) |Count |Total |Number of timeouts encountered. |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_client_request_timeouts2 |No |timeouts |Count |Total |Number of timeouts encountered. |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_client_request_unfinished_commit |No |unfinished commit |Count |Total |Number of transactions that were committed on write. |cassandra_datacenter, cassandra_node, request_type |

+|cassandra_commit_log_waiting_on_commit_latency_histogram |No |commit latency on waiting average (microseconds) |Count |Average |Average time spent waiting on CL fsync (in microseconds); for Periodic this is only occurs when the sync is lagging its sync interval. |cassandra_datacenter, cassandra_node, quantile |

+|cassandra_cql_prepared_statements_executed |No |prepared statements executed |Count |Total |Number of prepared statements executed. |cassandra_datacenter, cassandra_node |

+|cassandra_cql_regular_statements_executed |No |regular statements executed |Count |Total |Number of non prepared statements executed. |cassandra_datacenter, cassandra_node |

+|cassandra_jvm_gc_count |No |gc count |Count |Total |Total number of collections that have occurred. |cassandra_datacenter, cassandra_node |

+|cassandra_jvm_gc_time |No |gc time |MilliSeconds |Average |Approximate accumulated collection elapsed time. |cassandra_datacenter, cassandra_node |

+|cassandra_table_all_memtables_live_data_size |No |all memtables live data size |Bytes |Total |Total amount of live data stored in the memtables (2i and pending flush memtables included) that resides off-heap, excluding any data structure overhead. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_all_memtables_off_heap_size |No |all memtables off heap size |Bytes |Total |Total amount of data stored in the memtables (2i and pending flush memtables included) that resides off-heap. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_bloom_filter_disk_space_used |No |bloom filter disk space used |Bytes |Total |Disk space used by bloom filter (in bytes). |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_bloom_filter_false_positives |No |bloom filter false positives |Count |Total |Number of false positives on table's bloom filter. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_bloom_filter_false_ratio |No |bloom filter false ratio |Percent |Average |False positive ratio of table's bloom filter. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_bloom_filter_off_heap_memory_used |No |bloom filter off-heap memory used |Bytes |Total |Off-heap memory used by bloom filter. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_bytes_flushed |No |bytes flushed |Bytes |Total |Total number of bytes flushed since server [re]start. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_cas_commit |No |cas commit average (microseconds) |Count |Average |Average latency of paxos commit round. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_cas_commit_p99 |No |cas commit p99 (microseconds) |Count |Average |p99 Latency of paxos commit round. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_cas_prepare |No |cas prepare average (microseconds) |Count |Average |Average latency of paxos prepare round. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_cas_prepare_p99 |No |cas prepare p99 (microseconds) |Count |Average |p99 Latency of paxos prepare round. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_cas_propose |No |cas propose average (microseconds) |Count |Average |Average latency of paxos propose round. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_cas_propose_p99 |No |cas propose p99 (microseconds) |Count |Average |p99 Latency of paxos propose round. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_col_update_time_delta_histogram |No |col update time delta average |Count |Average |Average column update time delta on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_col_update_time_delta_histogram_p99 |No |col update time delta p99 |Count |Average |p99 Column update time delta on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_compaction_bytes_written |No |compaction bytes written |Bytes |Total |Total number of bytes written by compaction since server [re]start. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_compression_metadata_off_heap_memory_used |No |compression metadata off-heap memory used |Bytes |Total |Off-heap memory used by compression metadata. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_compression_ratio |No |compression ratio |Percent |Average |Current compression ratio for all SSTables. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_coordinator_read_latency |No |coordinator read latency average (microseconds) |Count |Average |Average coordinator read latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_coordinator_read_latency_p99 |No |coordinator read latency p99 (microseconds) |Count |Average |p99 Coordinator read latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_coordinator_scan_latency |No |coordinator scan latency average (microseconds) |Count |Average |Average coordinator range scan latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_coordinator_scan_latency_p99 |No |coordinator scan latency p99 (microseconds) |Count |Average |p99 Coordinator range scan latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_dropped_mutations |No |dropped mutations (deprecated) |Count |Total |Number of dropped mutations on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_dropped_mutations2 |No |dropped mutations |Count |Total |Number of dropped mutations on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_estimated_column_count_histogram |No |estimated column count average |Count |Average |Estimated number of columns in average. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_estimated_column_count_histogram_p99 |No |estimated column count p99 |Count |Average |p99 Estimated number of columns. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_estimated_partition_count |No |estimated partition count |Count |Total |Approximate number of keys in table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_estimated_partition_size_histogram |No |estimated partition size average |Bytes |Average |Estimated partition size in average. |cassandra_datacenter, cassandra_node, quantile, table, keyspace |

+|cassandra_table_estimated_partition_size_histogram_p99 |No |estimated partition size p99 |Bytes |Average |p99 Estimated partition size (in bytes). |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_index_summary_off_heap_memory_used |No |index summary off-heap memory used |Bytes |Total |Off-heap memory used by index summary. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_key_cache_hit_rate |No |key cache hit rate |Percent |Average |Key cache hit rate for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_live_disk_space_used |No |live disk space used |Bytes |Total |Disk space used by SSTables belonging to this table (in bytes). |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_live_scanned_histogram |No |live scanned average |Count |Average |Average live cells scanned in queries on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_live_scanned_histogram_p99 |No |live scanned p99 |Count |Average |p99 Live cells scanned in queries on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_live_sstable_count |No |live sstable count |Count |Total |Number of SSTables on disk for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_max_partition_size |No |max partition size |Bytes |Maximum |Size of the largest compacted partition (in bytes). |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_mean_partition_size |No |mean partition size |Bytes |Average |Size of the average compacted partition (in bytes). |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_memtable_columns_count |No |memtable columns count |Count |Total |Total number of columns present in the memtable. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_memtable_off_heap_size |No |memtable off heap size |Bytes |Total |Total amount of data stored in the memtable that resides off-heap, including column related overhead and partitions overwritten. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_memtable_on_heap_size |No |memtable on heap size |Bytes |Total |Total amount of data stored in the memtable that resides on-heap, including column related overhead and partitions overwritten. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_memtable_switch_count |No |memtable switch count |Count |Total |Number of times flush has resulted in the memtable being switched out. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_min_partition_size |No |min partition size |Bytes |Minimum |Size of the smallest compacted partition (in bytes). |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_pending_compactions |No |pending compactions (deprecated) |Count |Total |Estimate of number of pending compactions for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_pending_compactions2 |No |pending compactions |Count |Total |Estimate of number of pending compactions for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_pending_flushes |No |pending flushes (deprecated) |Count |Total |Estimated number of flush tasks pending for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_pending_flushes2 |No |pending flushes |Count |Total |Estimated number of flush tasks pending for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_percent_repaired |No |percent repaired |Percent |Average |Percent of table data that is repaired on disk. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_range_latency |No |range latency average (microseconds) |Count |Average |Average local range scan latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_range_latency_p99 |No |range latency p99 (microseconds) |Count |Average |p99 Local range scan latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_read_latency |No |read latency average (microseconds) |Count |Average |Average local read latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_read_latency_p99 |No |read latency p99 (microseconds) |Count |Average |p99 Local read latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_row_cache_hit |No |row cache hit |Count |Total |Number of table row cache hits. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_row_cache_hit_out_of_range |No |row cache hit out of range |Count |Total |Number of table row cache hits that do not satisfy the query filter, thus went to disk. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_row_cache_miss |No |row cache miss |Count |Total |Number of table row cache misses. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_speculative_retries |No |speculative retries |Count |Total |Number of times speculative retries were sent for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_sstables_per_read_histogram |No |sstables per read average |Count |Average |Average number of sstable data files accessed per single partition read. SSTables skipped due to Bloom Filters, min-max key or partition index lookup are not taken into account. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_sstables_per_read_histogram_p99 |No |sstables per read p99 |Count |Average |p99 Number of sstable data files accessed per single partition read. SSTables skipped due to Bloom Filters, min-max key or partition index lookup are not taken into account. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_tombstone_scanned_histogram |No |tombstone scanned average |Count |Average |Average tombstones scanned in queries on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_tombstone_scanned_histogram_p99 |No |tombstone scanned p99 |Count |Average |p99 Tombstones scanned in queries on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_total_disk_space_used |No |total disk space used (deprecated) |Bytes |Total |Total disk space used by SSTables belonging to this table, including obsolete ones waiting to be GC'd. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_total_disk_space_used2 |No |total disk space used |Bytes |Total |Total disk space used by SSTables belonging to this table, including obsolete ones waiting to be GC'd. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_view_lock_acquire_time |No |view lock acquire time average |Count |Average |Average time taken acquiring a partition lock for materialized view updates on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_view_lock_acquire_time_p99 |No |view lock acquire time p99 |Count |Average |p99 Time taken acquiring a partition lock for materialized view updates on this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_view_read_time |No |view read time average |Count |Average |Average time taken during the local read of a materialized view update. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_view_read_time_p99 |No |view read time p99 |Count |Average |p99 Time taken during the local read of a materialized view update. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_waiting_on_free_memtable_space |No |waiting on free memtable space average |Count |Average |Average time spent waiting for free memtable space, either on- or off-heap. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_waiting_on_free_memtable_space_p99 |No |waiting on free memtable space p99 |Count |Average |p99 Time spent waiting for free memtable space, either on- or off-heap. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_write_latency |No |write latency average (microseconds) |Count |Average |Average local write latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_table_write_latency_p99 |No |write latency p99 (microseconds) |Count |Average |p99 Local write latency for this table. |cassandra_datacenter, cassandra_node, table, keyspace |

+|cassandra_thread_pools_active_tasks |No |active tasks |Count |Total |Number of tasks being actively worked on by this pool. |cassandra_datacenter, cassandra_node, pool_name, pool_type |

+|cassandra_thread_pools_currently_blocked_tasks |No |currently blocked tasks (deprecated) |Count |Total |Number of tasks that are currently blocked due to queue saturation but on retry will become unblocked. |cassandra_datacenter, cassandra_node, pool_name, pool_type |

+|cassandra_thread_pools_currently_blocked_tasks2 |No |currently blocked tasks |Count |Total |Number of tasks that are currently blocked due to queue saturation but on retry will become unblocked. |cassandra_datacenter, cassandra_node, pool_name, pool_type |

+|cassandra_thread_pools_max_pool_size |No |max pool size |Count |Maximum |The maximum number of threads in this pool. |cassandra_datacenter, cassandra_node, pool_name, pool_type |

+|cassandra_thread_pools_pending_tasks |No |pending tasks |Count |Total |Number of queued tasks queued up on this pool. |cassandra_datacenter, cassandra_node, pool_name, pool_type |

+|cassandra_thread_pools_total_blocked_tasks |No |total blocked tasks |Count |Total |Number of tasks that were blocked due to queue saturation. |cassandra_datacenter, cassandra_node, pool_name, pool_type |

+|cpu |No |CPU usage active |Percent |Average |CPU active usage rate |ClusterResourceName, DataCenterResourceName, Address, Kind, CPU |

+|disk_utilization |Yes |disk utilization |Percent |Average |Disk utilization rate |ClusterResourceName, DataCenterResourceName, Address |

+|diskio_merged_reads |No |disk I/O merged reads |Count |Total |disk I/O merged reads |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|diskio_merged_writes |No |disk I/O merged writes |Count |Total |disk I/O merged writes |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|diskio_read_bytes |No |disk I/O read bytes |Bytes |Total |disk I/O read bytes |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|diskio_read_time |No |disk I/O read time (milliseconds) |MilliSeconds |Total |disk I/O read time (milliseconds) |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|diskio_reads |No |disk I/O read counts |Count |Total |disk I/O read counts |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|diskio_write_bytes |No |disk I/O write bytes |Bytes |Total |disk I/O write bytes |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|diskio_write_time |No |disk I/O write time (milliseconds) |MilliSeconds |Total |disk I/O write time (milliseconds) |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|diskio_writes |No |disk I/O write counts |Count |Total |disk I/O write counts |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|ethtool_rx_bytes |No |network received bytes |Bytes |Total |network received bytes |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|ethtool_rx_packets |No |network received packets |Count |Total |network received packets |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|ethtool_tx_bytes |No |network transmitted bytes |Bytes |Total |network transmitted bytes |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|ethtool_tx_packets |No |network transmitted packets |Count |Total |network transmitted packets |ClusterResourceName, DataCenterResourceName, Address, Kind |

+|percent_mem |Yes |memory utilization |Percent |Average |Memory utilization rate |ClusterResourceName, DataCenterResourceName, Address |

+## Microsoft.DocumentDB/DatabaseAccounts

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|AddRegion |Yes |Region Added |Count |Count |Region Added |Region |

+|AutoscaleMaxThroughput |No |Autoscale Max Throughput |Count |Maximum |Autoscale Max Throughput |DatabaseName, CollectionName |

+|AvailableStorage |No |(deprecated) Available Storage |Bytes |Total |"Available Storage"will be removed from Azure Monitor at the end of September 2023. Cosmos DB collection storage size is now unlimited. The only restriction is that the storage size for each logical partition key is 20GB. You can enable PartitionKeyStatistics in Diagnostic Log to know the storage consumption for top partition keys. For more info about Cosmos DB storage quota, please check this doc https://docs.microsoft.com/azure/cosmos-db/concepts-limits. After deprecation, the remaining alert rules still defined on the deprecated metric will be automatically disabled post the deprecation date. |CollectionName, DatabaseName, Region |

+|CassandraConnectionClosures |No |Cassandra Connection Closures |Count |Total |Number of Cassandra connections that were closed, reported at a 1 minute granularity |APIType, Region, ClosureReason |

+|CassandraConnectorAvgReplicationLatency |No |Cassandra Connector Average ReplicationLatency |MilliSeconds |Average |Cassandra Connector Average ReplicationLatency |No Dimensions |

+|CassandraConnectorReplicationHealthStatus |No |Cassandra Connector Replication Health Status |Count |Count |Cassandra Connector Replication Health Status |NotStarted, ReplicationInProgress, Error |

+|CassandraKeyspaceCreate |No |Cassandra Keyspace Created |Count |Count |Cassandra Keyspace Created |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|CassandraKeyspaceDelete |No |Cassandra Keyspace Deleted |Count |Count |Cassandra Keyspace Deleted |ResourceName, ApiKind, ApiKindResourceType, OperationType |

+|CassandraKeyspaceThroughputUpdate |No |Cassandra Keyspace Throughput Updated |Count |Count |Cassandra Keyspace Throughput Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|CassandraKeyspaceUpdate |No |Cassandra Keyspace Updated |Count |Count |Cassandra Keyspace Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|CassandraRequestCharges |No |Cassandra Request Charges |Count |Total |RUs consumed for Cassandra requests made |APIType, DatabaseName, CollectionName, Region, OperationType, ResourceType |

+|CassandraRequests |No |Cassandra Requests |Count |Count |Number of Cassandra requests made |APIType, DatabaseName, CollectionName, Region, OperationType, ResourceType, ErrorCode |

+|CassandraTableCreate |No |Cassandra Table Created |Count |Count |Cassandra Table Created |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|CassandraTableDelete |No |Cassandra Table Deleted |Count |Count |Cassandra Table Deleted |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, OperationType |

+|CassandraTableThroughputUpdate |No |Cassandra Table Throughput Updated |Count |Count |Cassandra Table Throughput Updated |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|CassandraTableUpdate |No |Cassandra Table Updated |Count |Count |Cassandra Table Updated |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|CreateAccount |Yes |Account Created |Count |Count |Account Created |No Dimensions |

+|DataUsage |No |Data Usage |Bytes |Total |Total data usage reported at 5 minutes granularity |CollectionName, DatabaseName, Region |

+|DedicatedGatewayAverageCPUUsage |No |DedicatedGatewayAverageCPUUsage |Percent |Average |Average CPU usage across dedicated gateway instances |Region, MetricType |

+|DedicatedGatewayAverageMemoryUsage |No |DedicatedGatewayAverageMemoryUsage |Bytes |Average |Average memory usage across dedicated gateway instances, which is used for both routing requests and caching data |Region |

+|DedicatedGatewayCPUUsage |No |DedicatedGatewayCPUUsage |Percent |Average |CPU usage across dedicated gateway instances |Region, ApplicationType |

+|DedicatedGatewayMaximumCPUUsage |No |DedicatedGatewayMaximumCPUUsage |Percent |Average |Average Maximum CPU usage across dedicated gateway instances |Region, MetricType |

+|DedicatedGatewayMemoryUsage |No |DedicatedGatewayMemoryUsage |Bytes |Average |Memory usage across dedicated gateway instances |Region, ApplicationType |

+|DedicatedGatewayRequests |Yes |DedicatedGatewayRequests |Count |Count |Requests at the dedicated gateway |DatabaseName, CollectionName, CacheExercised, OperationName, Region, CacheHit |

+|DeleteAccount |Yes |Account Deleted |Count |Count |Account Deleted |No Dimensions |

+|DocumentCount |No |Document Count |Count |Total |Total document count reported at 5 minutes, 1 hour and 1 day granularity |CollectionName, DatabaseName, Region |

+|DocumentQuota |No |Document Quota |Bytes |Total |Total storage quota reported at 5 minutes granularity |CollectionName, DatabaseName, Region |

+|GremlinDatabaseCreate |No |Gremlin Database Created |Count |Count |Gremlin Database Created |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|GremlinDatabaseDelete |No |Gremlin Database Deleted |Count |Count |Gremlin Database Deleted |ResourceName, ApiKind, ApiKindResourceType, OperationType |

+|GremlinDatabaseThroughputUpdate |No |Gremlin Database Throughput Updated |Count |Count |Gremlin Database Throughput Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|GremlinDatabaseUpdate |No |Gremlin Database Updated |Count |Count |Gremlin Database Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|GremlinGraphCreate |No |Gremlin Graph Created |Count |Count |Gremlin Graph Created |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|GremlinGraphDelete |No |Gremlin Graph Deleted |Count |Count |Gremlin Graph Deleted |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, OperationType |

+|GremlinGraphThroughputUpdate |No |Gremlin Graph Throughput Updated |Count |Count |Gremlin Graph Throughput Updated |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|GremlinGraphUpdate |No |Gremlin Graph Updated |Count |Count |Gremlin Graph Updated |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|GremlinRequestCharges |No |Gremlin Request Charges |Count |Total |Request Units consumed for Gremlin requests made |APIType, DatabaseName, CollectionName, Region |

+|GremlinRequests |No |Gremlin Requests |Count |Count |Number of Gremlin requests made |APIType, DatabaseName, CollectionName, Region, ErrorCode |

+|IndexUsage |No |Index Usage |Bytes |Total |Total index usage reported at 5 minutes granularity |CollectionName, DatabaseName, Region |

+|IntegratedCacheEvictedEntriesSize |No |IntegratedCacheEvictedEntriesSize |Bytes |Average |Size of the entries evicted from the integrated cache |Region |

+|IntegratedCacheItemExpirationCount |No |IntegratedCacheItemExpirationCount |Count |Average |Number of items evicted from the integrated cache due to TTL expiration |Region, CacheEntryType |

+|IntegratedCacheItemHitRate |No |IntegratedCacheItemHitRate |Percent |Average |Number of point reads that used the integrated cache divided by number of point reads routed through the dedicated gateway with eventual consistency |Region, CacheEntryType |

+|IntegratedCacheQueryExpirationCount |No |IntegratedCacheQueryExpirationCount |Count |Average |Number of queries evicted from the integrated cache due to TTL expiration |Region, CacheEntryType |

+|IntegratedCacheQueryHitRate |No |IntegratedCacheQueryHitRate |Percent |Average |Number of queries that used the integrated cache divided by number of queries routed through the dedicated gateway with eventual consistency |Region, CacheEntryType |

+|MaterializedViewCatchupGapInMinutes |No |Materialized View Catchup Gap In Minutes |Count |Maximum |Maximum time difference in minutes between data in source container and data propagated to materialized view |Region, TargetContainerName, BuildType |

+|MaterializedViewsBuilderAverageCPUUsage |No |Materialized Views Builder Average CPU Usage |Percent |Average |Average CPU usage across materialized view builder instances, which are used for populating data in materialized views |Region, MetricType |

+|MaterializedViewsBuilderAverageMemoryUsage |No |Materialized Views Builder Average Memory Usage |Bytes |Average |Average memory usage across materialized view builder instances, which are used for populating data in materialized views |Region |

+|MaterializedViewsBuilderMaximumCPUUsage |No |Materialized Views Builder Maximum CPU Usage |Percent |Average |Average Maximum CPU usage across materialized view builder instances, which are used for populating data in materialized views |Region, MetricType |

+|MetadataRequests |No |Metadata Requests |Count |Count |Count of metadata requests. Cosmos DB maintains system metadata collection for each account, that allows you to enumerate collections, databases, etc, and their configurations, free of charge. |DatabaseName, CollectionName, Region, StatusCode, Role |

+|MongoCollectionCreate |No |Mongo Collection Created |Count |Count |Mongo Collection Created |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|MongoCollectionDelete |No |Mongo Collection Deleted |Count |Count |Mongo Collection Deleted |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, OperationType |

+|MongoCollectionThroughputUpdate |No |Mongo Collection Throughput Updated |Count |Count |Mongo Collection Throughput Updated |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|MongoCollectionUpdate |No |Mongo Collection Updated |Count |Count |Mongo Collection Updated |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|MongoDatabaseDelete |No |Mongo Database Deleted |Count |Count |Mongo Database Deleted |ResourceName, ApiKind, ApiKindResourceType, OperationType |

+|MongoDatabaseThroughputUpdate |No |Mongo Database Throughput Updated |Count |Count |Mongo Database Throughput Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|MongoDBDatabaseCreate |No |Mongo Database Created |Count |Count |Mongo Database Created |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|MongoDBDatabaseUpdate |No |Mongo Database Updated |Count |Count |Mongo Database Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|MongoRequestCharge |Yes |Mongo Request Charge |Count |Total |Mongo Request Units Consumed |DatabaseName, CollectionName, Region, CommandName, ErrorCode, Status |

+|MongoRequests |Yes |Mongo Requests |Count |Count |Number of Mongo Requests Made |DatabaseName, CollectionName, Region, CommandName, ErrorCode, Status |

+|NormalizedRUConsumption |No |Normalized RU Consumption |Percent |Maximum |Max RU consumption percentage per minute |CollectionName, DatabaseName, Region, PartitionKeyRangeId, CollectionRid, PhysicalPartitionId |

+|OfflineRegion |No |Region Offlined |Count |Count |Region Offlined |Region, StatusCode, Role, OperationName |

+|OnlineRegion |No |Region Onlined |Count |Count |Region Onlined |Region, StatusCode, Role, OperationName |

+|PhysicalPartitionSizeInfo |No |Physical Partition Size |Bytes |Maximum |Physical Partition Size in bytes |CollectionName, DatabaseName, PhysicalPartitionId, OfferOwnerRid, Region |

+|PhysicalPartitionThroughputInfo |No |Physical Partition Throughput |Count |Maximum |Physical Partition Throughput |CollectionName, DatabaseName, PhysicalPartitionId, OfferOwnerRid, Region |

+|ProvisionedThroughput |No |Provisioned Throughput |Count |Maximum |Provisioned Throughput |DatabaseName, CollectionName, AllowWrite |

+|RegionFailover |Yes |Region Failed Over |Count |Count |Region Failed Over |No Dimensions |

+|RemoveRegion |Yes |Region Removed |Count |Count |Region Removed |Region |

+|ReplicationLatency |Yes |P99 Replication Latency |MilliSeconds |Average |P99 Replication Latency across source and target regions for geo-enabled account |SourceRegion, TargetRegion |

+|ServerSideLatency |No |Server Side Latency |MilliSeconds |Average |Server Side Latency |DatabaseName, CollectionName, Region, ConnectionMode, OperationType, PublicAPIType |

+|ServerSideLatencyDirect |No |Server Side Latency Direct |MilliSeconds |Average |Server Side Latency in Direct Connection Mode |DatabaseName, CollectionName, Region, ConnectionMode, OperationType, PublicAPIType, APIType |

+|ServerSideLatencyGateway |No |Server Side Latency Gateway |MilliSeconds |Average |Server Side Latency in Gateway Connection Mode |DatabaseName, CollectionName, Region, ConnectionMode, OperationType, PublicAPIType, APIType |

+|ServiceAvailability |No |Service Availability |Percent |Average |Account requests availability at one hour, day or month granularity |No Dimensions |

+|SqlContainerCreate |No |Sql Container Created |Count |Count |Sql Container Created |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|SqlContainerDelete |No |Sql Container Deleted |Count |Count |Sql Container Deleted |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, OperationType |

+|SqlContainerThroughputUpdate |No |Sql Container Throughput Updated |Count |Count |Sql Container Throughput Updated |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|SqlContainerUpdate |No |Sql Container Updated |Count |Count |Sql Container Updated |ResourceName, ChildResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|SqlDatabaseCreate |No |Sql Database Created |Count |Count |Sql Database Created |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|SqlDatabaseDelete |No |Sql Database Deleted |Count |Count |Sql Database Deleted |ResourceName, ApiKind, ApiKindResourceType, OperationType |

+|SqlDatabaseThroughputUpdate |No |Sql Database Throughput Updated |Count |Count |Sql Database Throughput Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|SqlDatabaseUpdate |No |Sql Database Updated |Count |Count |Sql Database Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|TableTableCreate |No |AzureTable Table Created |Count |Count |AzureTable Table Created |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|TableTableDelete |No |AzureTable Table Deleted |Count |Count |AzureTable Table Deleted |ResourceName, ApiKind, ApiKindResourceType, OperationType |

+|TableTableThroughputUpdate |No |AzureTable Table Throughput Updated |Count |Count |AzureTable Table Throughput Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest |

+|TableTableUpdate |No |AzureTable Table Updated |Count |Count |AzureTable Table Updated |ResourceName, ApiKind, ApiKindResourceType, IsThroughputRequest, OperationType |

+|TotalRequests |Yes |Total Requests |Count |Count |Number of requests made |DatabaseName, CollectionName, Region, StatusCode, OperationType, Status, CapacityType |

+|TotalRequestsPreview |No |Total Requests (Preview) |Count |Count |Number of requests |DatabaseName, CollectionName, Region, StatusCode, OperationType, Status, IsExternal |

+|TotalRequestUnits |Yes |Total Request Units |Count |Total |Request Units consumed |DatabaseName, CollectionName, Region, StatusCode, OperationType, Status, CapacityType |

+|TotalRequestUnitsPreview |No |Total Request Units (Preview) |Count |Total |Request Units consumed with CapacityType |DatabaseName, CollectionName, Region, StatusCode, OperationType, Status, CapacityType |

+|UpdateAccountKeys |Yes |Account Keys Updated |Count |Count |Account Keys Updated |KeyType |

+|UpdateAccountNetworkSettings |Yes |Account Network Settings Updated |Count |Count |Account Network Settings Updated |No Dimensions |

+|UpdateAccountReplicationSettings |Yes |Account Replication Settings Updated |Count |Count |Account Replication Settings Updated |No Dimensions |

+|UpdateDiagnosticsSettings |No |Account Diagnostic Settings Updated |Count |Count |Account Diagnostic Settings Updated |DiagnosticSettingsName, ResourceGroupName |

+## microsoft.edgezones/edgezones

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|DiskStorageIOPSUsage |No |Disk IOPS |CountPerSecond |Average |The total IOPS generated by Managed Disks in Azure Edge Zone Enterprise site. |No Dimensions |

+|DiskStorageUsedSizeUsage |Yes |Disk Usage Percentage |Percent |Average |The utilization of the Managed Disk capacity in Azure Edge Zone Enterprise site. |No Dimensions |

+|RegionSiteConnectivity |Yes |Region Site Connectivity |Count |Average |The status of an Edge Zone Enterprise link connection to its Azure region |No Dimensions |

+|TotalDiskStorageSizeCapacity |Yes |Total Disk Capacity |Bytes |Average |The total capacity of Managed Disk in Azure Edge Zone Enterprise site. |No Dimensions |

+|TotalVcoreCapacity |Yes |Total VCore Capacity |Count |Average |The total capacity of the General-Purpose Compute vcore in Edge Zone Enterprise site. |No Dimensions |

+|VcoresUsage |Yes |Vcore Usage Percentage |Percent |Average |The utilization of the General-Purpose Compute vcores in Edge Zone Enterprise site |No Dimensions |

+## Microsoft.EventGrid/domains

+<!-- Data source : naam-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|AdvancedFilterEvaluationCount |Yes |Advanced Filter Evaluations |Count |Total |Total advanced filters evaluated across event subscriptions for this topic. |Topic, EventSubscriptionName, DomainEventSubscriptionName |

+|DeadLetteredCount |Yes |Dead Lettered Events |Count |Total |Total dead lettered events matching to this event subscription |Topic, EventSubscriptionName, DomainEventSubscriptionName, DeadLetterReason |

+|DeliveryAttemptFailCount |No |Delivery Failed Events |Count |Total |Total events failed to deliver to this event subscription |Topic, EventSubscriptionName, DomainEventSubscriptionName, Error, ErrorType |

+|DeliverySuccessCount |Yes |Delivered Events |Count |Total |Total events delivered to this event subscription |Topic, EventSubscriptionName, DomainEventSubscriptionName |

+|DestinationProcessingDurationInMs |No |Destination Processing Duration |MilliSeconds |Average |Destination processing duration in milliseconds |Topic, EventSubscriptionName, DomainEventSubscriptionName |

+|DroppedEventCount |Yes |Dropped Events |Count |Total |Total dropped events matching to this event subscription |Topic, EventSubscriptionName, DomainEventSubscriptionName, DropReason |

+|MatchedEventCount |Yes |Matched Events |Count |Total |Total events matched to this event subscription |Topic, EventSubscriptionName, DomainEventSubscriptionName |

+|PublishFailCount |Yes |Publish Failed Events |Count |Total |Total events failed to publish to this topic |Topic, ErrorType, Error |

+|PublishSuccessCount |Yes |Published Events |Count |Total |Total events published to this topic |Topic |

+|PublishSuccessLatencyInMs |Yes |Publish Success Latency |MilliSeconds |Total |Publish success latency in milliseconds |No Dimensions |

+## Microsoft.EventGrid/eventSubscriptions

+<!-- Data source : arm-->

+|Metric|Exportable via Diagnostic Settings?|Metric Display Name|Unit|Aggregation Type|Description|Dimensions|

+||||||||

+|DeadLetteredCount |Yes |Dead Lettered Events |Count |Total |Total dead lettered events matching to this event subscription |DeadLetterReason |

+|DeliveryAttemptFailCount |No |Delivery Failed Events |Count |Total |Total events failed to deliver to this event subscription |Error, ErrorType |

+|DeliverySuccessCount |Yes |Delivered Events |Count |Total |Total events delivered to this event subscription |No Dimensions |

+|DestinationProcessingDurationInMs |No |Destination Processing Duration |Milliseconds |Average |Destination processing duration in milliseconds |No Dimensions |

+|DroppedEventCount |Yes |Dropped Events |Count |Total |Total dropped events matching to this event subscription |DropReason |

+|MatchedEventCount |Yes |Matched Events |Count |Total |Total events matched to this event subscription |No Dimensions |

+## Microsoft.EventGrid/extensionTopics

+<!-- Data source : arm-->

+|PublishFailCount |Yes |Publish Failed Events |Count |Total |Total events failed to publish to this topic |ErrorType, Error |

+|PublishSuccessCount |Yes |Published Events |Count |Total |Total events published to this topic |No Dimensions |

+|PublishSuccessLatencyInMs |Yes |Publish Success Latency |Milliseconds |Total |Publish success latency in milliseconds |No Dimensions |

+|UnmatchedEventCount |Yes |Unmatched Events |Count |Total |Total events not matching any of the event subscriptions for this topic |No Dimensions |

+## Microsoft.EventGrid/partnerNamespaces

+<!-- Data source : naam-->

+|PublishFailCount |Yes |Publish Failed Events |Count |Total |Total events failed to publish to this partner namespace |ErrorType, Error |

+|PublishSuccessCount |Yes |Published Events |Count |Total |Total events published to this partner namespace |No Dimensions |

+|PublishSuccessLatencyInMs |Yes |Publish Success Latency |MilliSeconds |Total |Publish success latency in milliseconds |No Dimensions |

+|UnmatchedEventCount |Yes |Unmatched Events |Count |Total |Total events not matching any of the partner topics |No Dimensions |

+## Microsoft.EventGrid/partnerTopics

+<!-- Data source : naam-->

+|AdvancedFilterEvaluationCount |Yes |Advanced Filter Evaluations |Count |Total |Total advanced filters evaluated across event subscriptions for this partner topic. |EventSubscriptionName |

+|DeadLetteredCount |Yes |Dead Lettered Events |Count |Total |Total dead lettered events matching to this event subscription |DeadLetterReason, EventSubscriptionName |

+|DeliveryAttemptFailCount |No |Delivery Failed Events |Count |Total |Total events failed to deliver to this event subscription |Error, ErrorType, EventSubscriptionName |

+|DeliverySuccessCount |Yes |Delivered Events |Count |Total |Total events delivered to this event subscription |EventSubscriptionName |

+|DestinationProcessingDurationInMs |No |Destination Processing Duration |MilliSeconds |Average |Destination processing duration in milliseconds |EventSubscriptionName |

+|DroppedEventCount |Yes |Dropped Events |Count |Total |Total dropped events matching to this event subscription |DropReason, EventSubscriptionName |

+|MatchedEventCount |Yes |Matched Events |Count |Total |Total events matched to this event subscription |EventSubscriptionName |

+|PublishSuccessCount |Yes |Published Events |Count |Total |Total events published to this partner topic |No Dimensions |

+|UnmatchedEventCount |Yes |Unmatched Events |Count |Total |Total events not matching any of the event subscriptions for this partner topic |No Dimensions |

+## Microsoft.EventGrid/systemTopics

+<!-- Data source : arm-->

+|AdvancedFilterEvaluationCount |Yes |Advanced Filter Evaluations |Count |Total |Total advanced filters evaluated across event subscriptions for this topic. |EventSubscriptionName |

+|DeadLetteredCount |Yes |Dead Lettered Events |Count |Total |Total dead lettered events matching to this event subscription |DeadLetterReason, EventSubscriptionName |

+|DeliveryAttemptFailCount |No |Delivery Failed Events |Count |Total |Total events failed to deliver to this event subscription |Error, ErrorType, EventSubscriptionName |

+|DeliverySuccessCount |Yes |Delivered Events |Count |Total |Total events delivered to this event subscription |EventSubscriptionName |

+|DestinationProcessingDurationInMs |No |Destination Processing Duration |Milliseconds |Average |Destination processing duration in milliseconds |EventSubscriptionName |

+|DroppedEventCount |Yes |Dropped Events |Count |Total |Total dropped events matching to this event subscription |DropReason, EventSubscriptionName |

+|MatchedEventCount |Yes |Matched Events |Count |Total |Total events matched to this event subscription |EventSubscriptionName |

+|PublishFailCount |Yes |Publish Failed Events |Count |Total |Total events failed to publish to this topic |ErrorType, Error |

+|PublishSuccessCount |Yes |Published Events |Count |Total |Total events published to this topic |No Dimensions |

+|PublishSuccessLatencyInMs |Yes |Publish Success Latency |Milliseconds |Total |Publish success latency in milliseconds |No Dimensions |

+|UnmatchedEventCount |Yes |Unmatched Events |Count |Total |Total events not matching any of the event subscriptions for this topic |No Dimensions |

+## Microsoft.EventGrid/topics

+<!-- Data source : naam-->

+|AdvancedFilterEvaluationCount |Yes |Advanced Filter Evaluations |Count |Total |Total advanced filters evaluated across event subscriptions for this topic. |EventSubscriptionName |

+|DeadLetteredCount |Yes |Dead Lettered Events |Count |Total |Total dead lettered events matching to this event subscription |DeadLetterReason, EventSubscriptionName |

+|DeliveryAttemptFailCount |No |Delivery Failed Events |Count |Total |Total events failed to deliver to this event subscription |Error, ErrorType, EventSubscriptionName |

+|DeliverySuccessCount |Yes |Delivered Events |Count |Total |Total events delivered to this event subscription |EventSubscriptionName |

+|DestinationProcessingDurationInMs |No |Destination Processing Duration |MilliSeconds |Average |Destination processing duration in milliseconds |EventSubscriptionName |

+|DroppedEventCount |Yes |Dropped Events |Count |Total |Total dropped events matching to this event subscription |DropReason, EventSubscriptionName |

+|MatchedEventCount |Yes |Matched Events |Count |Total |Total events matched to this event subscription |EventSubscriptionName |

+|PublishFailCount |Yes |Publish Failed Events |Count |Total |Total events failed to publish to this topic |ErrorType, Error |

+|PublishSuccessCount |Yes |Published Events |Count |Total |Total events published to this topic |No Dimensions |

+|PublishSuccessLatencyInMs |Yes |Publish Success Latency |MilliSeconds |Total |Publish success latency in milliseconds |No Dimensions |

+|UnmatchedEventCount |Yes |Unmatched Events |Count |Total |Total events not matching any of the event subscriptions for this topic |No Dimensions |

+## Microsoft.EventHub/clusters

+<!-- Data source : naam-->

+|ActiveConnections |No |ActiveConnections |Count |Average |Total Active Connections for Microsoft.EventHub. |No Dimensions |

+|AvailableMemory |No |Available Memory |Percent |Maximum |Available memory for the Event Hub Cluster as a percentage of total memory. |Role |

+|CaptureBacklog |No |Capture Backlog. |Count |Total |Capture Backlog for Microsoft.EventHub. |No Dimensions |

+|CapturedBytes |No |Captured Bytes. |Bytes |Total |Captured Bytes for Microsoft.EventHub. |No Dimensions |

+|CapturedMessages |No |Captured Messages. |Count |Total |Captured Messages for Microsoft.EventHub. |No Dimensions |

+|ConnectionsClosed |No |Connections Closed. |Count |Average |Connections Closed for Microsoft.EventHub. |No Dimensions |

+|ConnectionsOpened |No |Connections Opened. |Count |Average |Connections Opened for Microsoft.EventHub. |No Dimensions |

+|CPU |No |CPU |Percent |Maximum |CPU utilization for the Event Hub Cluster as a percentage |Role |

+|IncomingBytes |Yes |Incoming Bytes. |Bytes |Total |Incoming Bytes for Microsoft.EventHub. |No Dimensions |

+|IncomingMessages |Yes |Incoming Messages |Count |Total |Incoming Messages for Microsoft.EventHub. |No Dimensions |

+|IncomingRequests |Yes |Incoming Requests |Count |Total |Incoming Requests for Microsoft.EventHub. |No Dimensions |

+|OutgoingBytes |Yes |Outgoing Bytes. |Bytes |Total |Outgoing Bytes for Microsoft.EventHub. |No Dimensions |

+|OutgoingMessages |Yes |Outgoing Messages |Count |Total |Outgoing Messages for Microsoft.EventHub. |No Dimensions |

+|QuotaExceededErrors |No |Quota Exceeded Errors. |Count |Total |Quota Exceeded Errors for Microsoft.EventHub. |OperationResult |

+|ServerErrors |No |Server Errors. |Count |Total |Server Errors for Microsoft.EventHub. |OperationResult |

+|Size |No |Size |Bytes |Average |Size of an EventHub in Bytes. |Role |

+|SuccessfulRequests |No |Successful Requests |Count |Total |Successful Requests for Microsoft.EventHub. |OperationResult |

+|ThrottledRequests |No |Throttled Requests. |Count |Total |Throttled Requests for Microsoft.EventHub. |OperationResult |

+|UserErrors |No |User Errors. |Count |Total |User Errors for Microsoft.EventHub. |OperationResult |

+## Microsoft.EventHub/Namespaces

+<!-- Data source : naam-->

+|ActiveConnections |No |ActiveConnections |Count |Maximum |Total Active Connections for Microsoft.EventHub. |No Dimensions |

+|CaptureBacklog |No |Capture Backlog. |Count |Total |Capture Backlog for Microsoft.EventHub. |EntityName |

+|CapturedBytes |No |Captured Bytes. |Bytes |Total |Captured Bytes for Microsoft.EventHub. |EntityName |

+|CapturedMessages |No |Captured Messages. |Count |Total |Captured Messages for Microsoft.EventHub. |EntityName |

+|ConnectionsClosed |No |Connections Closed. |Count |Maximum |Connections Closed for Microsoft.EventHub. |EntityName |

+|ConnectionsOpened |No |Connections Opened. |Count |Maximum |Connections Opened for Microsoft.EventHub. |EntityName |

+|EHABL |Yes |Archive backlog messages (Deprecated) |Count |Total |Event Hub archive messages in backlog for a namespace (Deprecated) |No Dimensions |

+|EHAMBS |Yes |Archive message throughput (Deprecated) |Bytes |Total |Event Hub archived message throughput in a namespace (Deprecated) |No Dimensions |

+|EHAMSGS |Yes |Archive messages (Deprecated) |Count |Total |Event Hub archived messages in a namespace (Deprecated) |No Dimensions |

+|EHINBYTES |Yes |Incoming bytes (Deprecated) |Bytes |Total |Event Hub incoming message throughput for a namespace (Deprecated) |No Dimensions |

+|EHINMBS |Yes |Incoming bytes (obsolete) (Deprecated) |Bytes |Total |Event Hub incoming message throughput for a namespace. This metric is deprecated. Please use Incoming bytes metric instead (Deprecated) |No Dimensions |

+|EHINMSGS |Yes |Incoming Messages (Deprecated) |Count |Total |Total incoming messages for a namespace (Deprecated) |No Dimensions |

+|EHOUTBYTES |Yes |Outgoing bytes (Deprecated) |Bytes |Total |Event Hub outgoing message throughput for a namespace (Deprecated) |No Dimensions |

+|EHOUTMBS |Yes |Outgoing bytes (obsolete) (Deprecated) |Bytes |Total |Event Hub outgoing message throughput for a namespace. This metric is deprecated. Please use Outgoing bytes metric instead (Deprecated) |No Dimensions |

+|EHOUTMSGS |Yes |Outgoing Messages (Deprecated) |Count |Total |Total outgoing messages for a namespace (Deprecated) |No Dimensions |

+|FAILREQ |Yes |Failed Requests (Deprecated) |Count |Total |Total failed requests for a namespace (Deprecated) |No Dimensions |

+|IncomingBytes |Yes |Incoming Bytes. |Bytes |Total |Incoming Bytes for Microsoft.EventHub. |EntityName |

+|IncomingMessages |Yes |Incoming Messages |Count |Total |Incoming Messages for Microsoft.EventHub. |EntityName |

+|IncomingRequests |Yes |Incoming Requests |Count |Total |Incoming Requests for Microsoft.EventHub. |EntityName |

+|INMSGS |Yes |Incoming Messages (obsolete) (Deprecated) |Count |Total |Total incoming messages for a namespace. This metric is deprecated. Please use Incoming Messages metric instead (Deprecated) |No Dimensions |

+|INREQS |Yes |Incoming Requests (Deprecated) |Count |Total |Total incoming send requests for a namespace (Deprecated) |No Dimensions |

+|INTERR |Yes |Internal Server Errors (Deprecated) |Count |Total |Total internal server errors for a namespace (Deprecated) |No Dimensions |

+|MISCERR |Yes |Other Errors (Deprecated) |Count |Total |Total failed requests for a namespace (Deprecated) |No Dimensions |

+|NamespaceCpuUsage |No |CPU |Percent |Maximum |CPU usage metric for Premium SKU namespaces. |Replica |

+|NamespaceMemoryUsage |No |Memory Usage |Percent |Maximum |Memory usage metric for Premium SKU namespaces. |Replica |

+|OutgoingBytes |Yes |Outgoing Bytes. |Bytes |Total |Outgoing Bytes for Microsoft.EventHub. |EntityName |

+|OutgoingMessages |Yes |Outgoing Messages |Count |Total |Outgoing Messages for Microsoft.EventHub. |EntityName |

+|OUTMSGS |Yes |Outgoing Messages (obsolete) (Deprecated) |Count |Total |Total outgoing messages for a namespace. This metric is deprecated. Please use Outgoing Messages metric instead (Deprecated) |No Dimensions |

+|QuotaExceededErrors |No |Quota Exceeded Errors. |Count |Total |Quota Exceeded Errors for Microsoft.EventHub. |EntityName, OperationResult |

+|ServerErrors |No |Server Errors. |Count |Total |Server Errors for Microsoft.EventHub. |EntityName, OperationResult |

+|Size |No |Size |Bytes |Average |Size of an EventHub in Bytes. |EntityName |

+|SuccessfulRequests |No |Successful Requests |Count |Total |Successful Requests for Microsoft.EventHub. |EntityName, OperationResult |

+|SUCCREQ |Yes |Successful Requests (Deprecated) |Count |Total |Total successful requests for a namespace (Deprecated) |No Dimensions |

+|SVRBSY |Yes |Server Busy Errors (Deprecated) |Count |Total |Total server busy errors for a namespace (Deprecated) |No Dimensions |

+|ThrottledRequests |No |Throttled Requests. |Count |Total |Throttled Requests for Microsoft.EventHub. |EntityName, OperationResult |

+|UserErrors |No |User Errors. |Count |Total |User Errors for Microsoft.EventHub. |EntityName, OperationResult |

+## Microsoft.HDInsight/clusters

+<!-- Data source : arm-->