不等待在云运行容器中进行log.write（）承诺就可以了吗？

我正在使用Cloud Run@google-cloud/logging从我的express应用程序注销一些内容。

像这样的东西：

routeHandler.ts

import { Logging } from "@google-cloud/logging";

const logging = new Logging({ projectId: process.env.PROJECT_ID });
const logName = LOG_NAME; 
const log = logging.log(logName);

const resource = {
  type: "cloud_run_revision",
  labels: { ... }
};

export const routeHandler: RequestHandler = (req,res,next) => {
  try {
    // EXAMPLE: LOG A WARNING
    const metadata = { resource, severity: "WARNING" };
    const entry = log.entry(metadata,"SOME WARNING MSG");
    await log.write(entry);
    return res.sendStatus(200);
  }
  catch(err) {
    // EXAMPLE: LOG AN ERROR
    const metadata = { resource, severity: "ERROR" };
    const entry = log.entry(metadata,"SOME ERROR MSG");
    await log.write(entry);
    return res.sendStatus(500);
  }
};

您可以看到的log.write(entry)是异步的。因此，从理论上讲，建议您等待它。但是，这里的文档@google-cloud/logging说的是：

文件连结

我对此没有任何问题。在我的真实情况下，即使log.write()失败，它也位于a内try-catch，任何错误都将得到很好的处理。

我的问题是，它与Cloud Run文档有点冲突：

文件连结

Note: If I don't wait for the log.write() call, I'll end the request cycle by responding to the request

And Cloud Run does behave like that. A couple weeks back, I tried to respond immediately to the request and fire some long background job. And the process kind of halted for a while, and I think it restarted once it got another request. Completely unpredictable. And when I ran this test I'm mentioning here, I even had a MIN_INSTANCE=1 set on my cloud run service container. Even that didn't allow my background job to run smoothly. Therefore, I don't think it's fine to leave the process doing background stuff when I've finished handling a request (by doing the "fire and forget" approach).

So, what should I do here?