Thomas Gruber bd04e19c96
Merge development branch to main (#141)
* Remove go-toolkit as build requirement for RPM builds if run in CI

* Remove condition around BuildRequires and use go-toolkit for RPM builds

* use go-toolkit for RPM builds

* Install go-toolkit to fulfill build requirements for RPM

* Add golang-race for UBI9 and Alma9

* Fix wrongly named packages

* Fix wrongly named packages

* Fix Release part

* Fix Release part

* Fix documentation of RAPL collector

* Mark all JSON config fields of message processor as omitempty

* Generate HUGO inputs out of Markdown files

* Check creation of CCMessage in NATS receiver

* Use CCMessage FromBytes instead of Influx's decoder

* Rename 'process_message' to 'process_messages' in metricRouter config

This makes the behavior more consistent with the other modules, which
have their MessageProcessor named 'process_messages'. This most likely
was just a typo.

* Add optional interface alias in netstat (#130)

* Check creation of CCMessage in NATS receiver

* add optional interface aliases for netstatMetric

* small fix

---------

Co-authored-by: Thomas Roehl <thomas.roehl@fau.de>
Co-authored-by: exterr2f <Robert.Externbrink@rub.de>
Co-authored-by: Thomas Gruber <Thomas.Roehl@googlemail.com>

* Fix excluded metrics for diskstat and add exclude_mounts (#131)

* Check creation of CCMessage in NATS receiver

* fix excluded metrics and add optional mountpoint exclude

---------

Co-authored-by: Thomas Roehl <thomas.roehl@fau.de>
Co-authored-by: exterr2f <Robert.Externbrink@rub.de>
Co-authored-by: Thomas Gruber <Thomas.Roehl@googlemail.com>

* Add derived values for nfsiostat (#132)

* Check creation of CCMessage in NATS receiver

* add derived_values for nfsiostatMetric

---------

Co-authored-by: Thomas Roehl <thomas.roehl@fau.de>
Co-authored-by: exterr2f <Robert.Externbrink@rub.de>
Co-authored-by: Thomas Gruber <Thomas.Roehl@googlemail.com>

* Add exclude_devices to iostat (#133)

* Check creation of CCMessage in NATS receiver

* add exclude_device for iostatMetric

* add md file

---------

Co-authored-by: Thomas Roehl <thomas.roehl@fau.de>
Co-authored-by: exterr2f <Robert.Externbrink@rub.de>
Co-authored-by: Thomas Gruber <Thomas.Roehl@googlemail.com>

* Add derived_values for numastats (#134)

* Check creation of CCMessage in NATS receiver

* add derived_values for numastats

* change to ccMessage

* remove vim command artefact

---------

Co-authored-by: Thomas Roehl <thomas.roehl@fau.de>
Co-authored-by: exterr2f <Robert.Externbrink@rub.de>
Co-authored-by: Thomas Gruber <Thomas.Roehl@googlemail.com>

* Fix artifacts of not done cc-lib switch

* Fix artifacts in netstat collector of not done cc-lib switch

* Change to cc-lib (#135)

* Change to ccMessage from cc-lib

* Remove local development path

* Use receiver, sinks, ccLogger and ccConfig from cc-lib

* Fix ccLogger import path

* Update CI

* Delete mountpoint when it vanishes, not just its data (#137)

---------

Co-authored-by: Michael Panzlaff <michael.panzlaff@fau.de>
Co-authored-by: brinkcoder <Robert.Externbrink@ruhr-uni-bochum.de>
Co-authored-by: exterr2f <Robert.Externbrink@rub.de>
2025-04-16 13:38:11 +02:00
..

The MetricAggregator

In some cases, further combination of metrics or raw values is required. For that strings like foo + 1 with runtime dependent foo need to be evaluated. The MetricAggregator relies on the gval Golang package to perform all expression evaluation. The gval package provides the basic arithmetic operations but the MetricAggregator defines additional ones.

Note: To get an impression which expressions can be handled by gval, see its README

Simple expression evaluation

For simple expression evaluation, the MetricAggregator provides two function for different use-cases:

  • EvalBoolCondition(expression string, params map[string]interface{}: Used by the MetricRouter to match metrics like metric.Name() == 'mymetric'
  • EvalFloat64Condition(expression string, params map[string]interface{}): Used by the MetricRouter and LikwidCollector to derive new values like (PMC0+PMC1)/PMC3

MetricAggregator extensions for gval

The MetricAggregator provides these functions additional to the Full language in gval:

  • sum(array): Sum up values in an array like sum(values)
  • min(array): Get the minimum value in an array like min(values)
  • avg(array): Get the mean value in an array like avg(values)
  • mean(array): Get the mean value in an array like mean(values)
  • max(array): Get the maximum value in an array like max(values)
  • len(array): Get the length of an array like len(values)
  • median(array): Get the median value in an array like mean(values)
  • in: Check existence in an array like 0 in getCpuList() to check whether there is an entry 0. Also substring matching works like temp in metric.Name()
  • match: Regular-expression matching like match('temp_cores_%d+', metric.Name()). Note all \ in an regex has to be replaced with %
  • getCpuCore(cpuid): For a CPU id, the the corresponding CPU core id like getCpuCore(0)
  • getCpuSocket(cpuid): For a CPU id, the the corresponding CPU socket id
  • getCpuNuma(cpuid): For a CPU id, the the corresponding NUMA domain id
  • getCpuDie(cpuid): For a CPU id, the the corresponding CPU die id
  • getSockCpuList(sockid): For a given CPU socket id, the list of CPU ids is returned like the CPUs on socket 1 getSockCpuList(1)
  • getNumaCpuList(numaid): For a given NUMA node id, the list of CPU ids is returned
  • getDieCpuList(dieid): For a given CPU die id, the list of CPU ids is returned
  • getCoreCpuList(coreid): For a given CPU core id, the list of CPU ids is returned
  • getCpuList: Get the list of all CPUs

Limitations

  • Since the metrics are written in JSON files which do not allow "" without proper escaping inside of JSON strings, you have to use '' for strings.
  • Since \ is interpreted by JSON as escape character, it cannot be used in metrics. But it is required to write regular expressions. So instead of /, use % and the MetricAggregator replaces them after reading the JSON file.