Struct Anomaly 

#[non_exhaustive]
pub struct Anomaly {
    pub observation_parameter: Option<String>,
    pub observation_type: Option<String>,
    pub observations: Option<Vec<Observation>>,
    pub observed_pattern: Option<String>,
}

Anomaly

Describes an anomaly or deviation detected in a system. Anomalies are unexpected activity patterns that could indicate potential issues needing attention.

[] Category: | Name: anomaly

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

observation_parameter: Option<String>

Observation Parameter

The specific parameter, metric or property where the anomaly was observed. Examples include: CPU usage percentage, API response time in milliseconds, HTTP error rate, memory utilization, network latency, transaction volume, etc. This helps identify the exact aspect of the system exhibiting anomalous behavior.

required

observation_type: Option<String>

Observation Type

The type of analysis methodology used to detect the anomaly. This indicates how the anomaly was identified through different analytical approaches. Common types include: Frequency Analysis, Time Pattern Analysis, Volume Analysis, Sequence Analysis, Distribution Analysis, etc.

recommended

observations: Option<Vec<Observation>>

Observations

Details about the observed anomaly or observations that were flagged as anomalous compared to expected baseline behavior.

required

observed_pattern: Option<String>

Observed Pattern

The specific pattern identified within the observation type. For Frequency Analysis, this could be ‘FREQUENT’, ‘INFREQUENT’, ‘RARE’, or ‘UNSEEN’. For Time Pattern Analysis, this could be ‘BUSINESS_HOURS’, ‘OFF_HOURS’, or ‘UNUSUAL_TIME’. For Volume Analysis, this could be ‘NORMAL_VOLUME’, ‘HIGH_VOLUME’, or ‘SURGE’. The pattern values are specific to each observation type and indicate how the observed behavior relates to the baseline.

recommended

Trait Implementations

impl Clone for Anomaly

fn clone(&self) -> Anomaly

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Anomaly

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for Anomaly

fn default() -> Anomaly

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for Anomaly

where Anomaly: Default,

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for Anomaly

fn eq(&self, other: &Anomaly) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for Anomaly

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for Anomaly