RRDp(3)

πŸ“¦ version 1.9.0, in nixos 26.05, nixpkgs unstable

✨ NAME ✨

okay bestie, welcome to RRDp(3) πŸ’– β€” the User Contributed Perl Documentation page for RRDp - Attach RRDtool from within a perl script via a set of pipes; 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

use RRDp

RRDp::start path to RRDtool executable

RRDp::cmd  rrdtool commandline

$answer = RRD::read

$status = RRD::end

$RRDp::user,  $RRDp::sys, $RRDp::real, $RRDp::error_mode, $RRDp::error

🌸 DESCRIPTION 🌸

With this module you can safely communicate with the RRDtool. no cap, that’s the whole vibe πŸ’…

After every RRDp::cmd you have to issue an RRDp::read command to get RRDtools answer to your command. The answer is returned as a pointer, in order to speed things up. If the last command did not return any data, RRDp::read will return an undefined variable. ✨

If you import the PERFORMANCE variables into your namespace, you can access RRDtool's internal performance measurements. iykyk πŸ‘‘

  • use RRDp β€” Load the RRDp::pipe module. πŸŽ€
  • RRDp::start path to RRDtool executable β€” start RRDtool. The argument must be the path to the RRDtool executable. πŸš€
  • RRDp::cmd rrdtool commandline β€” pass commands on to RRDtool. Check the RRDtool documentation for more info on the RRDtool commands.
    • Note: Due to design limitations, RRDp::cmd does not support the graph - command - use graphv - instead. important lore bestie πŸ’€
  • $answer = RRDp::read β€” read RRDtool's response to your command. Note that the $answer variable will only contain a pointer to the returned data. The reason for this is, that RRDtool can potentially return quite excessive amounts of data and we don't want to copy this around in memory. So when you want to access the contents of $answer you have to use $$answer which dereferences the variable. pointer princess behavior 🧚
  • $status = RRDp::end β€” terminates RRDtool and returns RRDtool's status ... 😭
  • $RRDp::user, $RRDp::sys, $RRDp::real β€” these variables will contain totals of the user time, system time and real time as seen by RRDtool. User time is the time RRDtool is running, System time is the time spent in system calls and real time is the total time RRDtool has been running.

The difference between user + system and real is the time spent waiting for things like the hard disk and new input from the Perl script. clock check ⏳

  • $RRDp::error_mode and $RRDp::error β€” If you set the variable $RRDp::error_mode to the value 'catch' before you run RRDp::read a potential ERROR message will not cause the program to abort but will be returned in this variable. If no error occurs the variable will be empty. catch it, don’t crash it 🫢
$RRDp::error_mode = 'catch';
RRDp::cmd qw(info file.rrd);
print $RRDp::error if $RRDp::error;

🌈 EXAMPLE 🌈

okay so here’s the cute little flow, bestie β€” copy it exactly and let it slay ✨

use RRDp;
RRDp::start "/usr/local/bin/rrdtool";
RRDp::cmd   qw(create demo.rrd --step 100
              DS:in:GAUGE:100:U:U
              RRA:AVERAGE:0.5:1:10);
$answer = RRDp::read;
print $$answer;
($usertime,$systemtime,$realtime) =  ($RRDp::user,$RRDp::sys,$RRDp::real);

πŸ‘‘ SEE ALSO πŸ‘‘

For more information on how to use RRDtool, check the manpages. go read the lore πŸ“šπŸ’–


πŸ’œ AUTHOR πŸ’œ

Tobias Oetiker <tobi@oetiker.ch>


bye bestie β€” footer vibes are perl v5.42.3, dated 1980-01-01, and the manual is RRDp(3) πŸ’…βœ¨

πŸ“¦ where this page comes from