cc-metric-collector/receivers
2022-08-17 17:37:24 +02:00
..
httpReceiver.go ioutils is depreceated 2022-08-15 15:25:20 +02:00
httpReceiver.md Add HttpReceiver as counterpart to the HttpSink (#49) 2022-03-05 17:30:55 +01:00
metricReceiver.go Additional comments 2022-02-28 12:16:48 +01:00
natsReceiver.go Refactor: Embed Init() into New() function 2022-02-23 15:15:17 +01:00
natsReceiver.md Update README and receiver-specific pages 2022-02-28 17:26:28 +01:00
prometheusReceiver.go Add scraper for Prometheus clients (#47) 2022-02-25 14:46:29 +01:00
prometheusReceiver.md Update README and receiver-specific pages 2022-02-28 17:26:28 +01:00
README.md Add HttpReceiver as counterpart to the HttpSink (#49) 2022-03-05 17:30:55 +01:00
receiveManager.go Add redfish receiver 2022-04-19 12:05:03 +02:00
redfishReceiver.go Fix for servers, which do not set status.state for thermals or powercontrols 2022-08-17 17:37:24 +02:00
redfishReceiver.md Add redfish receiver documentation 2022-08-11 15:36:18 +02:00
sampleReceiver.go Extended go routine use case in sample receiver 2022-04-19 11:42:46 +02:00

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

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