AppEngine Cloud Trace是否需要AppStats？ [英] Does AppEngine Cloud Trace require AppStats?

问题描述

Google的AppEngine已升级其开发者控制台，并且包含名为 Cloud Trace 的监控工具。这是 AppStats 分析工具的改进版吗？如果是这样，我可以删除以前需要的配置文件，如 appengine_config.py 和 app.yaml
$ p $ builtins：
- appstats：on
pre


解决方案

Cloud Trace处于测试阶段，意思是它不包含在任何SLA或弃用策略中，不兼容的变化，而AppStats是App Engine支持的组件。

对我而言，这意味着您可能不应该依赖生产应用程序中的Cloud Trace，但是在开发版本中试验它是一个很好的主意 - 如果你使用了大量的RPC跟踪/统计数据（这是保持你的应用程序处于良好状态的一种很好的方式 - ），这可能是值得的，在它自己的和上使用Cloud Trace，同时使用它和AppStats加倍。

通过这种方式，您将了解是否在当前公测状态，Cloud Trace提供了所有与调整应用程序对RPC使用相关的信息，以及也是否让AppStats在Cloud Trace的功能中产生任何更改（根据文档，它不应该[*]，但是，测试版在您的应用中（与您最为相关：< - strong>： - ）是指测试版:-) 。

[*]，所以要明确回答Q我可以删除以前需要的配置文件：理论上的答案是是！在实践中，它是测试版，在开发过程中尝试它，生产，版本，并查看它是否中断 - 对于大多数测试中的任何新功能： - ）

使用这两种方法可以比较和对比他们提供的测量结果，检查是否存在可能影响您使用所述测量结果的任何系统或随机差异（同样，不应该有，但是，等等。 - ）。

由于AppStats 是受支持的组件，因此它受制于通常的弃用策略，因此它将成为在官方宣布弃用后至少一年的时间内（如果发布此类声明），因此您现在确实没有必要考虑将制作应用程序迁移到目前的时间。

Google's AppEngine has upgraded their Developer's Console and it includes a monitoring tool called Cloud Trace. Is this an improved version of the AppStats profiling tool? If so, can I remove the configuration files that were previously required, like appengine_config.py and the console path in app.yaml?

builtins:
- appstats: on

解决方案

Cloud Trace is in beta, meaning "it's not covered by any SLA or deprecation policy and may be subject to backward-incompatible changes", while AppStats is a supported component of App Engine.

The implication, to me, is that you probably should not yet depend on Cloud Trace in production applications, but that it's an excellent idea to experiment with it in development versions -- if you use a lot of RPC traces/stats (a great way to keep your apps in fine shape!-), it's probably worth your while to experiment, both with using Cloud Trace on its own and with "doubling up" with both it and AppStats.

This way you will learn whether, in its current beta state, Cloud Trace supplies all the information you find relevant to tuning your apps' use of RPCs, as well as whether also having AppStats produces any change in Cloud Trace's functionality (per the docs, it shouldn't [*], but, beta does mean beta:-) in your apps (which is the most relevant to you:-).

[*] so to explicitly answer the Q "can I remove the configuration files that were previously required": the answer in theory is "yes!"; in practice, "it's beta, do try it in a development, not production, version, and see if it breaks" -- as for most any new feature in beta:-)

Having both on lets you compare and contrast the measurements they offer, checking if there's any systematic or random difference that could affect your use of said measurements (again, there shouldn't be, but, etc, etc:-).

Since AppStats is a supported component, it is subject to the usual deprecation policy, and thus it will be around for a minimum of one year after it's officially announced as deprecated (if such an announcement ever happens), so there is really no urgency for you to consider migrating production apps off it at this time.

这篇关于AppEngine Cloud Trace是否需要AppStats？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！