Skip to content

Commit 2480252

Browse files
committed
Added health monitoring note
1 parent 23ae43f commit 2480252

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

articles/sentinel/connect-aws-s3-waf.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -142,11 +142,13 @@ When the resource stacks are all created, return to the browser tab open to the
142142

143143
Now that the automatic setup process is more reliable, there aren't many good reasons to resort to manual setup. If you must, though, see the [Manual setup instructions](connect-aws.md#manual-setup) in the [Amazon Web Services S3 Connector documentation](connect-aws.md).
144144

145-
## Test the connector
145+
## Test and monitor the connector
146146

147-
After the connector is set up, go to the **Logs** page (or the **Advanced hunting** page in the Defender portal) and run the following query. If you get any results, the connector is working properly.
147+
1. After the connector is set up, go to the **Logs** page (or the **Advanced hunting** page in the Defender portal) and run the following query. If you get any results, the connector is working properly.
148148

149-
```kusto
150-
AWSWAF
151-
| take 10
152-
```
149+
```kusto
150+
AWSWAF
151+
| take 10
152+
```
153+
154+
1. If you haven't already done so, we recommend that you implement **data connector health monitoring** so that you can know when connectors are not receiving data or any other issues with connectors. For more information, see [Monitor the health of your data connectors](monitor-data-connector-health.md).

0 commit comments

Comments
 (0)