Merge pull request #4 from amymzhou/amyzhou-mcc

Amyzhou mcc
This commit is contained in:
Amy Zhou 2022-09-14 14:06:40 -07:00 committed by GitHub
commit e9086f050f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 1 deletions

View File

@ -73,6 +73,8 @@
href: mcc-isp-vm-performance.md href: mcc-isp-vm-performance.md
- name: Support and troubleshooting - name: Support and troubleshooting
href: mcc-isp-support.md href: mcc-isp-support.md
- name: Version History
href: mcc-version-history.md
- name: MCC for ISPs (Private Preview) - name: MCC for ISPs (Private Preview)
href: mcc-isp.md href: mcc-isp.md
- name: Content endpoints for Delivery Optimization and Microsoft Connected Cache - name: Content endpoints for Delivery Optimization and Microsoft Connected Cache

View File

@ -3,6 +3,14 @@
## Metrics ## Metrics
Within Azure portal, there are a number of metrics that are available to monitor cache node health and performance. Within Azure portal, there are a number of metrics that are available to monitor cache node health and performance.
### Monitoring your metrics
To view the metrics associated with your cache nodes, navigate to the Overview >> Monitoring tab within Azure portal.
:::image type="content" source="images/mcc-isp-metrics.png" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab":::
You can choose to monitor the health and performance of all cache nodes or one by one by using the dropdown menu. The Egress bits per second graph shows your inbound and outbound traffic of your cache nodes over time. You can change the time range (1 hour, 12 hours, 1 day, 7 days, 14 days, and 30 days) by selecting the time range of choice on the top bar.
If you are unable to view metrics for your cache node, it may be that your cache node is unhealthy, inactive, or hasn't been fully configured.
### Available Metrics ### Available Metrics