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
{{ message }}
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.
If these cannot be supported out of the box, at least some way to enable this functionality in a platform dependent port should be there. Even if i have e.g. network statistics available on my platform, i don't see a way to publish these right now.
The text was updated successfully, but these errors were encountered:
Thank you for your suggestion and feedback; we will consider it for future releases. Metrics collection is handled by the platform, and currently only the TCP connections metrics group is supported.
Although the API does not expose a method for adding other metrics groups, if your platform has other metrics available, then you could try implementing the functionality to publish them. Note that this would require adding code to parts of the Defender library. To start, you could add a new metrics group here and update the count. You would also need to add code to serialize the metrics group.
Currently, defender only supports AWS_IOT_DEFENDER_METRICS_TCP_CONNECTIONS. There is no known way to me to provide other groups such as "Listening UDP ports", "Listening TCP ports", and "Network statistics" (see https://docs.aws.amazon.com/iot/latest/developerguide/device-defender-detect.html#DetectMetricsMessages).
If these cannot be supported out of the box, at least some way to enable this functionality in a platform dependent port should be there. Even if i have e.g. network statistics available on my platform, i don't see a way to publish these right now.
The text was updated successfully, but these errors were encountered: