Closed nturinski closed 6 months ago
(I'm running with advanced because there are no resources currently available to test on basic.)
It seems like I'm never prompted about creating a log analytics workspace, but the output logs indicate it's being defaulted to an existing resource. Is this intended behavior?
(I'm running with advanced because there are no resources currently available to test on basic.)
What's the error? If you increase the sku, that will usually resolve the issue.
It seems like I'm never prompted about creating a log analytics workspace, but the output logs indicate it's being defaulted to an existing resource. Is this intended behavior?
Yeah, there's nothing to really pick and as far as I know, no benefit to really having a bunch of workspaces. I'll confirm with the App Service team, but that is the intended behavior. You must have had one created with a function app at some point.
What's the error? If you increase the sku, that will usually resolve the issue.
I assume being internal during high demand is the reason
Are you using the free tier?
It reproduces on all the tiers offered via quick picks
Leverages log analytics create step, which is required to migrate App Insights to the Workspace Based. Here is some documentation on that. This was already being done in Functions, so the step already existed.
It also uses the connection string property rather than the instrumentational key since that is the recommended path going forward.
Another reference: https://learn.microsoft.com/en-us/azure/azure-monitor/app/create-workspace-resource
How to test: