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: docs/doxygen/demos/defender_demo.dox
+8-2
Original file line number
Diff line number
Diff line change
@@ -12,14 +12,20 @@ The demo reports the following metrics to the AWS IoT Device Defender Service:
12
12
- List of open TCP ports
13
13
- List of open UDP ports
14
14
- List of established connections
15
+
- System CPU usage statistics (as a custom metric of number-list type)
16
+
- System memory statistics (as a custom metric of string-list type)
15
17
16
-
The demo gets the above metrics by reading `/proc/net/dev`, `/proc/net/tcp` and,
17
-
`/proc/net/udp`. It then constructs a JSON report in the format as expected by
18
+
The demo gets the above metrics by reading `/proc/net/dev`, `/proc/net/tcp`,
19
+
`/proc/net/udp`, `/proc/uptime`, and `/proc/meminfo`. It then constructs a JSON report in the format as expected by
18
20
the AWS IoT Device Defender service. The constructed JSON report is then
19
21
published on the device defender MQTT topic reserved for publishing JSON
20
22
reports. The demo then waits for a report accepted response, and ensures that
21
23
the response contains the same report Id as was sent in the request.
22
24
25
+
For the AWS IoT Device Defender service to make use of the custom metrics reported by the demo, you need to
26
+
define the custom metrics in your account. You can use either the AWS console or CLI to create
27
+
custom metrics in your account. For more information, please refer to [Custom Metrics AWS documentation](https://docs.aws.amazon.com/iot/latest/developerguide/dd-detect-custom-metrics.html).
0 commit comments