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
Copy file name to clipboardExpand all lines: articles/service-bus-messaging/monitor-service-bus-reference.md
+48-48Lines changed: 48 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,7 +117,7 @@ Operational log entries include elements listed in the following table:
117
117
|`Status`| Operation status | Yes | Yes|
118
118
|`Caller`| Caller of operation (the Azure portal or management client) | Yes | Yes|
119
119
|`Provider`|Name of Service emitting the logs e.g., ServiceBus | No | Yes|
120
-
|`Type`| Type of logs emitted | No | Yes|
120
+
|`Type`| Type of logs emitted | No | Yes|
121
121
|`Category`| Log Category | Yes | No|
122
122
123
123
Here's an example of an operational log JSON string:
@@ -183,20 +183,20 @@ The following management operations are captured in operational logs:
183
183
### Virtual network and IP filtering logs
184
184
Service Bus virtual network (VNet) connection event JSON includes elements listed in the following table:
185
185
186
-
| Name | Description | Supported in Azure Diagnostics | Supported in AZMSVnetConnectionEvents (Resource specific table)
187
-
| --- | ----------- |---| ---|
188
-
| `SubscriptionId` | Azure subscription ID | Yes | Yes
189
-
| `NamespaceName` | Namespace name | Yes | Yes
190
-
| `IPAddress` | IP address of a client connecting to the Service Bus service | Yes | Yes
191
-
| `AddressIP` | IP address of client connecting to service bus | Yes | Yes
192
-
| `TimeGenerated [UTC]`|Time of executed operation (in UTC) | Yes | Yes
193
-
| `Action` | Action done by the Service Bus service when evaluating connection requests. Supported actions are **Accept Connection** and **Deny Connection**. | Yes | Yes
194
-
| `Reason` | Provides a reason why the action was done | Yes | Yes
195
-
| `Count` | Number of occurrences for the given action | Yes | Yes
| `Provider`|Name of Service emitting the logs e.g., ServiceBus | No | Yes
199
-
| `Type` | Type of Logs Emitted | No | Yes
186
+
| Name | Description | Supported in Azure Diagnostics | Supported in AZMSVnetConnectionEvents (Resource specific table) |
187
+
| --- | ----------- |---| ---|
188
+
|`SubscriptionId`| Azure subscription ID | Yes | Yes|
189
+
|`NamespaceName`| Namespace name | Yes | Yes|
190
+
|`IPAddress`| IP address of a client connecting to the Service Bus service | Yes | Yes |
191
+
|`AddressIP`| IP address of client connecting to service bus | Yes | Yes|
192
+
|`TimeGenerated [UTC]`|Time of executed operation (in UTC) | Yes | Yes |
193
+
|`Action`| Action done by the Service Bus service when evaluating connection requests. Supported actions are **Accept Connection** and **Deny Connection**. | Yes | Yes |
194
+
|`Reason`| Provides a reason why the action was done | Yes | Yes|
195
+
|`Count`| Number of occurrences for the given action | Yes | Yes|
Number of servers that can be profiled per running instance of the Azure Site Recovery Deployment Planner |Single (VMs belonging to one vCenter Server or one ESXi server can be profiled at a time)|Multiple (VMs across multiple hosts or host clusters can be profile at a time)| NA |Multiple (VMs across multiple hosts or host clusters can be profile at a time)| NA
70
+
|**Categories**|**VMware to Azure**|**Hyper-V to Azure**|**Azure to Azure**|**Hyper-V to secondary site**|**VMware to secondary site**|
71
+
|--|--|--|--|--|--|
72
+
|Supported scenarios |Yes|Yes|No|Yes*|No|
73
+
|Supported Version | vCenter 6.7, 6.5, 6.0 or 5.5| Windows Server 2016, Windows Server 2012 R2 | NA |Windows Server 2016, Windows Server 2012 R2|NA|
|Number of servers that can be profiled per running instance of the Azure Site Recovery Deployment Planner |Single (VMs belonging to one vCenter Server or one ESXi server can be profiled at a time)|Multiple (VMs across multiple hosts or host clusters can be profile at a time)| NA |Multiple (VMs across multiple hosts or host clusters can be profile at a time)| NA|
76
76
77
77
*The tool is primarily for the Hyper-V to Azure disaster recovery scenario. For Hyper-V to secondary site disaster recovery, it can be used only to understand source side recommendations like required network bandwidth, required free storage space on each of the source Hyper-V servers, and initial replication batching numbers and batch definitions. Ignore the Azure recommendations and costs from the report. Also, the Get Throughput operation is not applicable for the Hyper-V to secondary site disaster recovery scenario.
78
78
@@ -81,10 +81,9 @@ The tool has three main phases for Hyper-V: get VM list, profiling, and report g
81
81
82
82
| Server requirement | Description |
83
83
|---|---|
84
-
|Get VM list, profiling, and throughput measurement |<ul><li>Operating system: Microsoft Windows Server 2016 or Microsoft Windows Server 2012 R2 </li><li>Machine configuration: 8 vCPUs, 16 GB RAM, 300 GB HDD</li><li>[Microsoft .NET Framework 4.5](https://aka.ms/dotnet-framework-45)</li><li>[Microsoft Visual C++ Redistributable for Visual Studio 2012](https://aka.ms/vcplusplus-redistributable)</li><li>Internet access to Azure (*.blob.core.windows.net) from this server, port 443<br>[This is optional. You can choose to provide the available bandwidth during Report Generation manually.]</li><li>Azure storage account</li><li>Administrator access on the server</li><li>Minimum 100 GB of free disk space (assuming 1000 VMs with an average of three disks each, profiled for 30 days)</li><li>The VM from where you are running the Azure Site Recovery deployment planner tool must be added to TrustedHosts list of all the Hyper-V servers.</li><li>All Hyper-V servers to be profiled must be added to TrustedHosts list of the client VM from where the tool is being run. [Learn more to add servers into TrustedHosts list](#steps-to-add-servers-into-trustedhosts-list). </li><li> The tool should be run from Administrative privileges from PowerShell or command-line console on the client</ul></ul>|
84
+
|Get VM list, profiling, and throughput measurement |<ul><li>Operating system: Microsoft Windows Server 2016 or Microsoft Windows Server 2012 R2 </li><li>Machine configuration: 8 vCPUs, 16 GB RAM, 300 GB HDD</li><li>[Microsoft .NET Framework 4.5](https://aka.ms/dotnet-framework-45)</li><li>[Microsoft Visual C++ Redistributable for Visual Studio 2012](https://aka.ms/vcplusplus-redistributable)</li><li>Internet access to Azure (`*.blob.core.windows.net`) from this server, port 443<br>[This is optional. You can choose to provide the available bandwidth during Report Generation manually.]</li><li>Azure storage account</li><li>Administrator access on the server</li><li>Minimum 100 GB of free disk space (assuming 1000 VMs with an average of three disks each, profiled for 30 days)</li><li>The VM from where you are running the Azure Site Recovery deployment planner tool must be added to TrustedHosts list of all the Hyper-V servers.</li><li>All Hyper-V servers to be profiled must be added to TrustedHosts list of the client VM from where the tool is being run. [Learn more to add servers into TrustedHosts list](#steps-to-add-servers-into-trustedhosts-list). </li><li> The tool should be run from Administrative privileges from PowerShell or command-line console on the client</ul></ul>|
85
85
| Report generation | A Windows PC or Windows Server with Microsoft Excel 2013 or later |
86
-
| User permissions | Administrator account to access Hyper-V cluster/Hyper-V host during get VM list and profiling operations.<br>All the hosts that need to be profiled should have a domain administrator account with the same credentials i.e. user name and password
87
-
|
86
+
| User permissions | Administrator account to access Hyper-V cluster/Hyper-V host during get VM list and profiling operations.<br>All the hosts that need to be profiled should have a domain administrator account with the same credentials, that is, user name and password |
88
87
89
88
## Steps to add servers into TrustedHosts List
90
89
1. The VM from where the tool is to be deployed should have all the hosts to be profiled in its TrustedHosts list. To add the client into Trustedhosts list run the following command from an elevated PowerShell on the VM. The VM can be a Windows Server 2012 R2 or Windows Server 2016.
0 commit comments