不要Azure诊断中的Azure升级插槽运行? [英] Do Azure Diagnostics run in Azure staging slot?

查看:221
本文介绍了不要Azure诊断中的Azure升级插槽运行?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在收集Azure的诊断数据,并分期插槽也发送诊断数据到WadPerformanceCounters表?

When collecting Azure diagnostic data, does the staging slot also send diagnostic data to the WadPerformanceCounters Table?

如果是这样,我怎么能关闭这个功能?或者,我怎么能读诊断时分期/生产区分。

If so, how can I turn this off? Or how can I differentiate between staging/production when reading the diagnostics.

我不希望显示我们网站的数据假设它的所有的生产,而实际上它的一部分是分期插槽。

I don't want to display data about our website assuming it's all production when in fact part of it is the staging slot.

推荐答案

是 - Windows Azure的诊断在生产和分期插槽运行。这两个插槽之间的唯一真正的区别是DNS名称。

Yes - Windows Azure diagnostics runs in the Production and Staging slots. The only real difference between these two slots is the DNS name.

至于使诊断,有一个在 HTTP一个很好的起点:// msdn.microsoft.com/en-us/library/gg433048.aspx 。这提供链接到Windows Azure上的诊断提供了大量的信息。

As for enabling diagnostics, there is a good starting point at http://msdn.microsoft.com/en-us/library/gg433048.aspx. This provides links to a lot of info on Windows Azure diagnostics.

我不相信这是在诊断表中的数据的一种方式(WadPerformanceCountersTable,例如)生产和分期插槽区分。你也许能够过滤基于该RowKey值,我相信包含deploymentID,这将是生产和分期不同。

I don't believe there is a way in the diagnostics table data (WadPerformanceCountersTable, for example) to distinguish between Production and Staging slots. You might be able to filter based off the RowKey value, which I believe contains the deploymentID and that would be different between Production and Staging.

您也可以使用不同的存储账户生产和分期插槽。这将会是,可以在运行时完成.cscfg的相当快速更新。

You could also use a different storage account for Production and Staging slots. It'd be a fairly quick update of the .cscfg that could be done at run time.

这篇关于不要Azure诊断中的Azure升级插槽运行?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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