Merge pull request #222240 from miashapan/agent-configurations

Agent configurations

Author: prmerger-automator[bot]

articles/defender-for-iot/device-builders/concept-micro-agent-configuration.md

@@ -54,6 +54,11 @@ Configure the micro agent using the following collector-specific properties and
 |--|--|--|--|
 | **SystemInformation_Disabled** | `True`/`False` | Disables the System Information collector. | `False` |
 | **SystemInformation_MessageFrequency** | `Low`/`Medium`/`High` | Defines the frequency in which to send System Information events. | `Low` |
+| **SystemInformation_HardwareVendor** | string | Set hardware vendor information. | `None` |
+| **SystemInformation_HardwareModel** | string | Set hardware model information. | `None` |
+| **SystemInformation_HardwareSerialNumber** | string | Set hardware serial number information. | `None` |
+| **SystemInformation_FirmwareVendor** | string | Set firmware vendor information. | `None` |
+| **SystemInformation_FirmwareVersion** | string | Set firmware version information. | `None` |
 
 ### SBoM collector-specific settings
 
@@ -91,6 +96,7 @@ Configure the micro agent using the following collector-specific properties and
 | **NetworkActivity_MessageFrequency** | `Low`/`Medium`/`High` | Defines the frequency in which to send Network Activity events. | `Medium` |
 | **NetworkActivity_Devices** | A list of the network devices separated by a comma. <br><br>For example `eth0,eth1` | Defines the list of network devices (interfaces) that the agent will use to monitor the traffic. <br><br>If a network device isn't listed, the network raw events won't be recorded for the missing device.| `eth0` |
 | **NetworkActivity_CacheSize** | Positive integer | The number of Network Activity events (after aggregation) to keep in the cache between send intervals. Beyond that number, older events will be dropped (lost).| `256` |
+| **NetworkActivity_PacketBufferSize** | Positive integer | Tonfigure the buffer size (in bytes) that will be used to capture packets for a single device per direction (incoming or outcoming traffic). | `2097152 (=2MB)` |
 
 ### Process collector-specific settings
 

articles/defender-for-iot/device-builders/tutorial-standalone-agent-binary-installation.md

@@ -137,6 +137,26 @@ This procedure describes additional steps required to support the AMQP protocol.
     sudo systemctl restart defender-iot-micro-agent.service
     ```
 
+**To add AMQP over web socket protocol support**:
+
+1. On your micro-agent machine, open the `/etc/defender_iot_micro_agent/conf.json` file and add the following content:
+
+    ```json
+    {
+    "IothubModule_TransportProtocol": "AMQP_WebSocket_Protocol"
+    }
+    ```
+1. Delete any cached file at **/var/lib/defender_iot_micro_agent/cache.json**.
+
+1. Restart the micro-agent. Run
+
+    ```bash
+    sudo systemctl restart defender-iot-micro-agent.service
+    ```
+
+The agent will use this protocol, and communicate with the IoT Hub on port 443.
+Http Proxy configuration is supported for this protocol, in the case that proxy is also configured, the port of communication with the proxy will be as defined in the proxy configuration.
+
 ## Authenticate the micro agent
 
 There are two options that can be used to authenticate the Defender for IoT micro agent: