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-fabric/service-fabric-cluster-config-upgrade-windows-server.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,15 +21,15 @@ You can add, update, or remove settings in the `fabricSettings` section under th
21
21
For example, the following JSON adds a new setting *MaxDiskQuotaInMB* to the *Diagnostics* section under `fabricSettings`:
22
22
23
23
```json
24
-
{
25
-
"name": "Diagnostics",
26
-
"parameters": [
27
-
{
28
-
"name": "MaxDiskQuotaInMB",
29
-
"value": "65536"
30
-
}
31
-
]
32
-
}
24
+
{
25
+
"name": "Diagnostics",
26
+
"parameters": [
27
+
{
28
+
"name": "MaxDiskQuotaInMB",
29
+
"value": "65536"
30
+
}
31
+
]
32
+
}
33
33
```
34
34
35
35
After you've modified the settings in your ClusterConfig.json file, [test the cluster configuration](#test-the-cluster-configuration) and then [upgrade the cluster configuration](#upgrade-the-cluster-configuration) to apply the settings to your cluster.
Copy file name to clipboardExpand all lines: articles/service-fabric/service-fabric-diagnostics-event-aggregation-wad.md
+16-15Lines changed: 16 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -202,25 +202,26 @@ Logs from additional channels are also available for collection, here are some o
202
202
203
203
* Operational Channel - Base: Enabled by default, high-level operations performed by Service Fabric and the cluster, including events for a node coming up, a new application being deployed, or an upgrade rollback, etc. For a list of events, refer to [Operational Channel Events](./service-fabric-diagnostics-event-generation-operational.md).
* Operational Channel - Detailed: This includes health reports and load balancing decisions, plus everything in the base operational channel. These events are generated by either the system or your code by using the health or load reporting APIs such as [ReportPartitionHealth](/previous-versions/azure/reference/mt645153(v=azure.100)) or [ReportLoad](/previous-versions/azure/reference/mt161491(v=azure.100)). To view these events in Visual Studio's Diagnostic Event Viewer add "Microsoft-ServiceFabric:4:0x4000000000000008" to the list of ETW providers.
* Data and Messaging Channel - Base: Critical logs and events generated in the messaging (currently only the ReverseProxy) and data path, in addition to detailed operational channel logs. These events are request processing failures and other critical issues in the ReverseProxy, as well as requests processed. **This is our recommendation for comprehensive logging**. To view these events in Visual Studio's Diagnostic Event Viewer, add "Microsoft-ServiceFabric:4:0x4000000000000010" to the list of ETW providers.
* Data & Messaging Channel - Detailed: Verbose channel that contains all the non-critical logs from data and messaging in the cluster and the detailed operational channel. For detailed troubleshooting of all reverse proxy events, refer to the [reverse proxy diagnostics guide](service-fabric-reverse-proxy-diagnostics.md). To view these events in Visual Studio's Diagnostic Event viewer, add "Microsoft-ServiceFabric:4:0x4000000000000020" to the list of ETW providers.
@@ -285,13 +286,13 @@ Update the `EtwEventSourceProviderConfiguration` section in the template.json fi
285
286
For example, if your event source is named My-Eventsource, add the following code to place the events from My-Eventsource into a table named MyDestinationTableName.
286
287
287
288
```json
288
-
{
289
-
"provider": "My-Eventsource",
290
-
"scheduledTransferPeriod": "PT5M",
291
-
"DefaultEvents": {
292
-
"eventDestination": "MyDestinationTableName"
293
-
}
294
-
}
289
+
{
290
+
"provider": "My-Eventsource",
291
+
"scheduledTransferPeriod": "PT5M",
292
+
"DefaultEvents": {
293
+
"eventDestination": "MyDestinationTableName"
294
+
}
295
+
}
295
296
```
296
297
297
298
To collect performance counters or event logs, modify the Resource Manager template by using the examples provided in [Create a Windows virtual machine with monitoring and diagnostics by using an Azure Resource Manager template](../virtual-machines/extensions/diagnostics-template.md?toc=/azure/virtual-machines/windows/toc.json). Then, republish the Resource Manager template.
Copy file name to clipboardExpand all lines: articles/service-fabric/service-fabric-tutorial-standalone-create-service-fabric-cluster.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,13 +39,13 @@ Next, update the three ipAddress lines that occur in the file on lines 8, 15, an
39
39
After updating the nodes, they appear as follows:
40
40
41
41
```json
42
-
{
43
-
"nodeName": "vm0",
44
-
"ipAddress": "172.31.27.1",
45
-
"nodeTypeRef": "NodeType0",
46
-
"faultDomain": "fd:/dc1/r0",
47
-
"upgradeDomain": "UD0"
48
-
}
42
+
{
43
+
"nodeName": "vm0",
44
+
"ipAddress": "172.31.27.1",
45
+
"nodeTypeRef": "NodeType0",
46
+
"faultDomain": "fd:/dc1/r0",
47
+
"upgradeDomain": "UD0"
48
+
}
49
49
```
50
50
51
51
Then you need to update a couple of the properties. On line 34, you need to modify the connection string for the diagnostic store it should look like this `"connectionstring": "C:\\ProgramData\\SF\\DiagnosticsStore"`
Copy file name to clipboardExpand all lines: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-mvss-custom-image.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,13 +90,16 @@ In the scale set resource, add a `dependsOn` clause referring to the custom imag
90
90
In the `imageReference` of the scale set `storageProfile`, instead of specifying the publisher, offer, sku, and version of a platform image, specify the `id` of the `Microsoft.Compute/images` resource:
In this example, use the `resourceId` function to get the resource ID of the image created in the same template. If you have created the managed disk image beforehand, you should provide the ID of that image instead. This ID must be of the form: `/subscriptions/<subscription-id>resourceGroups/<resource-group-name>/providers/Microsoft.Compute/images/<image-name>`.
Copy file name to clipboardExpand all lines: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-mvss-start.md
+58-51Lines changed: 58 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,39 +58,41 @@ Next is the resources section of the template. Here, you define what you actuall
58
58
All resources require `type`, `name`, `apiVersion`, and `location` properties. This example's first resource has type [Microsoft.Network/virtualNetwork](/azure/templates/microsoft.network/virtualnetworks), name `myVnet`, and apiVersion `2018-11-01`. (To find the latest API version for a resource type, see the [Azure Resource Manager template reference](/azure/templates/).)
59
59
60
60
```json
61
-
{
62
-
"type": "Microsoft.Network/virtualNetworks",
63
-
"name": "myVnet",
64
-
"apiVersion": "2018-11-01",
61
+
{
62
+
"type": "Microsoft.Network/virtualNetworks",
63
+
"name": "myVnet",
64
+
"apiVersion": "2018-11-01",
65
+
}
65
66
```
66
67
67
68
## Specify location
68
69
To specify the location for the virtual network, use a [Resource Manager template function](../azure-resource-manager/templates/template-functions.md). This function must be enclosed in quotes and square brackets like this: `"[<template-function>]"`. In this case, use the `resourceGroup` function. It takes in no arguments and returns a JSON object with metadata about the resource group this deployment is being deployed to. The resource group is set by the user at the time of deployment. This value is then indexed into this JSON object with `.location` to get the location from the JSON object.
69
70
70
71
```json
71
-
"location": "[resourceGroup().location]",
72
+
"location": "[resourceGroup().location]",
72
73
```
73
74
74
75
## Specify virtual network properties
75
76
Each Resource Manager resource has its own `properties` section for configurations specific to the resource. In this case, specify that the virtual network should have one subnet using the private IP address range `10.0.0.0/16`. A scale set is always contained within one subnet. It cannot span subnets.
76
77
77
78
```json
78
-
"properties": {
79
-
"addressSpace": {
80
-
"addressPrefixes": [
81
-
"10.0.0.0/16"
82
-
]
83
-
},
84
-
"subnets": [
85
-
{
86
-
"name": "mySubnet",
87
-
"properties": {
88
-
"addressPrefix": "10.0.0.0/16"
89
-
}
90
-
}
91
-
]
92
-
}
93
-
},
79
+
{
80
+
"properties": {
81
+
"addressSpace": {
82
+
"addressPrefixes": [
83
+
"10.0.0.0/16"
84
+
]
85
+
},
86
+
"subnets": [
87
+
{
88
+
"name": "mySubnet",
89
+
"properties": {
90
+
"addressPrefix": "10.0.0.0/16"
91
+
}
92
+
}
93
+
]
94
+
}
95
+
},
94
96
```
95
97
96
98
## Add dependsOn list
@@ -99,50 +101,55 @@ In addition to the required `type`, `name`, `apiVersion`, and `location` propert
99
101
In this case, there is only one element in the list, the virtual network from the previous example. You specify this dependency because the scale set needs the network to exist before creating any VMs. This way, the scale set can give these VMs private IP addresses from the IP address range previously specified in the network properties. The format of each string in the dependsOn list is `<type>/<name>`. Use the same `type` and `name` used previously in the virtual network resource definition.
Scale sets have many properties for customizing the VMs in the scale set. For a full list of these properties, see the [template reference](/azure/templates/microsoft.compute/virtualmachinescalesets). For this tutorial, only a few commonly used properties are set.
113
119
### Supply VM size and capacity
114
120
The scale set needs to know what size of VM to create ("sku name") and how many such VMs to create ("sku capacity"). To see which VM sizes are available, see the [VM Sizes documentation](../virtual-machines/sizes.md).
115
121
116
122
```json
117
-
"sku": {
118
-
"name": "Standard_A1",
119
-
"capacity": 2
120
-
},
123
+
"sku": {
124
+
"name": "Standard_A1",
125
+
"capacity": 2
126
+
},
121
127
```
122
128
123
129
### Choose type of updates
124
130
The scale set also needs to know how to handle updates on the scale set. Currently, there are three options, `Manual`, `Rolling` and `Automatic`. For more information on the differences between the two, see the documentation on [how to upgrade a scale set](./virtual-machine-scale-sets-upgrade-policy.md).
125
131
126
132
```json
127
-
"properties": {
128
-
"upgradePolicy": {
129
-
"mode": "Manual"
130
-
},
133
+
"properties": {
134
+
"upgradePolicy": {
135
+
"mode": "Manual"
136
+
},
137
+
}
131
138
```
132
139
133
140
### Choose VM operating system
134
141
The scale set needs to know what operating system to put on the VMs. Here, create the VMs with a fully patched Ubuntu 16.04-LTS image.
135
142
136
143
```json
137
-
"virtualMachineProfile": {
138
-
"storageProfile": {
139
-
"imageReference": {
140
-
"publisher": "Canonical",
141
-
"offer": "UbuntuServer",
142
-
"sku": "16.04-LTS",
143
-
"version": "latest"
144
-
}
145
-
},
144
+
"virtualMachineProfile": {
145
+
"storageProfile": {
146
+
"imageReference": {
147
+
"publisher": "Canonical",
148
+
"offer": "UbuntuServer",
149
+
"sku": "16.04-LTS",
150
+
"version": "latest"
151
+
}
152
+
},
146
153
```
147
154
148
155
### Specify computerNamePrefix
@@ -151,11 +158,11 @@ The scale set deploys multiple VMs. Instead of specifying each VM name, specify
151
158
In the following snippet, use the parameters from before to set the administrator username and password for all VMs in the scale set. This process uses the `parameters` template function. This function takes in a string that specifies which parameter to refer to and outputs the value for that parameter.
0 commit comments