定时器触发功能未触发 [英] Timer triggered function not fired

问题描述

1. 消费计划（Linux预览）
2. Azure管道 - Azure功能应用程序部署（有时我得到"无法同步功能应用程序的触发器。错误：网关未在指定时间段内收到'Microsoft.Web'的响应。"并重新运行发布任务）
3.   v2运行时，节点js
4. 未设置WEBSITE_TIME_ZONE
5. CRON表达式1 * * * * *（第一秒钟的每一分钟）
6. 预计将于28/05/2019,20：20：01 UTC开始，每分钟一次，但App Insights中没有其他日志，没有错误或例外
7. 最后一次收费是  28/05 / 201,20：19：01 UTC，   调用ID -   c6 2698af-314b-476a-b5fc-0a7340968ca7

1. Consumption Plan (Linux Preview)
2. Azure Pipelines - Azure Function App Deploy (sometimes I get "Failed to sync triggers for function app. Error: The gateway did not receive a response from 'Microsoft.Web' within the specified time period." and rerun release task)
3.  v2 runtime, node js
4. WEBSITE_TIME_ZONE not set
5. CRON expression 1 * * * * * (every minute on first second)
6. Expected to fire at 28/05/2019, 20:20:01 UTC, and every minute later but no further logs in App Insights, also no errors or exceptions
7. Last cal was at 28/05/2019, 20:19:01 UTC, invocation ID - c62698af-314b-476a-b5fc-0a7340968ca7

推荐答案

Hello Derman4ik，

Hello Derman4ik,

我可以通过查看计时器触发功能的后端日志正按预期的时间表执行。

I can confirm by looking at the back-end logs that your timer triggered function is executing on expected schedule.

以下是5月28日的一些执行细节：

Here are some of the Execution details for 28th May:

 2019-05-28T20:18:01.0014043+00:00
 2019-05-28T20:17:00.9986548+00:00
 2019-05-28T20:16:00.9985826+00:00
 2019-05-28T20:15:00.9986806+00:00
 2019-05-28T20:19:00.9986547+00:00
 2019-05-28T20:05:00.9985813+00:00
 2019-05-28T20:07:00.9987545+00:00
 2019-05-28T20:08:00.9986586+00:00
 2019-05-28T20:11:00.9886377+00:00
 2019-05-28T20:12:00.9885989+00:00

我们检测到您运行时为应用程序启用了记录采样的默认设置洞察。这可能会导致监视器日志中缺少执行日志。

We have detected that you are running with the default setting of logging sampling enabled for Application Insights. This could cause missing execution logs from your monitor logs.

Application Insights有一个
采样功能可以保护您在峰值负载时不会在已完成的执行中产生过多的遥测数据。当传入执行的速率超过指定阈值时，Application Insights会开始随机忽略某些传入的
执行。每秒最大执行次数的默认设置为20. 您可以在host.json中配置采样。以下是一个示例：

Application Insights has a sampling feature that can protect you from producing too much telemetry data on completed executions at times of peak load. When the rate of incoming executions exceeds a specified threshold, Application Insights starts to randomly ignore some of the incoming executions. The default setting for maximum number of executions per second is 20. You can configure sampling in host.json. Here's an example:

{
  "logging": {
    "applicationInsights": {
      "samplingSettings": {
        "isEnabled": true,
        "maxTelemetryItemsPerSecond" : 20
      }
    }
  }
}

启用应用程序洞察记录采样可能导致：



- 显示器日志中缺少定时器触发器执行

- 缺少其他数据日志



您可能只需要调整采样设置以适合您的特定监控方案。

请查看本指南以配置抽样。

Enable the application insights logging sampling might lead to:

- Timer Trigger executions missing from your monitor logs
- Other data log missing

You may just need to adjust the sampling settings to fit your particular monitoring scenario. Please review this guidance to configure sampling.

这篇关于定时器触发功能未触发的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！