Files
zeekay 189ce08e51 Regenerate against the document the deployment answers for
The projection these were generated from was a month old and predated the
compute migration, so every one of them described /v1/visor — which the API
serves at zero paths now. That is why a hand-written console client and a
generated one had drifted the same way at the same time.

No /v1/visor path survives here. The word still appears as a source-plane
value and inside gvisor and supervisor, which are not this rename.
2026-09-05 18:07:13 -07:00

140 lines
3.4 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.
*/
/*
* Metrics.h
*
*
*/
#ifndef HANZO_MODEL_Metrics_H_
#define HANZO_MODEL_Metrics_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
namespace hanzo {
namespace model {
class Metrics
: public ModelBase
{
public:
Metrics();
virtual ~Metrics();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// Metrics members
/// <summary>
/// unix seconds, server-stamped
/// </summary>
int64_t getAt() const;
bool atIsSet() const;
void unsetAt();
void setAt(int64_t value);
/// <summary>
/// 0..1 aggregate utilization
/// </summary>
double getGpuUtil() const;
bool gpuUtilIsSet() const;
void unsetGpuUtil();
void setGpuUtil(double value);
/// <summary>
/// Load1 is the machine&#39;s own one-minute load average — a count of runnable and uninterruptible tasks, NOT a percentage and NOT already divided by core count, so it is read against Spec.CPUs: 8.0 is idle on 16 cores and swamped on 4. Coerced finite and non-negative on write, so 0 means either genuinely idle or nothing reported.
/// </summary>
double getLoad1() const;
bool load1IsSet() const;
void unsetLoad1();
void setLoad1(double value);
/// <summary>
/// Load15 is the same figure over fifteen. The three together are what separate a machine that is busy right now from one that has been busy all along — which is the question a dispatcher is really asking.
/// </summary>
double getLoad15() const;
bool load15IsSet() const;
void unsetLoad15();
void setLoad15(double value);
/// <summary>
/// Load5 is the same figure averaged over five minutes.
/// </summary>
double getLoad5() const;
bool load5IsSet() const;
void unsetLoad5();
void setLoad5(double value);
/// <summary>
/// bytes
/// </summary>
int64_t getMemFree() const;
bool memFreeIsSet() const;
void unsetMemFree();
void setMemFree(int64_t value);
/// <summary>
/// bytes
/// </summary>
int64_t getMemUsed() const;
bool memUsedIsSet() const;
void unsetMemUsed();
void setMemUsed(int64_t value);
protected:
int64_t m_At;
bool m_AtIsSet;
double m_GpuUtil;
bool m_GpuUtilIsSet;
double m_Load1;
bool m_Load1IsSet;
double m_Load15;
bool m_Load15IsSet;
double m_Load5;
bool m_Load5IsSet;
int64_t m_MemFree;
bool m_MemFreeIsSet;
int64_t m_MemUsed;
bool m_MemUsedIsSet;
};
}
}
#endif /* HANZO_MODEL_Metrics_H_ */