Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

JCore-SpecWrkLoads-AVDAlerts-Fix deployment name length issues #421

Merged
merged 3 commits into from
Nov 21, 2024
Merged

JCore-SpecWrkLoads-AVDAlerts-Fix deployment name length issues #421

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
46a0622
Refactor metric alert naming to ensure deployment names are under 64 …
JCoreMS Nov 19, 2024
8c27c7c
Update documentation and versioning for AVD deployment solution; addr…
JCoreMS Nov 19, 2024
bebbe54
Update AVD documentation to correct formatting and ensure clarity; ad…
JCoreMS Nov 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/content/patterns/specialized/avd/Whats-New.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@ For information on what's new please refer to the [Releases](https://github.com/

To update your current deployment with the content from the latest release, please refer to the [Update to new release](Update-to-new-Release.md) page.

## 2024-11-20
### Deployment Names over 64 characters
An issue was discovered in which the deployment for some alerts would fail if the deployment name was over 64 characters. This was due to the Storage Account and/or ANF Volume names being too long and appended to the deployment name. Those names are now truncated if over 20 characters.

## 2024-01-25
### New features
Initial relocation from the Azure AVD Accelerator Brownfield with AVD specific Alerts on a per Host Pool basis.
Expand Down
14 changes: 7 additions & 7 deletions docs/content/patterns/specialized/avd/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,15 @@ geekdocCollapseSection: true

This solution provides a baseline of alerts for AVD that are disabled by default and for ensuring administrators and staff get meaningful and timely alerts when there are problems related to an AVD deployment. The deployment has been tested in Azure Global and Azure US Government and will incorporate storage alerts for either or both Azure Files and/or Azure Netapp Files. This solution initially was part of the Azure Virtual Desktop Solution Accelerator as a brownfield and moved to this location.

**Current Version:**
v2.1.5 (Dec 5, 2023)
**Current Version:**
v2.1.6 (Nov 20, 2024)

## Alerts Table

Table below shows the Alert Names however the number of alert rules created may be multiple based on different severity and/or additional volume or storage name designators. For example, a deployment with a single Azure Files Storage Account and an Azure NetApp Files Volume would yield 20 alert rules created. [(Excel Table)](https://github.com/Azure/azure-monitor-baseline-alerts/raw/main/docs/static/img/Avd/alerts.xlsx)

| Name | Threshold(s) (Severity) | Signal Type | Frequency | # Alert Rules |
|--- |--- |--- |--- |---
|--- |--- |--- |--- |--- |
| AVD-HostPool-Capacity (1.) | 95% (1) / 85% (2) / 50% (3)| Log Analytics | 5 min | 3/hostpool |
| AVD-HostPool-Disconnected User over n Hours (hostpoolname) | 24 (1) / 72 (2) | Log Analytics | 1 hour | 2/hostpool |
| AVD-HostPool-No Resources Available (hostpoolname) | Any are Sev1 | Log Analytics | 15 min | 1/hostpool |
Expand Down Expand Up @@ -43,10 +43,10 @@ Table below shows the Alert Names however the number of alert rules created may
| AVD-ServiceHealth-Security | na | Service Health | na | 4 |
| AVD-ServiceHealth-Service Issue | na | Service Health | na | 4 |

**NOTES:**
1. Alert based on associated Automation Account / Runbook
2. See the following for custom condition. Note that both Standard and Premium values are incorporated into the alert rule. ['How to create an alert if a file share is throttled'](https://docs.microsoft.com/azure/storage/files/storage-troubleshooting-files-performance#how-to-create-an-alert-if-a-file-share-is-throttled)
Service Health - The alert severity cannot be set or changed from 'Verbose'
**NOTES:**
1. Alert based on associated Automation Account / Runbook
2. See the following for custom condition. Note that both Standard and Premium values are incorporated into the alert rule. ['How to create an alert if a file share is throttled'](https://docs.microsoft.com/azure/storage/files/storage-troubleshooting-files-performance#how-to-create-an-alert-if-a-file-share-is-throttled)
Service Health - The alert severity cannot be set or changed from 'Verbose'

## 📣Feedback 📣

Expand Down
Loading