custom RRDs

Anything that you think should be in Cacti.

Moderators: Developers, Moderators

Post Reply
Magistrator

custom RRDs

Post by Magistrator »

I wonder if it isn’t more practical to create new RRDs based
on the result of arithmetic operations over other existing RRDs.
This approach would simplify the graphic making process a lot. And
would relocate each processes, of “graphic making” and
“data treatment”, to different areas.

I work my ass out to create nice data summations of interfaces
and network traffic between other things. With the above approach it would be much easier.


Cheers!
User avatar
TheWitness
Developer
Posts: 17047
Joined: Tue May 14, 2002 5:08 pm
Location: MI, USA
Contact:

Post by TheWitness »

Judgeman,

You realy need to be more specific. I am totally confused.

TheWitness
True understanding begins only when we realize how little we truly understand...

Life is an adventure, let yours begin with Cacti!

Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages


For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Magistrator

Post by Magistrator »

Each set of data collected is stored on an RRD file. It’s from these RRD files that we create graphs. Each graph is based on a set of various RRDs, we can even apply CDFs and staking functionalities to achieve determined graphic results.

My proposal is to create a way where we can create a new RRD file based not on some equipment ordinary data query, but based on the result of arithmetic operations on other RRDs.

So for example, imagine you want to know the total flux of data that enters a specific sub-network. I want to create a special RRD file that is the result of the sum and subtraction of specific gateway interfaces already existent RRDs. Then I would simply have to graph ONE RRD.

Right now as it is, Cacti makes this process a hard one, cause it makes me handle all the RRDs I need, at once, while creating the graph make-up.

This type of example is of course painful for large networks like mine where I have 84 equipments to monitor. So dividing the process in two step would make things a lot easier.
1º - Create a new RRD based on data treatment of other existent RRDs.
2º - Graph the single RRD data with a single simple graph template, (no staking or CDFs)


Please did I make myself clear?
Cheers
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests