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
module"aks" {
source="Azure/aks/azurerm"version="9.2.0"...log_analytics_workspace={
id ="/subscriptions/../../providers/Microsoft.OperationalInsights/workspaces/<workspacename>"
name ="<workspacename>"
}
msi_auth_for_monitoring_enabled=true
}
tfvars variables values
N/A
Debug Output/Panic Output
N/A
Expected Behaviour
Container insight logs are available in the existing log analytics workspace provided as an input variable.
I believe this is due to a missing data collection rule.
Actual Behaviour
No logs are available in the existing log analytics workspace.
The following warning is shown when looking at the monitor settings: You do not have access to the associated data collection rule to view the log analytics workspace name or the data collection rule has been deleted.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Greenfield/Brownfield provisioning
greenfield
Terraform Version
1.9.8
Module Version
9.2.0
AzureRM Provider Version
3.117.0
Affected Resource(s)/Data Source(s)
N/A
Terraform Configuration Files
tfvars variables values
N/A
Debug Output/Panic Output
Expected Behaviour
Container insight logs are available in the existing log analytics workspace provided as an input variable.
I believe this is due to a missing data collection rule.
Actual Behaviour
No logs are available in the existing log analytics workspace.
The following warning is shown when looking at the monitor settings:
You do not have access to the associated data collection rule to view the log analytics workspace name or the data collection rule has been deleted.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: