This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 28.000000000000004%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
A week ago I deleted my azure monitor workspace on my kubernetes cluster. Why can I still not link my kubernetes cluster to another workspace? It prompts me to enable managed prometheus in my insights but I get an error saying I don't not have access to the azure monitor workspace or it has been deleted. How do I configure my cluster to send data to a new workspace I've created? Will I have to recreate my whole cluster?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 73%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi Aaron Taylor,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
When you deleted your Azure Monitor workspace, your Kubernetes cluster was still set up to send logs and metrics to workspace. Before connecting the cluster to a new workspace, you need to disable the monitoring integration. This means you have to unlink the old Azure Monitor workspace from the cluster. After removing the old setup, you can enable the monitoring integration again and choose the new workspace. The cluster will be linked to new workspace and monitor agents will send logs and metrics to the new workspace.
If you have Managed Prometheus for collecting metrics in your Kubernetes cluster, enable it in the new workspace., so the Prometheus agent will know to send the metrics.
There is no need to recreate the entire cluster. By unlinking the old workspace and linking a new one, you're simply updating the configuration for these agents and Prometheus to use the new workspace.
For more information, please refer Enable monitoring for Kubernetes clusters
Disable monitoring of your Kubernetes cluster
Enable monitoring for Kubernetes clusters
If you have further queries, please do let me know.
Hi Aaron Taylor,
I have provided information to your query, did you get a chance to look into it. If you have any further queries, please let me know.
Thank you
I disabled/ re-enabled the Azure monitor agent using the cli commands and got the same errors:
az aks disable-addons --resource-group <resource-group> --name <name> --addons monitoring
az aks enable-addons --resource-group <resource-group> --name <name> --addons monitoring --workspace-resource-id
Hi Aaron Taylor,
Thank you for getting back with us. Could you please try below troubleshooting steps, I have tried from my end it is working for me.
First check that if old workspace is still linked with the cluster.
az aks show --resource-group <resource-group> --name <cluster-name> --query addonProfiles
Now remove the Monitoring Add-on, wait for some time.
az aks disable-addons -a monitoring --resource-group <resource-group> --name <cluster-name>
You can see that default workspace is removed. Now attach the new workspace.
Get the new workspace ID and then Re-enable monitoring with the new workspace.
az monitor log-analytics workspace show --resource-group <resource-group> --workspace-name <new-workspace> --query id
az aks enable-addons --resource-group <resource-group> --name <cluster-name> --addons monitoring --workspace-resource-id /subscriptions/xxxx-xxxx-xxxx/resourceGroups/<resource-group>/providers/Microsoft.OperationalInsights/workspaces/<new-workspace>
You can see that new workspace is attached to the AKS cluster. Check if Managed Prometheus is enabled for the new workspace and that AKS is configured to send metrics there.
If you have further queries, please do let me know. If this solution answers your query, please click Upvote and Accept Answer as it will be useful to others who face the same issue.