class Aws::IoT::Types::Behavior

@return [Boolean]
Suppresses alerts.
@!attribute [rw] suppress_alerts
@return [Types::BehaviorCriteria]
regard to the ‘metric`.
The criteria that determine if a device is behaving normally in
@!attribute [rw] criteria
@return [Types::MetricDimension]
specified in the dimension. This can’t be used with custom metrics.
metric to only MQTT topics where the name matches the pattern
`TOPIC_FILTER` dimension, you can narrow down the scope of the
The dimension for a metric in your behavior. For example, using a
@!attribute [rw] metric_dimension
@return [String]
What is measured by the behavior.
@!attribute [rw] metric
@return [String]
The name you’ve given to the behavior.
@!attribute [rw] name
}
suppress_alerts: false,
},
},
confidence_level: “LOW”, # required, accepts LOW, MEDIUM, HIGH
ml_detection_config: {
},
statistic: “EvaluationStatistic”,
statistical_threshold: {
consecutive_datapoints_to_clear: 1,
consecutive_datapoints_to_alarm: 1,
duration_seconds: 1,
},
strings: [“stringValue”],
numbers: [1.0],
number: 1.0,
ports: [1],
cidrs: [“Cidr”],
count: 1,
value: {
comparison_operator: “less-than”, # accepts less-than, less-than-equals, greater-than, greater-than-equals, in-cidr-set, not-in-cidr-set, in-port-set, not-in-port-set, in-set, not-in-set
criteria: {
},
operator: “IN”, # accepts IN, NOT_IN
dimension_name: “DimensionName”, # required
metric_dimension: {
metric: “BehaviorMetric”,
name: “BehaviorName”, # required
{
data as a hash:
@note When making an API call, you may pass Behavior
A Device Defender security profile behavior.