BJ Kea, thank you for the reply.
I think I understood the issue here. I assume that you are following the steps as highlighted in the following link to create the container apps - Quickstart: Deploy your first container app using the Azure portal
In this set of steps, the 4th step under "Create an environment" option mentions to "Select the Monitoring tab to create a Log Analytics workspace.".
Note that this "Monitoring" setting is optional, and you can choose "Don't save log" from this tab, if you do not want the container apps to store logs. You will still be able to stream them live but historical logs will not be available.
In case, you have already created container apps using the steps above, you can still disable the saving of logs to "Log Analytics", by following the steps below:
- In Azure portal, navigate to your "Container App" instance.
- From the "Overview" menu, click on the "Container Apps Environment" link as shown below. The Azure Container App environment is the secure boundary around one or more container apps and jobs. This is what provides the runtime environment for container apps.
- This opens up the "Container Apps Environment" instance in Azure portal. Select "Logging options" from resource menu, and click on "Don't save logs"
- Once you click "Save" on this page, the dependency on LA workspace will be removed. The logs will be only available under the "Log Stream" option, but you will not be able to review them later.
- There is also a possibility that you might see "Diagnostic Settings" too along with "Logging Option" here, if you have selected "Azure monitor" when creating the Container Apps Environment. In that case, you can review the settings under "Diagnostic Settings" and delete any setting which says that it is forwarding logs to "Log Analytics Workspace"
For more details on these options, please see Log storage and monitoring options in Azure Container Apps. Although these log saving settings are optional, they play a critical role in diagnosing and troubleshooting issues with container apps. Therefore, these options are enabled by default.
Hope this helps.
In case this still does not resolve your issue, can you please share the following information:
- How are you creating container apps? A link to the relevant document or cmdline/template (if creating using script/cmdline/PowerShell) should help us understand the issue better.
- What do you see under "Logging options" and "Diagnostic Settings" as mentioned in the steps in earlier part of this reply.
- When you deleted the "LA workspace" (as it needed to be recreated based on your last reply), did it break the container apps? Did you start receiving any specific error/s?
- "...workspace associated with my subscription" - can you please clarify this? A LA workspace is a resource, just like Virtual machines or App Service, in Azure Subscription. Like other resources, there can be multiple LA workspace in a single subscription. Why did you say that it is associated with your subscription? By chance, have you enabled "Send Activity logs to Log Analytics workspace"? If yes, you can follow the steps below to remove that dependency as well, in case it is not required:
- In Azure Portal --> Monitor --> click "Export Activity Logs".
- If you have any entry in this view, you can click on respective "Edit Setting" option in the row and "Delete" the setting which forwards the "Activity Logs" to Log Analytics Workspace.
Hope this helps. Please let me know if you have any questions.