infrastructure

type KVMHostCapacityKPI ¶

type KVMHostCapacityKPI struct {
	// Common base for all KPIs that provides standard functionality.
	plugins.BaseKPI[struct{}] // No options passed through yaml config
	// contains filtered or unexported fields
}

func (k *KVMHostCapacityKPI) Collect(ch chan<- prometheus.Metric)

func (k *KVMHostCapacityKPI) Describe(ch chan<- *prometheus.Desc)

func (KVMHostCapacityKPI) GetName() string

func (k *KVMHostCapacityKPI) Init(db *db.DB, client client.Client, opts conf.RawOpts) error

type KVMProjectUtilizationKPI ¶

type KVMProjectUtilizationKPI struct {
	// BaseKPI provides common fields and methods for all KPIs, such as database connection and Kubernetes client.
	plugins.BaseKPI[struct{}]
	// contains filtered or unexported fields
}

func (k *KVMProjectUtilizationKPI) Collect(ch chan<- prometheus.Metric)

func (k *KVMProjectUtilizationKPI) Describe(ch chan<- *prometheus.Desc)

func (k *KVMProjectUtilizationKPI) GetName() string

func (k *KVMProjectUtilizationKPI) Init(dbConn *db.DB, c client.Client, opts conf.RawOpts) error

type VMwareHostCapacityKPI ¶

type VMwareHostCapacityKPI struct {
	plugins.BaseKPI[struct{}]
	// contains filtered or unexported fields
}

func (k *VMwareHostCapacityKPI) Collect(ch chan<- prometheus.Metric)

func (k *VMwareHostCapacityKPI) Describe(ch chan<- *prometheus.Desc)

func (k *VMwareHostCapacityKPI) GetName() string

func (k *VMwareHostCapacityKPI) Init(dbConn *db.DB, c client.Client, opts conf.RawOpts) error

type VMwareProjectCommitmentsKPI ¶

type VMwareProjectCommitmentsKPI struct {
	// BaseKPI provides common fields and methods for all KPIs, such as database connection and Kubernetes client.
	plugins.BaseKPI[struct{}]
	// contains filtered or unexported fields
}

This KPI tracks committed resources in the VMware environment, based on commitments provided by Limes. For KVM we can map a commitment to a reservation on a specific host. In VMware this is not possible. For general purpose workload customer can specific amounts of resources. For HANA workloads customers commit a certain number of HANA instances (based on flavor). Like this it is possible to determine the workload type of a commitment. For general purpose workloads its not possible to differentiate the cpu architecture. To avoid weird behavior in a dashboard we don't export this label for the metric. For HANA flavors the cpu architecture is part of the flavor name (_v2 suffix for sapphire rapids, without suffix for cascade lake). For both types of workload however we can not determine on which host the commitment is fulfilled.

func (k *VMwareProjectCommitmentsKPI) Collect(ch chan<- prometheus.Metric)

func (k *VMwareProjectCommitmentsKPI) Describe(ch chan<- *prometheus.Desc)

func (k *VMwareProjectCommitmentsKPI) GetName() string

func (k *VMwareProjectCommitmentsKPI) Init(dbConn *db.DB, c client.Client, opts conf.RawOpts) error

type VMwareProjectUtilizationKPI ¶

type VMwareProjectUtilizationKPI struct {
	// BaseKPI provides common fields and methods for all KPIs, such as database connection and Kubernetes client.
	plugins.BaseKPI[struct{}]
	// contains filtered or unexported fields
}

func (k *VMwareProjectUtilizationKPI) Collect(ch chan<- prometheus.Metric)

func (k *VMwareProjectUtilizationKPI) Describe(ch chan<- *prometheus.Desc)

func (k *VMwareProjectUtilizationKPI) GetName() string

func (k *VMwareProjectUtilizationKPI) Init(dbConn *db.DB, c client.Client, opts conf.RawOpts) error