You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked for previous/existing GitHub issues
Issue Type?
Question
Description
The Azure Monitor Baseline Alerts (AMBA) has a deployment pattern for Azure Landing Zones, which includes Azure Policy initiatives that deploys Alerts, Alert Processing Rules, Action Groups, etc.
There is also mention of a Retrieval-Augmented Generation (RAG) pattern, but I don't see any supported method for deploying this pattern. All I see is a list of Alerts and Thresholds, but no actual deployment mechanism (like the Azure Landing Zone pattern).
❓ Is there (or will there be) support for deploying the Azure Artificial Intelligence / GPT-RAG pattern in a similar manner?
We have a lot of users that are deploying many Azure AI services, so we're interested alerts, etc. for these services.
The text was updated successfully, but these errors were encountered:
@AErmie, thanks for your interest in AMBA. The RAG pattern does not have a deployment method yet. I have marked this as an enhancement for consideration in a future release.
Check for previous/existing GitHub issues
Issue Type?
Question
Description
The Azure Monitor Baseline Alerts (AMBA) has a deployment pattern for Azure Landing Zones, which includes Azure Policy initiatives that deploys Alerts, Alert Processing Rules, Action Groups, etc.
There is also mention of a Retrieval-Augmented Generation (RAG) pattern, but I don't see any supported method for deploying this pattern. All I see is a list of Alerts and Thresholds, but no actual deployment mechanism (like the Azure Landing Zone pattern).
❓ Is there (or will there be) support for deploying the Azure Artificial Intelligence / GPT-RAG pattern in a similar manner?
We have a lot of users that are deploying many Azure AI services, so we're interested alerts, etc. for these services.
The text was updated successfully, but these errors were encountered: