您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

诊断日志-Azure 内容分发网络Diagnostic logs - Azure Content Delivery Network

使用 Azure 诊断日志,可以查看核心分析并将其保存到一个或多个目标,包括:With Azure diagnostic logs, you can view core analytics and save them into one or more destinations including:

  • Azure 存储帐户Azure Storage account
  • Log Analytics 工作区Log Analytics workspace
  • Azure 事件中心Azure Event Hubs

此功能在所有定价层的 CDN 终结点上提供。This feature is available on CDN endpoints for all pricing tiers.

使用诊断日志可以将基本使用情况指标从 CDN 终结点导出到不同种类的源,以便以自定义方式使用它们。Diagnostics logs allow you to export basic usage metrics from your CDN endpoint to different kinds sources so that you can consume them in a customized way. 您可以执行以下类型的数据导出:You can do the following types of data export:

  • 将数据导出到 Blob 存储、导出为CSV,并在 Excel 中生成图形。Export data to blob storage, export to CSV, and generate graphs in Excel.
  • 将数据导出到事件中心,并关联到其他 Azure 服务的数据。Export data to Event Hubs and correlate with data from other Azure services.
  • 将数据导出到 Azure Monitor 日志,并在自己的 Log Analytics 工作区中查看数据Export data to Azure Monitor logs and view data in your own Log Analytics workspace

需要 Azure CDN 配置文件才能执行以下步骤。An Azure CDN profile is required for the following steps. 继续之前,请参阅 创建 Azure CDN 配置文件和终结点Refer to create an Azure CDN profile and endpoint before you continue.

使用 Azure 门户启用日志记录Enable logging with the Azure portal

按照以下步骤为你的 Azure CDN 终结点启用日志记录:Follow these steps enable logging for your Azure CDN endpoint:

  1. 登录到 Azure 门户Sign in to the Azure portal.

  2. 在 Azure 门户中,导航到 All resources -> 你的 cdn 配置文件 中的所有资源In the Azure portal, navigate to All resources -> your-cdn-profile

  3. 选择要为其启用诊断日志的 CDN 终结点:Select the CDN endpoint for which you want to enable diagnostics logs:

    选择 "CDN 终结点"。

  4. 在 "监视" 部分选择 "诊断日志":Select Diagnostics logs in the Monitoring section:

    选择 "诊断日志"。

使用 Azure 存储启用日志记录Enable logging with Azure Storage

若要使用存储帐户来存储日志,请执行以下步骤:To use a storage account to store the logs, follow these steps:

备注

若要完成这些步骤,需要一个存储帐户。A storage account is required to complete these steps. 有关详细信息,请参阅: 创建 Azure 存储帐户Refer to: Create an Azure Storage account for more information.

  1. 对于 " 诊断设置名称",请输入诊断日志设置的名称。For Diagnostic setting name, enter a name for your diagnostic log settings.

  2. 选择“存档到存储帐户”,然后选择“CoreAnalytics”。Select Archive to a storage account, then select CoreAnalytics.

  3. 对于“保留期(天数)”,请选择保留天数。For Retention (days), choose the number of retention days. 如果保留期为 0 天,则会无限期存储日志。A retention of zero days stores the logs indefinitely.

  4. 选择日志的订阅和存储帐户。Select the subscription and storage account for the logs.

    诊断日志-存储。

  5. 选择“保存”。Select Save.

发送到 Log AnalyticsSend to Log Analytics

若要对日志使用 Log Analytics,请执行以下步骤:To use Log Analytics for the logs, follow these steps:

备注

需要使用 log analytics 工作区才能完成这些步骤。A log analytics workspace is required to complete these steps. 有关详细信息,请参阅: 在 Azure 门户中创建 Log Analytics 工作区Refer to: Create a Log Analytics workspace in the Azure portal for more information.

  1. 对于 " 诊断设置名称",请输入诊断日志设置的名称。For Diagnostic setting name, enter a name for your diagnostic log settings.

  2. 选择 " 发送到 Log Analytics",然后选择 " CoreAnalytics"。Select Send to Log Analytics, then select CoreAnalytics.

  3. 为日志选择 "订阅" 和 "Log Analytics" 工作区。Select the subscription and Log Analytics workspace for the logs.

    诊断日志-Log Analytics。

  4. 选择“保存”。Select Save.

流式传输到事件中心Stream to an event hub

若要将事件中心用于日志,请执行以下步骤:To use an event hub for the logs, follow these steps:

备注

需要使用事件中心才能完成这些步骤。An event hub is required to complete these steps. 有关详细信息,请参阅: 快速入门:使用 Azure 门户创建事件中心Refer to: Quickstart: Create an event hub using Azure portal for more information.

  1. 对于 " 诊断设置名称",请输入诊断日志设置的名称。For Diagnostic setting name, enter a name for your diagnostic log settings.

  2. 选择 " 流式传输到事件中心",然后选择 " CoreAnalytics"。Select Stream to an event hub, then select CoreAnalytics.

  3. 选择日志的订阅和事件中心命名空间。Select the subscription and event hub namespace for the logs.

    诊断日志-事件中心。

  4. 选择“保存”。Select Save.

使用 PowerShell 启用日志记录Enable logging with PowerShell

以下示例演示了如何通过 Azure PowerShell Cmdlet 启用诊断日志。The following example shows how to enable diagnostic logs via the Azure PowerShell Cmdlets.

备注

本文进行了更新,以便使用新的 Azure PowerShell Az 模块。This article has been updated to use the new Azure PowerShell Az module. 你仍然可以使用 AzureRM 模块,至少在 2020 年 12 月之前,它将继续接收 bug 修补程序。You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. 若要详细了解新的 Az 模块和 AzureRM 兼容性,请参阅新 Azure Powershell Az 模块简介To learn more about the new Az module and AzureRM compatibility, see Introducing the new Azure PowerShell Az module. 有关 Az 模块安装说明,请参阅安装 Azure PowerShellFor Az module installation instructions, see Install Azure PowerShell.

在存储帐户中启用诊断日志Enable diagnostic logs in a storage account

  1. 登录到 Azure PowerShell:Sign in to Azure PowerShell:

    Connect-AzAccount 
    
  2. 若要在存储帐户中启用诊断日志,请输入以下命令。To enable Diagnostic Logs in a storage account, enter these commands. 将变量替换为值:Replace the variables with your values:

    $rsg = <your-resource-group-name>
    $cdnprofile = <your-cdn-profile-name>
    $cdnendpoint = <your-cdn-endpoint-name>
    $storageacct = <your-storage-account-name>
    $diagname = <your-diagnostic-setting-name>
    
    $cdn = Get-AzCdnEndpoint -ResourceGroupName $rsg -ProfileName $cdnprofile -EndpointName $cdnendpoint
    
    $storage = Get-AzStorageAccount -ResourceGroupName $rsg -Name $storageacct
    
    Set-AzDiagnosticSetting -Name $diagname -ResourceId $cdn.id -StorageAccountId $storage.id -Enabled $true -Categories CoreAnalytics
    

为 Log Analytics 工作区启用诊断日志Enable diagnostics logs for Log Analytics workspace

  1. 登录到 Azure PowerShell:Sign in to Azure PowerShell:

    Connect-AzAccount 
    
  2. 若要为 Log Analytics 工作区启用诊断日志,请输入以下命令。To enable Diagnostic Logs for a Log Analytics workspace, enter these commands. 将变量替换为值:Replace the variables with your values:

    $rsg = <your-resource-group-name>
    $cdnprofile = <your-cdn-profile-name>
    $cdnendpoint = <your-cdn-endpoint-name>
    $workspacename = <your-log-analytics-workspace-name>
    $diagname = <your-diagnostic-setting-name>
    
    $cdn = Get-AzCdnEndpoint -ResourceGroupName $rsg -ProfileName $cdnprofile -EndpointName $cdnendpoint
    
    $workspace = Get-AzOperationalInsightsWorkspace -ResourceGroupName $rsg -Name $workspacename
    
    Set-AzDiagnosticSetting -Name $diagname -ResourceId $cdn.id -WorkspaceId $workspace.ResourceId -Enabled $true -Categories CoreAnalytics
    

为事件中心命名空间启用诊断日志Enable diagnostics logs for event hub namespace

  1. 登录到 Azure PowerShell:Sign in to Azure PowerShell:

    Connect-AzAccount 
    
  2. 若要为 Log Analytics 工作区启用诊断日志,请输入以下命令。To enable Diagnostic Logs for a Log Analytics workspace, enter these commands. 将变量替换为值:Replace the variables with your values:

    $rsg = <your-resource-group-name>
    $cdnprofile = <your-cdn-profile-name>
    $cdnendpoint = <your-cdn-endpoint-name>
    $eventhubname = <your-event-hub-namespace-name>
    $diagname = <your-diagnostic-setting-name>
    
    $cdn = Get-AzCdnEndpoint -ResourceGroupName $rsg -ProfileName $cdnprofile -EndpointName $cdnendpoint
    
    Set-AzDiagnosticSetting -Name $diagname -ResourceId $cdn.id -EventHubName $eventhubname -Enabled $true -Categories CoreAnalytics
    

从 Azure 存储中使用诊断日志Consuming diagnostics logs from Azure Storage

本部分介绍 Azure 存储帐户中的 CDN 核心分析和组织的架构,并提供用于将日志下载到 CSV 文件的示例代码。This section describes the schema of CDN core analytics, organization in an Azure storage account, and provides sample code to download the logs in a CSV file.

使用 Microsoft Azure 存储资源管理器Using Microsoft Azure Storage Explorer

若要下载该工具,请参阅 Azure 存储资源管理器To download the tool, see Azure Storage Explorer. 下载并安装软件后,请将其配置为使用已配置为 CDN 诊断日志目标的同一 Azure 存储帐户。After downloading and installing the software, configure it to use the same Azure storage account that was configured as a destination to the CDN Diagnostics Logs.

  1. 打开 Microsoft Azure 存储资源管理器Open Microsoft Azure Storage Explorer
  2. 找到存储帐户Locate the storage account
  3. 展开该存储帐户下的“Blob 容器”节点。Expand the Blob Containers node under this storage account.
  4. 选择名为 insights-logs-coreanalytics 的容器。Select the container named insights-logs-coreanalytics.
  5. 结果显示在右窗格中,从第一级开始,类似于 resourceId=Results show up on the right-hand pane, starting with the first level, as resourceId=. 继续选择每个级别,直至找到 PT1H.json 文件。Continue selecting each level until you find the file PT1H.json. 有关路径的说明,请参阅 Blob 路径格式For an explanation of the path, see Blob path format.
  6. 每个 Blob PT1H.json 文件表示特定 CDN 终结点或其自定义域一小时内的分析日志。Each blob PT1H.json file represents the analytics logs for one hour for a specific CDN endpoint or its custom domain.
  7. 有关此 JSON 文件的内容架构,请参阅核心分析日志的“架构”部分。The schema of the contents of this JSON file is described in the section schema of the core analytics logs.

Blob 路径格式Blob path format

核心分析日志每隔一小时生成一次,数据以 JSON 有效负载的形式收集并存储在单个 Azure Blob 中。Core analytics logs are generated every hour and the data is collected and stored inside a single Azure blob as a JSON payload. 存储资源管理器工具将 "/" 解释为目录分隔符,并显示层次结构。Storage explorer tool interprets '/' as a directory separator and shows the hierarchy. 将显示 Azure blob 的路径,如同存在分层结构并表示 blob 名称。The path to the Azure blob appears as if there's a hierarchical structure and represents the blob name. Blob 的名称遵循以下命名约定:The name of the blob follows the following naming convention:

resourceId=/SUBSCRIPTIONS/{Subscription Id}/RESOURCEGROUPS/{Resource Group Name}/PROVIDERS/MICROSOFT.CDN/PROFILES/{Profile Name}/ENDPOINTS/{Endpoint Name}/ y={Year}/m={Month}/d={Day}/h={Hour}/m={Minutes}/PT1H.json

字段说明:Description of fields:

Value 描述Description
订阅 IDSubscription ID Azure 订阅的 ID,采用 GUID 格式。ID of the Azure subscription in Guid format.
资源组名称Resource Group Name CDN 资源所属资源组的名称。Name of the resource group to which the CDN resources belong.
配置文件名称Profile Name CDN 配置文件的名称Name of the CDN Profile
终结点名称Endpoint Name CDN 终结点的名称Name of the CDN Endpoint
年龄Year 年份的四位数表示形式,例如 2017Four-digit representation of the year, for example, 2017
月份Month 月份的两位数表示形式。Two-digit representation of the month number. 01 = 一月 .。。12 = 12 月01=January ... 12=December
Day 月份中日的两位数表示形式Two-digit representation of the day of the month
PT1H.jsonPT1H.json 实际存储分析数据的 JSON 文件Actual JSON file where the analytics data is stored

将核心分析数据导出到 CSV 文件Exporting the core analytics data to a CSV file

为了访问核心分析,我们提供了工具的示例代码。To access core analytics, sample code for a tool is provided. 此工具可将 JSON 文件下载为逗号分隔的平面文件格式,然后可以使用该格式创建图表或其他聚合。This tool allows downloading the JSON files into a flat comma-separated file format, which can be used to create charts or other aggregations.

该工具的使用方式如下:Here's how you can use the tool:

  1. 访问 GitHub 链接: https://github.com/Azure-Samples/azure-cdn-samples/tree/master/CoreAnalytics-ExportToCsvVisit the GitHub link: https://github.com/Azure-Samples/azure-cdn-samples/tree/master/CoreAnalytics-ExportToCsv
  2. 下载代码。Download the code.
  3. 遵照说明进行编译和配置。Follow the instructions to compile and configure.
  4. 运行该工具。Run the tool.
  5. 生成的 CSV 文件以简单的平面层次结构显示分析数据。The resulting CSV file shows the analytics data in a simple flat hierarchy.

日志数据延迟Log data delays

下表介绍 Microsoft 推出的 Azure CDN 标准版Akamai 推出的 Azure CDN 标准版Verizon 推出的 Azure CDN 标准/高级版 的日志数据延迟。The following table shows log data delays for Azure CDN Standard from Microsoft, Azure CDN Standard from Akamai, and Azure CDN Standard/Premium from Verizon.

Microsoft 日志数据延迟Microsoft log data delays Verizon 日志数据延迟Verizon log data delays Akamai 日志数据延迟Akamai log data delays
延迟 1 小时。Delayed by 1 hour. 延迟 1 小时,在终结点传播完成后可能需要长达 2 小时的时间才会开始显示。Delayed by 1 hour and can take up to 2 hours to start appearing after endpoint propagation completion. 延迟 24 小时;如果数据是在 24 小时以前创建的,则最长需要在 2 小时后才会开始显示。Delayed by 24 hours; if it was created more than 24 hours ago, it takes up to 2 hours to start appearing. 如果是最近创建的,则可能需要长达 25 个小时才能开始显示日志。If it was recently created, it can take up to 25 hours for the logs to start appearing.

CDN 核心分析的诊断日志类型Diagnostic log types for CDN core analytics

Microsoft 当前仅提供核心分析日志,其中包含一些显示 HTTP 响应统计信息和出口统计信息的指标(如 CDN POP/边缘中所见)。Microsoft currently offers core analytics logs only, which contain metrics showing HTTP response statistics and egress statistics as seen from the CDN POPs/edges.

核心分析指标详细信息Core analytics metrics details

下表显示了的核心分析日志中可用指标的列表:The following table shows a list of metrics available in the core analytics logs for:

  • 来自 Microsoft 的 Azure CDN 标准版Azure CDN Standard from Microsoft
  • 来自 Akamai 的 Azure CDN 标准版Azure CDN Standard from Akamai
  • Verizon 中的标准/高级 Azure CDNAzure CDN Standard/Premium from Verizon

并非所有提供商提供的所有指标都可用,尽管这种差异很小。Not all metrics are available from all providers, although such differences are minimal. 此表还显示了某提供商的给定指标是否可用。The table also displays whether a given metric is available from a provider. 这些指标仅适用于在其上拥有流量的 CDN 终结点。The metrics are available for only those CDN endpoints that have traffic on them.

指标Metric 描述Description MicrosoftMicrosoft VerizonVerizon AkamaiAkamai
RequestCountTotalRequestCountTotal 在此期间请求命中的总次数。Total number of request hits during this period. Yes Yes Yes
RequestCountHttpStatus2xxRequestCountHttpStatus2xx 导致 2xx HTTP 代码(例如 200 和 202)的所有请求的计数。Count of all requests that resulted in a 2xx HTTP code (for example, 200, 202). Yes Yes Yes
RequestCountHttpStatus3xxRequestCountHttpStatus3xx 导致 3xx HTTP 代码(例如 300 和 302)的所有请求的计数。Count of all requests that resulted in a 3xx HTTP code (for example, 300, 302). Yes Yes Yes
RequestCountHttpStatus4xxRequestCountHttpStatus4xx 导致 4xx HTTP 代码(例如 400 和 404)的所有请求的计数。Count of all requests that resulted in a 4xx HTTP code (for example, 400, 404). Yes Yes Yes
RequestCountHttpStatus5xxRequestCountHttpStatus5xx 导致 5xx HTTP 代码(例如 500 和 504)的所有请求的计数。Count of all requests that resulted in a 5xx HTTP code (for example, 500, 504). Yes Yes Yes
RequestCountHttpStatusOthersRequestCountHttpStatusOthers 所有其他 HTTP 代码的计数(2xx-5xx 除外)。Count of all other HTTP codes (outside of 2xx-5xx). Yes Yes Yes
RequestCountHttpStatus200RequestCountHttpStatus200 导致 200 HTTP 代码响应的所有请求的计数。Count of all requests that resulted in a 200 HTTP code response. Yes No Yes
RequestCountHttpStatus206RequestCountHttpStatus206 导致 206 HTTP 代码响应的所有请求的计数。Count of all requests that resulted in a 206 HTTP code response. Yes No Yes
RequestCountHttpStatus302RequestCountHttpStatus302 导致 302 HTTP 代码响应的所有请求的计数。Count of all requests that resulted in a 302 HTTP code response. Yes No Yes
RequestCountHttpStatus304RequestCountHttpStatus304 导致 304 HTTP 代码响应的所有请求的计数。Count of all requests that resulted in a 304 HTTP code response. Yes No Yes
RequestCountHttpStatus404RequestCountHttpStatus404 导致 404 HTTP 代码响应的所有请求的计数。Count of all requests that resulted in a 404 HTTP code response. Yes No Yes
RequestCountCacheHitRequestCountCacheHit 导致缓存命中的所有请求的计数。Count of all requests that resulted in a Cache hit. 资产已直接从 POP 提供给客户端。The asset was served directly from the POP to the client. Yes Yes No
RequestCountCacheMissRequestCountCacheMiss 导致缓存未命中的所有请求的计数。Count of all requests that resulted in a Cache miss. 缓存未命中意味着在最靠近客户端的 POP 上找不到该资产,并已从源中检索到该资产。A Cache miss means the asset wasn't found on the POP closest to the client, and was retrieved from the origin. Yes Yes No
RequestCountCacheNoCacheRequestCountCacheNoCache 因边缘上的用户配置而无法缓存的资产的所有请求计数。Count of all requests to an asset that are prevented from being cached because of a user configuration on the edge. Yes Yes No
RequestCountCacheUncacheableRequestCountCacheUncacheable 对资产的 Cache-Control 和 Expires 标头禁止缓存的对资产的所有请求计数。Count of all requests to assets that are prevented from being cached by the asset's Cache-Control and Expires headers. 此计数表明它不应在 POP 上缓存或由 HTTP 客户端缓存。This count indicates that it shouldn't be cached on a POP or by the HTTP client. Yes Yes No
RequestCountCacheOthersRequestCountCacheOthers 上述未涵盖的具有缓存状态的所有请求的计数。Count of all requests with cache status not covered by above. No Yes No
EgressTotalEgressTotal 出站数据传输量(按 GB 计)Outbound data transfer in GB Yes Yes Yes
EgressHttpStatus2xxEgressHttpStatus2xx 针对状态代码为 2xx HTTP 的响应的出站数据传输量*(按 GB 计)。Outbound data transfer* for responses with 2xx HTTP status codes in GB. Yes Yes No
EgressHttpStatus3xxEgressHttpStatus3xx 针对状态代码为 3xx HTTP 的响应的出站数据传输量(按 GB 计)。Outbound data transfer for responses with 3xx HTTP status codes in GB. Yes Yes No
EgressHttpStatus4xxEgressHttpStatus4xx 针对状态代码为 4xx HTTP 的响应的出站数据传输量(按 GB 计)。Outbound data transfer for responses with 4xx HTTP status codes in GB. Yes Yes No
EgressHttpStatus5xxEgressHttpStatus5xx 针对状态代码为 5xx HTTP 的响应的出站数据传输量(按 GB 计)。Outbound data transfer for responses with 5xx HTTP status codes in GB. Yes Yes No
EgressHttpStatusOthersEgressHttpStatusOthers 针对带其他 HTTP 状态代码的响应的出站数据传输量(按 GB 计)。Outbound data transfer for responses with other HTTP status codes in GB. Yes Yes No
EgressCacheHitEgressCacheHit 针对直接从 CDN POP/边缘上 CDN 缓存传递的响应的出站数据传输量。Outbound data transfer for responses that were delivered directly from the CDN cache on the CDN POPs/Edges. Yes Yes No
EgressCacheMiss。EgressCacheMiss. 对于在最近的 POP 服务器上找不到的响应的出站数据传输,以及从源服务器检索到的响应。Outbound data transfer for responses that weren't found on the nearest POP server, and retrieved from the origin server. Yes Yes No
EgressCacheNoCacheEgressCacheNoCache 因边缘上的用户配置而无法缓存的资产的出站数据传输。Outbound data transfer for assets that are prevented from being cached because of a user configuration on the edge. Yes Yes No
EgressCacheUncacheableEgressCacheUncacheable 无法通过资产的 Cache-Control 和或 Expires 标头来缓存的资产的出站数据传输。Outbound data transfer for assets that are prevented from being cached by the asset's Cache-Control and, or Expires headers. 指示它不应在 POP 上缓存或由 HTTP 客户端缓存。Indicates that it shouldn't be cached on a POP or by the HTTP client. Yes Yes No
EgressCacheOthersEgressCacheOthers 其他缓存方案的出站数据传输量。Outbound data transfers for other cache scenarios. No Yes No

* 出站数据传输量是指从 CDN POP 服务器传递到客户端的流量。*Outbound data transfer refers to traffic delivered from CDN POP servers to the client.

核心分析日志的架构Schema of the core analytics logs

所有日志以 JSON 格式存储,每个项包含遵循以下架构的字符串字段:All logs are stored in JSON format and each entry has string fields according to the following schema:

    "records": [
        {
            "time": "2017-04-27T01:00:00",
            "resourceId": "<ARM Resource Id of the CDN Endpoint>",
            "operationName": "Microsoft.Cdn/profiles/endpoints/contentDelivery",
            "category": "CoreAnalytics",
            "properties": {
                "DomainName": "<Name of the domain for which the statistics is reported>",
                "RequestCountTotal": integer value,
                "RequestCountHttpStatus2xx": integer value,
                "RequestCountHttpStatus3xx": integer value,
                "RequestCountHttpStatus4xx": integer value,
                "RequestCountHttpStatus5xx": integer value,
                "RequestCountHttpStatusOthers": integer value,
                "RequestCountHttpStatus200": integer value,
                "RequestCountHttpStatus206": integer value,
                "RequestCountHttpStatus302": integer value,
                "RequestCountHttpStatus304": integer value,
                "RequestCountHttpStatus404": integer value,
                "RequestCountCacheHit": integer value,
                "RequestCountCacheMiss": integer value,
                "RequestCountCacheNoCache": integer value,
                "RequestCountCacheUncacheable": integer value,
                "RequestCountCacheOthers": integer value,
                "EgressTotal": double value,
                "EgressHttpStatus2xx": double value,
                "EgressHttpStatus3xx": double value,
                "EgressHttpStatus4xx": double value,
                "EgressHttpStatus5xx": double value,
                "EgressHttpStatusOthers": double value,
                "EgressCacheHit": double value,
                "EgressCacheMiss": double value,
                "EgressCacheNoCache": double value,
                "EgressCacheUncacheable": double value,
                "EgressCacheOthers": double value,
            }
        }

    ]
}

其中,time 表示报告统计信息的小时边界的开始时间。Where time represents the start time of the hour boundary for which the statistics is reported. CDN 提供程序不支持的指标(而不是 double 或 integer 值)会导致 null 值。A metric unsupported by a CDN provider, instead of a double or integer value, results in a null value. 该 null 值表示不存在指标且与 0 值不同。This null value indicates the absence of a metric, and is different from a value of 0. 在终结点上配置每个域的一组指标。One set of these metrics per domain is configured on the endpoint.

示例属性:Example properties:

{
     "DomainName": "manlingakamaitest2.azureedge.net",
     "RequestCountTotal": 480,
     "RequestCountHttpStatus2xx": 480,
     "RequestCountHttpStatus3xx": 0,
     "RequestCountHttpStatus4xx": 0,
     "RequestCountHttpStatus5xx": 0,
     "RequestCountHttpStatusOthers": 0,
     "RequestCountHttpStatus200": 480,
     "RequestCountHttpStatus206": 0,
     "RequestCountHttpStatus302": 0,
     "RequestCountHttpStatus304": 0,
     "RequestCountHttpStatus404": 0,
     "RequestCountCacheHit": null,
     "RequestCountCacheMiss": null,
     "RequestCountCacheNoCache": null,
     "RequestCountCacheUncacheable": null,
     "RequestCountCacheOthers": null,
     "EgressTotal": 0.09,
     "EgressHttpStatus2xx": null,
     "EgressHttpStatus3xx": null,
     "EgressHttpStatus4xx": null,
     "EgressHttpStatus5xx": null,
     "EgressHttpStatusOthers": null,
     "EgressCacheHit": null,
     "EgressCacheMiss": null,
     "EgressCacheNoCache": null,
     "EgressCacheUncacheable": null,
     "EgressCacheOthers": null
}

其他资源Additional resources