日志在灵活虚拟机的请求下未嵌套 [英] Logs are Not Nested Under Requests in Flexible VM

查看:95
本文介绍了日志在灵活虚拟机的请求下未嵌套的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个模块运行在App Engine Classic中,另一个模块运行在App Engine Flexible中。查看在App Engine Classic中运行的日志时,日志条目嵌套在每个请求中。



但是,查看在App Engine Flexible中运行的日志时,它们不是嵌套的。每个日志条目似乎都与请求无关。这使得很难确定哪个日志与哪个请求相关联。

是否有可能将App Engine Flexible中的日志嵌套在每个请求下面(因为它们是否与App Engine Classic一起)?



我无法在解释这种差异的文档中找到任何内容。

解决方案

现在,您可以按照以下说明编写与App Engine Standard类似的嵌套应用程序日志: https://cloud.google.com/logging/docs/view/service/appengine-logs#linking_application_logs_and_requests


I have a module running in App Engine Classic and another module running in App Engine Flexible. When viewing logs running in App Engine Classic, the log entries are nested within each request.

However, when viewing logs running in App Engine Flexible, they are not nested. Each log entry appears to be unconnected from the request. This makes it very difficult to determine which log is associated with which request.

Is it possible to get the logs in App Engine Flexible to be nested under each request (as they are with App Engine Classic)?

I cannot find anything in the documentation that explains this discrepancy.

解决方案

You can now write nested application logs that behave similarly to App Engine Standard by following the instructions here: https://cloud.google.com/logging/docs/view/service/appengine-logs#linking_application_logs_and_requests

这篇关于日志在灵活虚拟机的请求下未嵌套的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆