แก้ไข

แชร์ผ่าน


Access Peering Service connection telemetry

Connection telemetry provides insights collected for the connectivity between the customer's location and the Microsoft network.

In this article, you learn how to access your Peering Service connection telemetry to view the latency report and prefix states for the Peering Service connection.

Prerequisites

View the latency report

To view the latency report for a specific Peering Service connection, follow these steps.

  1. In the search box at the top of the portal, enter Peering Service. Select Peering Services in the search results.

    Screenshot shows how to search for Peering Service in the Azure portal.

  2. Select the Peering Service connection that you want to view its latency report.

    Screenshot shows the selected Peering Service in the Azure portal.

  3. Under Settings, select Prefixes to see the prefixes associated with the Peering Service connection.

    Screenshot shows the prefixes associated with the Peering Service connection in the Azure portal.

  4. Select the prefix that you want to view its latency report. From Show data for last, you can see the prefix latency for the last 6 hours, 12 hours, 1 day, 7 days, or 30 days.

    Screenshot shows the prefix latency in the Azure portal.

    Note

    Prefix latency data for prefixes smaller than /24 is approximated at /24. This is because we can view the client IP addresses on the measurements only with a resolution of /24 or higher due to compliance reasons.

View prefix state report

To view events for a specific prefix, select the prefix name and select Prefix events under Diagnostic. The events that are captured are listed.

Screenshot shows the prefix events in the Azure portal.

Some of the possible events that are captured in the Prefix events list are shown in the following table.

Event type Event impact Details
PrefixAnnouncementEvent Information Prefix announcement was received.
PrefixWithdrawalEvent Warning Prefix withdrawal was received.
PrefixBackupRouteAnnouncementEvent Information Prefix backup route announcement was received.
PrefixBackupRouteWithdrawalEvent Warning Prefix backup route withdrawal was received.
PrefixActivePath Information Current prefix active route.
PrefixBackupPath Information Current prefix backup route.
PrefixOriginAsChangeEvent Critical Exact prefix received with different origin autonomous system number (for active route).
PrefixBackupRouteOriginAsChangeEvent Error Prefix received with different origin autonomous system number (for backup route).

Next steps