Files
sdk/include/hanzo/model/O11y_metricsResponse_series.h
zeekay 645325a641 regenerate from cloud 939b09d4
The projection was 113 commits behind the document it claims to describe, and
`generate.py --all --check` reported every one of the thirteen clients DRIFTED —
the same +19 models in each, because they all fell behind the same emission.

Regenerated in place from hanzo-inc/cloud openapi.yaml at 939b09d4
(sha256 087024f6…), which is the only description of this API that cannot name a
route the binary does not serve. `--check` is clean across all thirteen after.

.spec-lock moved with the code. The generator READS that file and never writes
it — hanzoai/ci`s lane does — so a hand run leaves every lock naming the previous
document. A lock that disagrees with the tree beside it is worse than no lock:
the next `--check` without `--spec` fetches what production serves, compares it
to a digest that was already wrong, and reports drift that is really staleness.
2026-08-24 23:32:53 -07:00

101 lines
3.0 KiB
C++

/**
* 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
*
* NOTE: This class is auto generated by OpenAPI-Generator 7.14.0.
* https://openapi-generator.tech
* Do not edit the class manually.
*/
/*
* O11y_metricsResponse_series.h
*
* 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.
*/
#ifndef HANZO_MODEL_O11y_metricsResponse_series_H_
#define HANZO_MODEL_O11y_metricsResponse_series_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include "hanzo/model/O11y_point.h"
#include <vector>
namespace hanzo {
namespace model {
class O11y_point;
/// <summary>
/// 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.
/// </summary>
class O11y_metricsResponse_series
: public ModelBase
{
public:
O11y_metricsResponse_series();
virtual ~O11y_metricsResponse_series();
/////////////////////////////////////////////
/// ModelBase overrides
void validate() override;
web::json::value toJson() const override;
bool fromJson(const web::json::value& json) override;
void toMultipart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) const override;
bool fromMultiPart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) override;
/////////////////////////////////////////////
/// O11y_metricsResponse_series members
std::vector<std::shared_ptr<O11y_point>> getErrors() const;
bool errorsIsSet() const;
void unsetErrors();
void setErrors(const std::vector<std::shared_ptr<O11y_point>>& value);
std::vector<std::shared_ptr<O11y_point>> getLatencyP50Ms() const;
bool latencyP50MsIsSet() const;
void unsetLatencyP50Ms();
void setLatencyP50Ms(const std::vector<std::shared_ptr<O11y_point>>& value);
std::vector<std::shared_ptr<O11y_point>> getLatencyP95Ms() const;
bool latencyP95MsIsSet() const;
void unsetLatencyP95Ms();
void setLatencyP95Ms(const std::vector<std::shared_ptr<O11y_point>>& value);
std::vector<std::shared_ptr<O11y_point>> getRequests() const;
bool requestsIsSet() const;
void unsetRequests();
void setRequests(const std::vector<std::shared_ptr<O11y_point>>& value);
protected:
std::vector<std::shared_ptr<O11y_point>> m_Errors;
bool m_ErrorsIsSet;
std::vector<std::shared_ptr<O11y_point>> m_LatencyP50Ms;
bool m_LatencyP50MsIsSet;
std::vector<std::shared_ptr<O11y_point>> m_LatencyP95Ms;
bool m_LatencyP95MsIsSet;
std::vector<std::shared_ptr<O11y_point>> m_Requests;
bool m_RequestsIsSet;
};
}
}
#endif /* HANZO_MODEL_O11y_metricsResponse_series_H_ */