hanzo-client 8.5.156

Generated client for the Hanzo API — every service, one crate.
Documentation
/*
 * Hanzo Cloud API
 *
 * The Hanzo Cloud API as a customer calls it: every operation under /v1/ except the operator's admin product, relay routes, legacy spellings and capabilities still reached by flag. Tagged by product: the first path segment after /v1/.
 *
 * The version of the OpenAPI document: v1
 * 
 * Generated by: https://openapi-generator.tech
 */

use crate::models;
use serde::{Deserialize, Serialize};

/// O11yMetricsResponseSeries : Series is the RED trend: request rate, error rate and two latency quantiles, bucketed at range.stepSec and oldest bucket first. Latencies are in MILLISECONDS.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct O11yMetricsResponseSeries {
    #[serde(rename = "errors", skip_serializing_if = "Option::is_none")]
    pub errors: Option<Vec<models::O11yPeriodPoint>>,
    #[serde(rename = "latencyP50Ms", skip_serializing_if = "Option::is_none")]
    pub latency_p50_ms: Option<Vec<models::O11yPeriodPoint>>,
    #[serde(rename = "latencyP95Ms", skip_serializing_if = "Option::is_none")]
    pub latency_p95_ms: Option<Vec<models::O11yPeriodPoint>>,
    #[serde(rename = "requests", skip_serializing_if = "Option::is_none")]
    pub requests: Option<Vec<models::O11yPeriodPoint>>,
}

impl O11yMetricsResponseSeries {
    /// Series is the RED trend: request rate, error rate and two latency quantiles, bucketed at range.stepSec and oldest bucket first. Latencies are in MILLISECONDS.
    pub fn new() -> O11yMetricsResponseSeries {
        O11yMetricsResponseSeries {
            errors: None,
            latency_p50_ms: None,
            latency_p95_ms: None,
            requests: None,
        }
    }
}