Skip to content

Commit 16b4d1d

Browse files
Merge pull request #290997 from jl-ms/patch-23
Update concept-event-logs.md
2 parents c71639a + 7730cc0 commit 16b4d1d

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/virtual-network-manager/concept-event-logs.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,11 +100,11 @@ This category emits one log per connectivity configuration change per virtual ne
100100
| time | Datetime when the event was logged. |
101101
| resourceId | Resource ID of the network manager. |
102102
| location | Location of the virtual network resource. |
103-
| operationName | Operation that resulted in the virtual network being added or removed. Always the Microsoft.Network/networkManagers/connectivityConfigurations/write operation. |
103+
| operationName | Operation that resulted in the virtual network being added or removed. |
104104
| category | Category of this log. Always ConnectivityConfigurationChange. |
105105
| resultType | Indicates successful or failed operation. |
106106
| correlationId | GUID that can help relate or debug logs. |
107-
| level | Always Info. |
107+
| level | Info or Warning. |
108108
| properties | Collection of properties of the log. |
109109

110110
Within the `properties` attribute are several nested attributes:
@@ -115,6 +115,9 @@ Within the `properties` attribute are several nested attributes:
115115
| TargetResourceIds | Resource ID of the virtual network that experienced a change in connectivity configuration application. |
116116
| Message | A static message stating if the connectivity configuration change was successful or unsuccessful. |
117117

118+
> [!NOTE]
119+
> Connectivity configuration allows virtual networks with overlapping IP spaces within the same connected group, but communication to an overlapped IP address is dropped. In addition, when a connected group’s VNet is peered with an external VNet (a VNet not in the connected group) that has overlapping address spaces, these overlapping address spaces become inaccessible within the connected group. Traffic from the peered VNet to the overlapping address spaces is routed to the external VNet, while traffic from other VNets in the connected group to the overlapping address spaces is dropped. Logs will show a "Warning" level, with the `TargetResourceIds` field indicating the IDs of VNets with overlapping address spaces and a `message` indicating that either complete or partial address spaces are inaccessible due to overlapping addresses.
120+
118121
Within the `AppliedConnectivityConfigurations` attribute are several nested attributes:
119122

120123
| AppliedConnectivityConfigurations attributes | Description |

0 commit comments

Comments
 (0)