You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- No table(s) at https://learn.microsoft.com/azure/azure-monitor/reference/tables/tables-resourcetype. -->
38
39
39
-
<!-- Find the table(s) for your service at https://learn.microsoft.com/azure/azure-monitor/reference/tables/tables-resourcetype. These files are auto generated from the REST API. -->
40
+
Azure Notification Hubs supports activity and operational logs, which capture management operations that are performed on the Notification Hubs namespace. All logs are stored in JavaScript Object Notation (JSON) format in the following two locations:
-**AzureActivity**: Displays logs from operations and actions that are conducted against the namespace in the Azure portal or through Azure Resource Manager template deployments.
43
+
-**AzureDiagnostics**: Displays logs from operations and actions that are conducted against the namespace by using the API, or through management clients on the language SDK.
44
+
45
+
Diagnostic log JSON strings include the elements listed in the following table:
46
+
47
+
| Name | Description |
48
+
| ------- | ------- |
49
+
| time | UTC timestamp of the log |
50
+
| resourceId | Relative path to the Azure resource |
51
+
| operationName | Name of the management operation |
Operational logs capture all management operations that are performed on the Azure Notification Hubs namespace. Data operations aren't captured, because of the high volume of data operations that are conducted on notification hubs. The following management operations are captured in operational logs:
For the available resource log categories, their associated Log Analytics tables, and the logs schemas for Notification Hubs, see [Notification Hubs monitoring data reference](monitor-notification-hubs-reference.md#resource-logs).
28
+
Azure Notification Hubs supports activity and operational logs, which capture management operations that are performed on the Notification Hubs namespace.
29
+
30
+
- For details about where the logs are stored, the logs schema, and how to enable operational logs, see [Notification Hubs diagnostics logs](notification-hubs-diagnostic-logs.md).
31
+
32
+
- For the available resource log categories, associated Log Analytics tables, and the management operations captured in operational logs, see [Notification Hubs monitoring data reference](monitor-notification-hubs-reference.md#resource-logs).
Copy file name to clipboardExpand all lines: articles/notification-hubs/notification-hubs-diagnostic-logs.md
+8-30Lines changed: 8 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ For calls originating from the Azure portal the `identity` field is empty. The l
61
61
}
62
62
```
63
63
64
-
For calls made through Azure Resource Manager the `identity` field will contain the username of the logged in user.
64
+
For calls made through Azure Resource Manager the `identity` field contains the username of the logged in user.
65
65
66
66
```json
67
67
{
@@ -70,7 +70,7 @@ For calls made through Azure Resource Manager the `identity` field will contain
70
70
}
71
71
```
72
72
73
-
For calls to the Notification Hubs REST API the `identity` field will contain the name of the access policy used to generate the SharedAccessSignature token.
73
+
For calls to the Notification Hubs REST API the `identity` field contains the name of the access policy used to generate the SharedAccessSignature token.
74
74
75
75
```json
76
76
{
@@ -81,33 +81,11 @@ For calls to the Notification Hubs REST API the `identity` field will contain th
81
81
82
82
## Events and operations captured in operational logs
83
83
84
-
Operational logs capture all management operations that are performed on the Azure Notification Hubs namespace. Data operations are not captured, because of the high volume of data operations that are conducted on Azure Notification Hubs.
85
-
86
-
The following management operations are captured in operational logs:
87
-
88
-
| Scope | Operation Name | Operation Description |
89
-
| :-- | :-- | :-- |
90
-
| Namespace | Microsoft.NotificationHubs/Namespaces/authorizationRules/action | List Authorization Rules |
Operational logs capture all management operations that are performed on the Azure Notification Hubs namespace. Data operations aren't captured, because of the high volume of data operations that are conducted on notification hubs.
85
+
86
+
For a list of the management operations that are captured in operational logs, see [Activity log](monitor-notification-hubs-reference.md#activity-log).
87
+
88
+
### Enable operational logs
111
89
112
90
Operational logs are disabled by default. To enable logs, do the following:
113
91
@@ -138,7 +116,7 @@ Operational logs are disabled by default. To enable logs, do the following:
138
116
139
117
The new settings take effect in about 10 minutes. The logs are displayed in the configured archival target, in the **Diagnostics logs** pane.
140
118
141
-
## Next steps
119
+
## Related content
142
120
143
121
To learn more about configuring diagnostics settings, see:
144
122
*[Overview of Azure diagnostics logs](../azure-monitor/essentials/platform-logs-overview.md).
0 commit comments