在 Log Analytics 工作区下的 Azure 资源中设置 Azure 函数时出错 [英] Error setting up Azure Function within Azure Resource under Log Analytics Workspace
问题描述
我在 Log Analytics 工作区下的 Azure 资源中设置 Azure 函数时出错.
I have error setting up Azure Function within Azure Resource under Log Analytics Workspace.
仅选中 AllMetrics 时，它可以工作.但是每当检查 FunctionExecutionLogs 时，就会出现如下错误:
When only AllMetrics is checked, it works. But whenever FunctionExecutionLogs is checked, error occurs like below:
1.在 Azure 门户中导航到您的日志分析工作区.
1.Nav to your log analytics workspace in azure portal.
2.在左侧边栏选项卡中，选择 Workspace Data Sources -> Azure Resources，然后在此处单击您的 azure 函数.
2.in the left blade, select Workspace Data Sources -> Azure Resources, then click your azure function there.
- 检查 FunctionExecutionLogs 并发生错误.
有什么想法吗?
设置Azure Log Analytics 使用的数据与 Azure 函数
更新
我们希望了解更多有关 Application InSights 和 Log Analytics 的信息，并使用最适合我们的工具.
We would like to understand more on Application InSights and Log Analytics, and use the best tool for us.
推荐答案
将不再支持 azure log analytics 中 azure function/web app 的FunctionExecutionLogs".
'FunctionExecutionLogs' for azure function/web app in azure log analytics will not be supported any more.
因此应用洞察是监控 azure 功能的更好选择.
以下是 MS 日志分析团队的反馈:
The following is the feedback from MS log analytics team:
几个月前，应用服务/功能团队加入了 Azure Monitor 诊断日志，但他们实际上并没有发出日志数据.
Several months ago, App Service/Functions team on-boarded to Azure Monitor diagnostic logs but they don't actually emit log data.
基本上有数以千计的诊断设置注册是无操作的，实际上并没有做任何事情.
Basically there are thousands of diagnostic setting registrations which are no-ops and don't actually do anything.
最近几周，我们一直在与 App Service 讨论在接下来的几周内将此功能作为私人预览功能发布.
Recently in the past few weeks, we've been in discussion with App Service to release this feature in the next few weeks as a private preview feature.
不幸的是，这是一项重大更改，因为只有私人预览版客户才能打开应用服务的诊断日志.请注意 - 没有实际的客户影响，因为客户之前打开的任何东西都没有开始工作.
This unfortunately is a breaking change as only private preview customers can turn on diagnostic logs for App Service. Please note -- There is no actual customer impact as whatever customers turned on previously never worked to begin with.
要修复部署脚本，我们应该要求客户更新他们的模板以仅打开指标导出而不是日志 --- 这不会对客户产生任何实际影响.
To fix the deployment script, we should ask customers to update their template to only turn on metric export and not logs --- this won't have any actual customer impact.
因此，在我们的 Log Analytics 方面，我们的 Log Analytics 团队不再支持这种情况，我们的生产组已经宣布了这一方案.
So, from our Log Analytics side, this is a scenario we are not support from our Log Analytics team which has declared by our Production Group any more.
这篇关于在 Log Analytics 工作区下的 Azure 资源中设置 Azure 函数时出错的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
