Thanks Adam. We changed the steps and ping from 300 seconds to 60 seconds and the ping from 20 down to 10. So now that error makes sense that it cannot find ping_11 because it doesn't exist since we only ping 10 times.

What would be the best option? Put pings back to 20 I suppose would work, but that tells me that if anyone else modifies their config to include less than 20 pings for whatever reason this would happen again.

Any thoughts on the best way to handle this? Can the reference rrd's be flexible to include different amounts of pings or can the integration parse the smokeping config to see what it is set to?

Robbie Wright

Siuslaw Broadband

541-902-5101

**For support issues, please email support@siuslawbroadband.com.**

On Thu, Feb 6, 2014 at 4:13 PM, Adam Armstrong <adama@memetic.org> wrote:

On 2014-02-06 10:03, Robbie Wright wrote:

Perfect, thanks Tom. Here's the Performance & Output section. If you
want the lengthy RRD command, let me know. A bit of Googling and we
tried just straight up deleting the RRD, which didn't work. We did
change the steps and pings in the smokeping config in the Database
config and we did also change the charts in the Presentation config to
match a little more closely with our other tools. Maybe Observium is
looking for specifically named charts (ie 3 days) and since we changed
the defaults it can't find the right template?

RRDTool Output: ERROR: No DS called 'ping11' in
'/var/lib/smokeping/pud-gw1_domain_net.rrd'

Because we don't parse the smokeping config files, we rely on there being a specific number of DS in the RRD file.

My reference RRDs have DS of uptime, loss, median and ping1 to ping20.

The RRA resolution doesn't matter, but the number of DS must match.

Thanks,
adam.

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium