mirror of
https://github.com/ClusterCockpit/cc-metric-collector.git
synced 2025-04-05 05:05:56 +02:00
8e8be09ed9
* Add cpu_used (all-cpu_idle) to CpustatCollector * Update cc-metric-collector.init * Allow selection of timestamp precision in HttpSink * Add comment about precision requirement for cc-metric-store * Fix for API changes in gofish@v0.15.0 * Update requirements to latest version * Read sensors through redfish * Update golang toolchain to 1.21 * Remove stray error check * Update main config in configuration.md * Update Release action to use golang 1.22 stable release, no golang RPMs anymore * Update runonce action to use golang 1.22 stable release, no golang RPMs anymore * Update README.md Use right JSON type in configuration * Update sink's README * Test whether ipmitool or ipmi-sensors can be executed without errors --------- Co-authored-by: Holger Obermaier <Holger.Obermaier@kit.edu> Co-authored-by: Holger Obermaier <40787752+ho-ob@users.noreply.github.com>
CCMetric receivers
This folder contains the ReceiveManager and receiver implementations for the cc-metric-collector.
Configuration
The configuration file for the receivers is a list of configurations. The type field in each specifies which receiver to initialize.
{
"myreceivername" : {
"type": "receiver-type",
<receiver-specific configuration>
}
}
This allows to specify
Available receivers
nats: Receive metrics from the NATS networkprometheus: Scrape data from a Prometheus clienthttp: Listen for HTTP Post requests transporting metrics in InfluxDB line protocolipmi: Read IPMI sensor readingsredfishUse the Redfish (specification) to query thermal and power metrics
Contributing own receivers
A receiver contains a few functions and is derived from the type Receiver (in metricReceiver.go):
For an example, check the sample receiver