Hi Arne,
we are using the Billing Module to store important data of transit uplinks. Maybe this fits your requirements too?
Mit freundlichem Gruß wilhelm.tel GmbH
Denis Klimek Carrier Manager & Professional Network Engineer IP-Systemtechnik Tel: +49 (0) 40 / 521 04 – 1049 -> Work From Home Mobil: +49 (0) 151 / 652 219 06
dklimek@stadtwerke-norderstedt.de www.wilhelm-tel.de
______________________________________________
[cid:image004.png@01D6FF98.E1F65F20]
Postanschrift: wilhelm.tel GmbH Heidbergstraße 101-111 22846 Norderstedt
Geschäftsführer: Jens Seedorff, Theo Weirich Vorsitzender des Aufsichtsrats: Christoph Mendel Handelsregister: HRB 4216 NO, Amtsgericht Kiel Umsatzsteuer ID: DE 81 299 7663
[ig]https://www.instagram.com/azubiteam/[fb]https://www.facebook.com/wilhelmtel.norderstedt/
Von: observium observium-bounces@observium.org Im Auftrag von Arne Van Theemsche via observium Gesendet: Mittwoch, 10. Februar 2021 09:39 An: observium@observium.org Cc: Arne Van Theemsche arnevt@gmail.com Betreff: [Observium] best practices regarding interface switching and historical data
Hi,
I was wondering how you guys tackle the problem of changing the port of (e.g. your transit uplink) to another physical port & historical data. Since rrd's are stored under "port-<snmpid>" format, this event causes you by default to loose your historical data. Or even worse, you have to change your routing engine with a more recent version, and after replacing it seems all your snmp id's are changed.
this is certainly of importance for our interfaces which have a label that automatically creates aggregates graphs. How I do this until now is copying the rrd file to the new location, but this seems so... dirty
kind regards Arene
