API example code to get graphs

pozar · 9 March 2017 16:07

I am one of the co-founders of a peering fabric (Internet eXchange) in the San Francisco CA area. We wanted a way to pull daily and weekly graphs out of LibreNMS to display on our web site. I first ran rrdtool to create this on the LibreNMS box and then transferred these to the web site but found that a bit cumbersome. In drilling into the LibreNMS, I found I could get nearly everything I wanted via the API. Of course some of this is not documented so I had to dig through the code to find what I wanted.

One thing that was handy here was leveraging Libre’s concept of groups here to use this to identify ports I wanted to aggregate up. These are identified as “peering” in this script.

Additionally there doesn’t seem to be a way to add a title to a graph but I resolved that by using Imagemagick’s “convert” on the image I got via the API.

You can see the script at:

github.com

pozar/sysadmin_scripts/blob/master/create_public_graphs.sh

#!/bin/bash
#
# Creates the aggregate traffic graphs for the web site. See: 
# https://www.sfmix.org/services/statistics
# 
# Meant to be run on the web site and call out to the LibreNMS API.
# One thing that was handy here was leveraging Libre's concept of 
# groups here to use this to identify ports we wanted to aggregate up. 
# These are identified as "peering" in this script.
#
# The script should be added to cron with something like:
# */5 * * * * /usr/local/sbin/create_public_graphs.sh > /dev/null 2>&1 

export TZ="UTC"
caldate=`date +'%Y/%m/%d %H:%M'`
now=`date +%s`
daysecs=86400
weeksecs=604800
dayago=$((now - daysecs))
weekago=$((now - weeksecs))

This file has been truncated. show original

laf · 9 March 2017 16:13

I’m not sure if their’s a question in here or not

However this API call gets your peering graphs: http://docs.librenms.org/API/API-Docs/#api-route-get_graph_by_portgroup

pozar · 9 March 2017 17:07

No question. Just a post and pointer to a solution that we found for SFMIX. The code pointed to also shows some API arguments that are not (well) documented but are in the LibreNMS code that we found useful.

Goldie · 9 March 2017 21:02

Your link is broken, I get a 404.

laf · 9 March 2017 23:44

If you can improve the docs then please submit pull requests

pozar · 10 March 2017 05:51

My apologies. That repro was private. It is now public.

pozar · 10 March 2017 05:52

Heh… Back in the FidoNet days. it was “Send code”. Will do.

laf · 10 March 2017 09:33

This is an open source project and relies on people contributing to make it work