Skip to content

Commit 316033e

Browse files
committed
up2
1 parent 94971b9 commit 316033e

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/defender-for-iot/organizations/how-to-control-what-traffic-is-monitored.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -184,13 +184,12 @@ If you're working with dynamic networks, you need to handle IP addresses changes
184184
1. Select **Save** to save your changes.
185185

186186
## Configure traffic filters (advanced)
187-
<!-- should this be removed if the alerts arent available? -->
187+
**Belle remove this??** <!-- should this be removed if the alerts arent available? -->
188188
To reduce alert fatigue and focus your network monitoring on high priority traffic, you may decide to filter the traffic that streams into Defender for IoT at the source. Capture filters are configured via the OT sensor CLI, and allow you to block high-bandwidth traffic at the hardware layer, optimizing both appliance performance and resource usage.
189189

190190
For more information, see:
191191

192192
- [Defender for IoT CLI users and access](references-work-with-defender-for-iot-cli-commands.md)
193-
- [Traffic capture filters](cli-ot-sensor.md#traffic-capture-filters)
194193

195194
## Next steps
196195

0 commit comments

Comments
 (0)