Modified monitoring stack to use Telegraf and Timely#279
Modified monitoring stack to use Telegraf and Timely#279dlmarion merged 24 commits intoapache:mainfrom
Conversation
|
With these changes, does the Deployment Overview section in the README need to be updated? |
Done in 3bf6d7f |
|
@dlmarion what's the status of this? |
|
@ctubbsii - status is I was just waiting for review to happen. I'll make sure that it's up date. |
ctubbsii
left a comment
ctubbsii
left a comment
There was a problem hiding this comment.
I'm not opposed to merging this, but I'm not clear on its value either. I don't know how much value InfluxDB offered, vs. Timely.
"It's fine, I guess", is about all I can say, if people find it useful for testing Accumulo. I don't frequently use the Terraform stuff, though, and haven't tested this myself.
The value here is that using Timely instead of InfluxDB places load on Accumulo as Timely stores its data in Accumulo. Having the cluster running inserts data without having to run CI. |
Fixes from testing
3 participants
This commit modifies the Terraform configuration such that instead of deploying a Telegraf/InfluxDB/Grafana container on the Manager node, it now deploys Telegraf on each node and uses a Timely/Grafana container on the Manager node. The processes running on each node will send metrics to the Telegraf process running locally,which will then forward the metrics to Timely to be inserted into Accumulo. Thus, as the cluster grows larger, more and more metrics will be created and inserted into Accumulo.