I figured as much, and assumed that’s why you built the better, more dynamic graphing solution. We’ve unfortunately been using RRD 95th for quite a while. We can easily move away from it since no one would know the difference, but the challenge is the “proof” (either automatic or on-demand) we’re required to provide our customers.
Is there a way to generate the billing graph with 95th % in a .png format for export?
If I didn’t have to provide the graph I’d be set with what’s available already. In fact, the billing table in the DB makes it even easier for me to pull the info we used to pull from Cacti.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Monday, December 4, 2017 10:37 AM To: 'Observium' observium@observium.org Cc: 'Observium' observium@observium.org Subject: Re: [Observium] Aggregate vs individual port graph maximum value & 95th % on bits graph
The 95th value from rrd is useless for billing purposes.
Adam.
Sent from BlueMail http://www.bluemail.me/r?b=11327
On 4 Dec 2017, at 16:52, Sean Pedersen <spedersen.lists@gmail.com mailto:spedersen.lists@gmail.com > wrote:
For question 2, I added the following to /opt/observium/html/includes/graphs/generic_multi_bits_separated.inc.php after line 146:
$rrd_options .= " LINE1:95thin#aa0000";
$rrd_options .= " LINE1:d95thout#aa0000";
$rrd_options .= " 'COMMENT: \n file://n '";
$rrd_options .= " 'COMMENT:95th %\n'";
$rrd_options .= " GPRINT:95thin:%6.2lf%s\n";
$rrd_options .= " GPRINT:95thout:%6.2lf%s\n";
This gets me what I need in a round-about fashion, but would obviously be overwritten the next time an update comes through for that file. I could change the output around a little bit to move the numbers up to the top of the legend with the rest of the stats, but didn’t want to make extensive changes to the file just for a proof of concept.
Unfortunately, the 95th % value is off by 6Mbps, so there’s probably some adjustments that still need to be made. Either that or it’s a byproduct of how the billing and aggregate ports graphs are generated – deltas vs. RRD info.
Alternatively, if there was an easy means to export the graphs that traffic accounting generates into a regular image with 95th % included, that would be even better.
From: Sean Pedersen [mailto:spedersen.lists@gmail.com] Sent: Thursday, November 30, 2017 11:01 AM To: observium@observium.org mailto:observium@observium.org Subject: RE: Aggregate vs individual port graph maximum value & 95th % on bits graph
Wanted to bump this – if anyone has time to take a quick look and let me know way or another, it would be really helpful. Trying to replace several aging Cacti servers and billing scripts with Observium and this is all that’s holding me back. ☹
From: Sean Pedersen [mailto:spedersen.lists@gmail.com] Sent: Tuesday, November 28, 2017 7:20 AM To: observium@observium.org mailto:observium@observium.org Subject: Aggregate vs individual port graph maximum value & 95th % on bits graph
I have two graph questions that I haven't been able to get an answer on via IRC, so I thought this might be easier since I can include more information up front:
1st Question: A 2-port aggregate graph (agg_bits.png) shows a maximum value based on :AVERAGE while individual port graphs (port1_bits.png, port2_bits.png) for the ports that make up the aggregate show a maximum value based on :MAX. Is this intentional? If not, would it be possible to remove or toggle graphing average vs. maximum data on individual port graphs? I think both data points are useful, but in general when providing graphs the 5-minute average the only data we’d want to show them. More data below.
2nd Question: The “bits_old” graph includes 95th % both graphed and in the legend. Would it be possible to get the same for the other bits graphs, or at minimum, just bits? I did some digging and didn’t find a means to use options via graphs.php to generate it myself.
Question 1 data:
An aggregate graph (bits) takes the :AVERAGE inbound and outbound of the two ports, using that data to create the graph and populate the legend (min/max/avg, etc.):
DEF:in0=/opt/observium/rrd/dce01.01.mmr01/port-10.rrd:INOCTETS:AVERAGE DEF:out0=/opt/observium/rrd/dce01.01.mmr01/port-10.rrd:OUTOCTETS:AVERAGE
DEF:in1=/opt/observium/rrd/dce02.01.mmr02/port-10.rrd:INOCTETS:AVERAGE DEF:out1=/opt/observium/rrd/dce02.01.mmr02/port-10.rrd:OUTOCTETS:AVERAGE
The individual ports use both :AVERAGE and :MAX.
DEF:outoctets=/opt/observium/rrd/dce01.01.mmr02/port-10.rrd:OUTOCTETS:AVERAGE
DEF:inoctets=/opt/observium/rrd/dce01.01.mmr02/port-10.rrd:INOCTETS:AVERAGE
DEF:outoctets_max=/opt/observium/rrd/dce01.01.mmr02/port-10.rrd:OUTOCTETS:MAX
DEF:inoctets_max=/opt/observium/rrd/dce01.01.mmr02/port-10.rrd:INOCTETS:MAX
(I didn't include all the CDEFs, AREAS, HRULES, etc. for brevity, but I have copies of each RRD command for reference, if needed.)
The "Max" value in the legend reflects the :AVERAGE-based maximum on the aggregate graph and the :MAX-based maximum on the individual graph. Because of this, when compared side-by-side, the values do not match.
Aggregate Max:
p1_in: 118.25Mb
p1_out: 31.95Mb
p2_in: 40.15Mb
p2_out: 2.61Mb
Port 1 Max:
p1_in: 304.39Mb
p1_out: 98.77Mb
Port 2 Max:
p2_in: 90.94Mb
p2_out: 14.05Mb
--
Thanks,
skpio
_____
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium