cc-metric-collector/receivers
2024-07-13 02:23:58 +02:00
..
httpReceiver.go Switch to CCMessage for all files. 2024-07-13 02:23:58 +02:00
httpReceiver.md Merge develop into main (#109) 2023-12-04 12:21:26 +01:00
ipmiReceiver.go Switch to CCMessage for all files. 2024-07-13 02:23:58 +02:00
ipmiReceiver.md
metricReceiver.go Switch to CCMessage for all files. 2024-07-13 02:23:58 +02:00
natsReceiver.go Switch to CCMessage for all files. 2024-07-13 02:23:58 +02:00
natsReceiver.md Merge develop into main (#109) 2023-12-04 12:21:26 +01:00
prometheusReceiver.go Switch to CCMessage for all files. 2024-07-13 02:23:58 +02:00
prometheusReceiver.md
README.md Merge develop into main (#109) 2023-12-04 12:21:26 +01:00
receiveManager.go Switch to CCMessage for all files. 2024-07-13 02:23:58 +02:00
redfishReceiver.go Switch to CCMessage for all files. 2024-07-13 02:23:58 +02:00
redfishReceiver.md Read sensors through redfish 2024-03-06 14:59:47 +01:00
sampleReceiver.go

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 network
  • prometheus: Scrape data from a Prometheus client
  • http: Listen for HTTP Post requests transporting metrics in InfluxDB line protocol
  • ipmi: Read IPMI sensor readings
  • redfish Use 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