Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ccpgames/aggregateD
A dogstatsD inspired metrics and event aggregation daemon for InfluxDB.
https://github.com/ccpgames/aggregateD
Last synced: 6 days ago
JSON representation
A dogstatsD inspired metrics and event aggregation daemon for InfluxDB.
- Host: GitHub
- URL: https://github.com/ccpgames/aggregateD
- Owner: ccpgames
- License: mit
- Created: 2015-05-13T13:47:08.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-09-03T03:30:43.000Z (about 8 years ago)
- Last Synced: 2024-08-02T07:10:36.351Z (3 months ago)
- Language: Go
- Homepage:
- Size: 105 KB
- Stars: 14
- Watchers: 19
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-influxdb - aggregateD - A [dogstatsD](https://docs.datadoghq.com/guides/dogstatsd/) inspired metrics and event aggregation daemon for InfluxDB (Collecting data into InfluxDB / Projects)
README
[![Build Status](https://travis-ci.org/ccpgames/aggregateD.svg?branch=master)](https://travis-ci.org/ccpgames/ccp-aggregateD)
aggregateD
===========aggregateD is a network daemon which listens for metrics including gauges, counters, histograms, sets and events, sent over http and sends aggregates to InfluxDB. InfluxDB is a promising, but young time series database, aggregateD is intended to bring dogstatsD like functionality to Influx.
aggregateD can accept metrics either as JSON over HTTP or in the dogstatsD format sent over UDP. Therefore, aggregateD can be deployed in the same manner as either satsD or dogstatsD. That is, it can either run on the same host as instrumented applications or it can run on a dedicated host that multiple clients communicate with.
Usage and Configuration
-----------------------Usuage:
./aggregated -config aggregated.jsonaggregateD requires a minimal config in order to specify the InfluxDB server and its credentials. Config can either be provided as a json file or as a yaml file. An example config is as follows:
```yaml#accept metrics via HTTP
inputJSON: true
#accept metrics via plain StatsD
inputStatsD: true
#accept metrics via DogStatsD
inputDogStatsD: true#submit metrics to InfluxDB every 60 seconds
flushInterval: 60#output metrics via InfluxDB
outputInfluxDB: true#influxDB settings
influx:
url: http://localhost:8083
username: username
password: pass123
defaultDB: myDB#write to a redis list falback if InfluxDB is unavailable
redisOnInfluxFail: true
redisOutputURL: redis:6379
```aggregateD exposes two web service endpoints: /events and /metrics on port 8083 by default. aggregateD accepts json encoded metrics which take the form of:
```json
{
"name": "requests",
"host": "httpd.example.com",
"timestamp": 1461204545
"type": "gauge",
"value": 67,
"sampling": 1,
"secondaryValues": {"value1: "my.host"},
"tags": {"exampleTag1": 5, "exampleTag2": "value"}
}
```
Similarly, events are represented in the following format:```json
{
"name": "timeout",
"text": "a worker thread timedout",
"host": "node4.example.com",
"alerttype": "warning",
"priority": "normal",
"timestamp": 1461204545
"aggregationKey": "worker-timeout",
"sourceType": "default",
"tags": {"exampleTag1": 5, "exampleTag2": "value"},
}
```