Is graphite not a better solution for metrics in this case?
> On 16 Mar 2015, at 12:40, Eligijus Vitkauskas > <[email protected]> wrote: > > Hello, > > I'd like to know where is a proper place to accumulate stats. Imagine > this case: > > Server #1: > * Polls memory info every second > * Give this info to StatsAccumulator > * StatsAccumulator outputs every 10s via TCP to Server #2 > > Server #2 (responsible for displaying monitoring stuff): > * Listens for TCP > * Outputs to Elasticsearch > > My question if Stats accumulation should be handled on Server #2 instead > of Server #1. What are the best practices on this? > > Also does it make sense to store memory and cpu usage on elasticsearch > and display graphs with Kibana or should I use tools like Graphite for this? > > If it turns out that storing mem and cpu information on elasticsearch is > ok than is it ok to store that data on the same index that I store my > other logged information (like http access log)? > _______________________________________________ > Heka mailing list > [email protected] > https://mail.mozilla.org/listinfo/heka _______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
