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
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
One trick is to create a port group of the old port and the new port and graph the traffic of the port group. This way you will generate one graph with both the new and old data combined.
Den ons 10 feb. 2021 10:38Klimek, Denis via observium < observium@observium.org> skrev:
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
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
[image: ig] https://www.instagram.com/azubiteam/[image: 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 _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I've found that copying over the rrd to be the most reliable way to maintain history.
If I've migrated a port and forgotten to copy the rrd at the time, then I just do an rrdmerge of the two ports later to collate the data together.
It also means that you can delete/purge the original rrd if that port is going to be re-purposed for another use and you don't want the history polluting that graph.
M
On 10 Feb 2021, at 8:50 pm, Markus Klock via observium observium@observium.org wrote:
One trick is to create a port group of the old port and the new port and graph the traffic of the port group. This way you will generate one graph with both the new and old data combined.
Den ons 10 feb. 2021 10:38Klimek, Denis via observium <observium@observium.org mailto:observium@observium.org> skrev: 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 http://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 http://dklimek@stadtwerke-norderstedt.de/ www.wilhelm-tel.de http://www.wilhelm-tel.de/
Postanschrift:
wilhelm.tel http://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
https://www.instagram.com/azubiteam/ https://www.facebook.com/wilhelmtel.norderstedt/
Von: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> Im Auftrag von Arne Van Theemsche via observium Gesendet: Mittwoch, 10. Februar 2021 09:39 An: observium@observium.org mailto:observium@observium.org Cc: Arne Van Theemsche <arnevt@gmail.com mailto: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
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium <image002.png><image003.png><image004.png><image004.png>_______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (4)
-
Arne Van Theemsche -
Klimek, Denis -
Markus Klock -
Michael