Azure Functions v3迁移至v4：HTTP触发器代码改造咨询

我正在将Azure Functions从v3版本迁移至v4版本，需要把原封装了Application Insights的HTTP触发器代码适配v4的app对象写法。

原有v3版本代码 #

import { AzureFunction, Context, HttpRequest } from "@azure/functions"

const cgHttpTrigger: AzureFunction = async (
  context: any,
  req: any,
  httpTrigger: AzureFunction
) => {
  return appInsights.wContext(async () => {
    const startTime = Date.now() // 启动请求跟踪计时器

    // 执行业务函数
    await httpTrigger(context, req)

    // 请求完成后跟踪数据
    a.d.trackRequest({
      name: context.req.method + " " + context.req.url,
      resultCode: context.res.status,
    }, correlationContext ?? undefined)()
  })
}

当前v4版本尝试代码 #

import { app} from '@azure/functions';

app.http('appIn', {
  methods: ['GET', 'POST'],
  handler: cgHttpTrigger(httpTrigger),
});

需要将handler改造成类似handler: async (req, context) => {return cgHttpTrigger(req, context, (req, context) => {....})}的形式，以下是具体实现方式：

改造后的完整实现 #

通过高阶函数封装Application Insights逻辑，适配v4的handler参数结构：

import { app, HttpRequest, InvocationContext } from '@azure/functions';
import * as appInsights from 'applicationinsights';

// 初始化Application Insights（需提前完成配置）
appInsights.setup().start();
const appInsightsClient = appInsights.defaultClient;

// 封装Application Insights的高阶函数
const withAppInsights = (businessHandler: (req: HttpRequest, context: InvocationContext) => Promise<any>) => {
  return async (req: HttpRequest, context: InvocationContext) => {
    return appInsights.wContext(async () => {
      const startTime = Date.now();
      let resultCode = 200;

      try {
        // 执行业务逻辑
        const response = await businessHandler(req, context);
        resultCode = response?.status ?? 200;
        return response;
      } catch (error) {
        resultCode = 500;
        context.error(error);
        throw error;
      } finally {
        // 上报请求跟踪数据
        appInsightsClient.trackRequest({
          name: `${req.method} ${req.url}`,
          resultCode: resultCode.toString(),
          duration: Date.now() - startTime,
          success: resultCode >= 200 && resultCode < 400,
          url: req.url,
          httpMethod: req.method
        });
        // 确保跟踪数据及时发送
        await appInsightsClient.flush();
      }
    });
  };
};

// 示例业务逻辑handler
const myBusinessHandler = async (req: HttpRequest, context: InvocationContext) => {
  // 这里编写你的业务逻辑代码
  return {
    status: 200,
    body: 'Hello from v4 Function with App Insights!'
  };
};

// 注册HTTP触发器，使用封装后的handler
app.http('appIn', {
  methods: ['GET', 'POST'],
  authLevel: 'anonymous', // 根据实际需求调整权限级别
  handler: withAppInsights(myBusinessHandler)
});

关键说明 #

1. 高阶函数适配：withAppInsights作为高阶函数，接收业务逻辑handler作为参数，返回符合v4要求的handler函数，实现逻辑解耦。
2. v4参数调整：v4中handler的参数顺序为(request, context)，context类型为InvocationContext，不再包含req/res属性，需直接使用传入的request对象，返回值即为响应内容。
3. 异常与跟踪优化：新增异常捕获逻辑，确保错误请求也能被正确跟踪；补充duration和success字段，让监控数据更完整。
4. 数据发送保障：在finally块中调用flush()，确保跟踪数据及时上报，避免丢失。

内容的提问来源于stack exchange，提问作者art