Skip to content

Commit 97d92ab

Browse files
authored
Update diagnostic-logs.md
Adding VNet and IP Filtering Diagnostic Logs information for Azure Relay
1 parent 7865024 commit 97d92ab

File tree

1 file changed

+40
-1
lines changed

1 file changed

+40
-1
lines changed

articles/azure-relay/diagnostic-logs.md

Lines changed: 40 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The new settings take effect in about 10 minutes. The logs are displayed in the
4444

4545

4646
## Schema for hybrid connections events
47-
Hybrid connections event log JSON strings include the elements listed in the following table:
47+
Hybrid Connections event log JSON strings include the elements listed in the following table:
4848

4949
| Name | Description |
5050
| ------- | ------- |
@@ -72,6 +72,45 @@ Here's a sample hybrid connections event in JSON format.
7272
}
7373
```
7474

75+
76+
## Schema for VNet/IP Filtering Connection Logs
77+
Hybrid Connections VNet/IP Filtering Connection Logs include elements listed in the following table:
78+
79+
| Name | Description | Supported in Azure Diagnostics | Supported in AZMSVnetConnectionEvents (Resource specific table)
80+
| --- | ----------- |---| ---|
81+
| `SubscriptionId` | Azure subscription ID | Yes | Yes
82+
| `NamespaceName` | Namespace name | Yes | Yes
83+
| `IPAddress` | IP address of a client connecting to the Service Bus service | Yes | Yes
84+
| `AddressIP` | IP address of client connecting to service bus | Yes | Yes
85+
| `TimeGenerated [UTC]`|Time of executed operation (in UTC) | Yes | Yes
86+
| `Action` | Action done by the Service Bus service when evaluating connection requests. Supported actions are **Accept Connection** and **Deny Connection**. | Yes | Yes
87+
| `Reason` | Provides a reason why the action was done | Yes | Yes
88+
| `Count` | Number of occurrences for the given action | Yes | Yes
89+
| `ResourceId` | Azure Resource Manager resource ID. | Yes | Yes
90+
| `Category` | Log Category | Yes | No
91+
| `Provider`|Name of Service emitting the logs e.g., ServiceBus | No | Yes
92+
| `Type` | Type of Logs Emitted | No | Yes
93+
94+
> [!NOTE]
95+
> Virtual network logs are generated only if the namespace allows access from selected networks or from specific IP addresses (IP filter rules).
96+
97+
## Sample VNet and IP Filtering Logs
98+
Here's an example of a virtual network log JSON string:
99+
100+
AzureDiagnostics:
101+
```json
102+
{
103+
"SubscriptionId": "0000000-0000-0000-0000-000000000000",
104+
"NamespaceName": "namespace-name",
105+
"IPAddress": "1.2.3.4",
106+
"Action": "Accept Connection",
107+
"Reason": "IP is accepted by IPAddress filter.",
108+
"Count": 1,
109+
"ResourceId": "/SUBSCRIPTIONS/<AZURE SUBSCRPTION ID>/RESOURCEGROUPS/<RESOURCE GROUP NAME>/PROVIDERS/MICROSOFT.RELAY/NAMESPACES/<RELAY NAMESPACE NAME>",
110+
"Category": "VNetAndIPFilteringLogs"
111+
}
112+
```
113+
75114
## Events and operations captured in diagnostic logs
76115

77116
| Operation | Description |

0 commit comments

Comments
 (0)