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/azure-monitor/alerts/alerts-log.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ You can also [create log alert rules using Azure Resource Manager templates](../
37
37
1. Write a query that will find the log events for which you want to create an alert. You can use the [alert query examples article](../logs/queries.md) to understand what you can discover or [get started on writing your own query](../logs/log-analytics-tutorial.md). Also, [learn how to create optimized alert queries](alerts-log-query.md).
38
38
1. From the top command bar, Select **+ New Alert rule**.
39
39
40
-
:::image type="content" source="media/alerts-log/alerts-create-new-alert-rule.png" alt-text="Create new alert rule.":::
40
+
:::image type="content" source="media/alerts-log/alerts-create-new-alert-rule.png" alt-text="Create new alert rule." lightbox="media/alerts-log/alerts-create-new-alert-rule-expanded.png":::
41
41
42
42
1. The **Condition** tab opens, populated with your log query.
Copy file name to clipboardExpand all lines: articles/azure-monitor/alerts/itsmc-troubleshoot-overview.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
@@ -102,13 +102,13 @@ The following sections identify common symptoms, possible causes, and resolution
102
102
*[Sync the connector](itsmc-resync-servicenow.md).
103
103
* Check the [dashboard](itsmc-dashboard.md) and review the errors in the section for connector status. Then review the [common errors and their resolutions](itsmc-dashboard-errors.md)
104
104
105
-
### Configuration Item is blank in incidents received from ServiceNow
105
+
### In the incidents received from ServiceNow, the configuration item is blank
106
106
**Cause**: There can be several reasons for this:
107
-
*Only Log alerts supports the configuration item but the alert is another type of alert
108
-
*To contain the configuration item, the search results must include the **Computer** or **Resource** column
109
-
* The values in the configuration item field do not match an entry in the CMDB
107
+
*The alert is not a log alert. Configuration items are only supported by log alerts.
108
+
*The search results do not include the **Computer** or **Resource** column.
109
+
* The values in the configuration item field do not match an entry in the CMDB.
110
110
111
111
**Resolution**:
112
-
* Check whether it is log alert - if not configuration item not supported
113
-
*Check whether search results have column Computer or Resource -if not it should be added to the query
114
-
* Check whether values in the columns Computer/Resource are identical to the values in CMDB- if nota new entry should be added to the CMDB
112
+
* Check if the alert is a log alert. If it isn't a log alert, configuration items are not supported.
113
+
*If the search results do not have a Computer or Resource column, add them to the query.
114
+
* Check that the values in the Computer and Resource columns are identical to the values in the CMDB. If they are not, add a new entry to the CMDB with the matching values.
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-nat-gateway.md
+47-78Lines changed: 47 additions & 78 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.topic: conceptual
6
6
ms.service: container-instances
7
7
services: container-instances
8
8
ms.author: macolso
9
-
ms.date: 02/28/2022
9
+
ms.date: 05/03/2022
10
10
---
11
11
12
12
# Configure a NAT gateway for static IP address for outbound traffic from a container group
@@ -15,131 +15,100 @@ Setting up a [container group](container-instances-container-groups.md) with an
15
15
16
16
This article provides steps to configure a container group in a [virtual network](container-instances-virtual-network-concepts.md) integrated with a [Network Address Translation (NAT) gateway](../virtual-network/nat-gateway/nat-overview.md). By configuring a NAT gateway to SNAT a subnet address range delegated to Azure Container Instances (ACI), you can identify outbound traffic from your container groups. The container group egress traffic will use the public IP address of the NAT gateway. A single NAT gateway can be used by multiple container groups deployed in the virtual network's subnet delegated to ACI.
17
17
18
-
In this article you use the Azure CLI to create the resources for this scenario:
18
+
In this article, you use the Azure CLI to create the resources for this scenario:
19
19
20
-
* Container groups deployed on a delegated subnet [in the virtual network](container-instances-vnet.md)
20
+
* Container groups deployed on a delegated subnet [in the virtual network](container-instances-vnet.md)
21
21
* A NAT gateway deployed in the network with a static public IP address
22
22
23
23
You then validate egress from example container groups through the NAT gateway.
24
24
25
25
> [!NOTE]
26
-
> The ACI service recommends integrating with a NAT gateway for containerized workoads that have static egress but not static ingress requirements. For ACI architecture that supports both static ingress and egress, please see the following tutorial: [Use Azure Firewall for ingress and egress](container-instances-egress-ip-address.md).
27
-
## Before you begin
28
-
You must satisfy the following requirements to complete this tutorial:
26
+
> The ACI service recommends integrating with a NAT gateway for containerized workloads that have static egress but not static ingress requirements. For ACI architecture that supports both static ingress and egress, please see the following tutorial: [Use Azure Firewall for ingress and egress](container-instances-egress-ip-address.md).
29
27
30
-
**Azure CLI**: You must have Azure CLI version installed on your local computer. If you need to install or upgrade, see [Install the Azure CLI][azure-cli-install]
> To download the complete script, go to [full script](https://github.com/Azure-Samples/azure-cli-samples/blob/master/container-instances/nat-gateway.sh).
36
+
37
+
## Get started
38
+
39
+
This tutorial makes use of a randomized variable. If you are using an existing resource group, modify the value of this variable appropriately.
**Azure resource group**: If you don't have an Azure resource group already, create a resource group with the [az group create][az-group-create] command. Modify the location value as appropriate.
**Azure resource group**: If you don't have an Azure resource group already, create a resource group with the [az group create][az-group-create] command. Below is an example.
33
-
```azurecli
34
-
az group create --name myResourceGroup --location eastus
35
-
```
36
47
## Deploy ACI in a virtual network
37
48
38
-
In a typical case, you might already have an Azure virtual network in which to deploy a container group. For demonstration purposes, the following commands create a virtual network and subnet when the container group is created. The subnet is delegated to Azure Container Instances.
49
+
In a typical case, you might already have an Azure virtual network in which to deploy a container group. For demonstration purposes, the following commands create a virtual network and subnet when the container group is created. The subnet is delegated to Azure Container Instances.
39
50
40
51
The container group runs a small web app from the `aci-helloworld` image. As shown in other articles in the documentation, this image packages a small web app written in Node.js that serves a static HTML page.
41
52
42
-
> [!TIP]
43
-
> To simplify the following command examples, use an environment variable for the resource group's name:
44
-
> ```console
45
-
> export RESOURCE_GROUP_NAME=myResourceGroup
46
-
> ```
47
-
> This tutorial will make use of the environment variable going forward.
48
53
Create the container group with the [az container create][az-container-create] command:
> Adjust the value of `--subnet address-prefix` for the IP address space you need in your subnet. The smallest supported subnet is /29, which provides eight IP addresses. Some >IP addresses are reserved for use by Azure, which you can read more about [here](../virtual-network/ip-services/private-ip-addresses.md).
58
+
> Adjust the value of `--subnet address-prefix` for the IP address space you need in your subnet. The smallest supported subnet is /29, which provides eight IP addresses. Some >IP addresses are reserved for use by Azure, which you can read more about [here](../virtual-network/ip-services/private-ip-addresses.md).
59
+
63
60
## Create a public IP address
64
61
65
62
In the following sections, use the Azure CLI to deploy an Azure NAT gateway in the virtual network. For background, see [Quickstart: Create a NAT gateway using Azure CLI](../virtual-network/nat-gateway/quickstart-create-nat-gateway-cli.md).
66
63
67
-
First, use the [az network vnet public-ip create][az-network-public-ip-create] to create a public IP address for the NAT gateway. This will be used to access the Internet. You will receive a warning about an upcoming breaking change where Standard SKU IP addresses will be availability zone aware by default. You can learn more about the use of availability zones and public IP addresses [here](../virtual-network/ip-services/virtual-network-network-interface-addresses.md).
64
+
First, use the [az network vnet public-ip create][az-network-public-ip-create] to create a public IP address for the NAT gateway. This will be used to access the Internet. You will receive a warning about an upcoming breaking change where Standard SKU IP addresses will be availability zone aware by default. You can learn more about the use of availability zones and public IP addresses [here](../virtual-network/ip-services/virtual-network-network-interface-addresses.md).
Use the following [az network nat gateway create][az-network-nat-gateway-create] to create a NAT gateway that uses the public IP you created in the previous step.
We'll configure the source subnet **aci-subnet** to use a specific NAT gateway resource **myNATgateway** with [az network vnet subnet update][az-network-vnet-subnet-update]. This command will activate the NAT service on the specified subnet.
80
+
We'll configure the source subnet **aci-subnet** to use a specific NAT gateway resource **myNATgateway** with [az network vnet subnet update][az-network-vnet-subnet-update]. This command will activate the NAT service on the specified subnet.
Test inbound access to the *appcontainer* running in the virtual network by browsing to the firewall's public IP address. Previously, you stored the public IP address in variable $NG_PUBLIC_IP
86
+
Test inbound access to the `appcontainer` running in the virtual network by browsing to the firewall's public IP address. Previously, you stored the public IP address in variable $NG_PUBLIC_IP
112
87
113
88
Deploy the following sample container into the virtual network. When it runs, it sends a single HTTP request to `http://checkip.dyndns.org`, which displays the IP address of the sender (the egress IP address). If the application rule on the firewall is configured properly, the firewall's public IP address is returned.
When no longer needed, you can use [az group delete](/cli/azure/group) to remove the resource group and all related resources as follows. The `--no-wait` parameter returns control to the prompt without waiting for the operation to complete. The `--yes` parameter confirms that you wish to delete the resources without an additional prompt to do so.
109
+
110
+
```azurecli-interactive
111
+
az group delete --name $resourceGroup --yes --no-wait
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/alerts-reference.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,8 @@ At the bottom of this page, there's a table describing the Microsoft Defender fo
22
22
23
23
## <aname="alerts-windows"></a>Alerts for Windows machines
24
24
25
+
Microsoft Defender for Servers Plan 2 provides unique detections and alerts, in addition to the ones provided by Microsoft Defender for Endpoint. The alerts provided for Windows machines are:
26
+
25
27
[Further details and notes](defender-for-servers-introduction.md)
@@ -134,6 +136,8 @@ At the bottom of this page, there's a table describing the Microsoft Defender fo
134
136
135
137
## <aname="alerts-linux"></a>Alerts for Linux machines
136
138
139
+
Microsoft Defender for Servers Plan 2 provides unique detections and alerts, in addition to the ones provided by Microsoft Defender for Endpoint. The alerts provided for Linux machines are:
140
+
137
141
[Further details and notes](defender-for-servers-introduction.md)
0 commit comments