Hi,
Now I am able to collect all information needed.
But I still have a problém with collected data - there are very often gaps in graphs.
I moved whisper databases on memory filesystem and now the load does not exceed 1 (2 CPU machine)
I checked ipdevpoll.log for errors but nothing there.
I am collecting now 56 125 metrics - I just counted whisper databases in nav.* context. And it is about an half of the network monitored.
Any idea where could be a bottleneck now and how to figure it out? Any suggestions to further tweak the systém?
Mat -----Original Message----- From: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sent: Wednesday, March 26, 2014 2:34 PM To: JABUREK Martin Cc: John-Magne Bredal; nav-users@uninett.no Subject: Re: Problem retrieving port statistics
On Wed, 26 Mar 2014 12:26:43 +0000 "Martin.Jaburek@cah.cz" Martin.Jaburek@cah.cz wrote:
I checked it and it was indeed set to 50. I changed it to inf and I restarted nav and carbon.
Now I can see many new databases being created. Thank you very much for such swift response.
No problem, I'm glad you've sorted it out :)
It's a shame, that carbon ignores exceeding creation requests silently (I even checked the creates.log for new databases)
The feature is quite deliberate. AFAIK, Carbon/graphite was built for storing massive amounts of metrics from a cloud provider, where each individual metric wasn't necessarily very significant (i.e. cloud servers come and go all the time; the individual server doesn't matter in the grand scheme of things, the provided service level does).
The feature is there to not completely overload the I/O system of the Carbon server in such a setting. In the smaller context of a single NAV installation, individual metrics matter more, and the default setting of 50 becomes too small, given that the majority of metrics are only delivered once every five minutes, not every 10 seconds.
-- Morten Brekkevold UNINETT