Hi,
Since our midnight svn up / rediscover, it appears that every port graph has moved the "Unicast Packets Out" data into the "Errors TX" graph?!
Images below:
This is on all devices on all port graphs, as far as I can see anyway...
Including on our test installation polling some lab devices, on a different VM.
Help please?
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
Robert,
Indeed, thanks for the report.
Fixed in r7784.
Tom
On 04/28/2016 10:18 AM, Robert Williams wrote:
Hi, Since our midnight svn up / rediscover, it appears that every port graph has moved the “Unicast Packets Out” data into the “Errors TX” graph?! Images below: This is on _all_ devices on _all_ port graphs, as far as I can see anyway… Including on our test installation polling some lab devices, on a different VM. Help please? Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Tom,
Thanks very much for that! – Do you have any pointers on a script to erase the time range from all the RRDs?
It’s messed up most of the long-term views for all the ports now:
[cid:image005.jpg@01D1A159.9F76F670] [cid:image006.jpg@01D1A159.9F76F670]
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: 28 April 2016 09:37 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Graph data failures
Robert,
Indeed, thanks for the report.
Fixed in r7784.
Tom On 04/28/2016 10:18 AM, Robert Williams wrote: Hi,
Since our midnight svn up / rediscover, it appears that every port graph has moved the “Unicast Packets Out” data into the “Errors TX” graph?!
Images below:
[cid:image002.jpg@01D1A159.0B0F7A20]
[cid:image003.jpg@01D1A159.0B0F7A20]
[cid:image004.jpg@01D1A159.0B0F7A20]
This is on all devices on all port graphs, as far as I can see anyway…
Including on our test installation polling some lab devices, on a different VM.
Help please?
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.commailto:Robert@CustodianDC.com http://www.CustodianDC.com
_______________________________________________
observium mailing list
observium@observium.orgmailto:observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Not easily possible to remove a time period, but you can use the spike remover stuff to try to get rid of that horrible spike in unicast packets.
adam. On 28/04/2016 14:24:34, Robert Williams robert@custodiandc.com wrote: Hi Tom, Thanks very much for that! – Do you have any pointers on a script to erase the time range from all the RRDs? It’s messed up most of the long-term views for all the ports now: Cheers! Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: 28 April 2016 09:37 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Graph data failures Robert,
Indeed, thanks for the report.
Fixed in r7784.
Tom On 04/28/2016 10:18 AM, Robert Williams wrote: Hi, Since our midnight svn up / rediscover, it appears that every port graph has moved the “Unicast Packets Out” data into the “Errors TX” graph?! Images below: This is on all devices on all port graphs, as far as I can see anyway… Including on our test installation polling some lab devices, on a different VM. Help please? Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com [mailto:Robert@CustodianDC.com] http://www.CustodianDC.com [http://www.CustodianDC.com]
_______________________________________________ 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]
Thanks - Will have a look and see what we can come up with here, anything useful and I’ll share :)
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: 28 April 2016 15:02 To: observium@observium.org Subject: Re: [Observium] Graph data failures
Not easily possible to remove a time period, but you can use the spike remover stuff to try to get rid of that horrible spike in unicast packets.
adam.
On 28/04/2016 14:24:34, Robert Williams <robert@custodiandc.commailto:robert@custodiandc.com> wrote: Hi Tom,
Thanks very much for that! – Do you have any pointers on a script to erase the time range from all the RRDs?
It’s messed up most of the long-term views for all the ports now:
[cid:image005.jpg@01D1A159.9F76F670] [cid:image006.jpg@01D1A159.9F76F670]
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.commailto:Robert@CustodianDC.com http://www.CustodianDC.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: 28 April 2016 09:37 To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] Graph data failures
Robert,
Indeed, thanks for the report.
Fixed in r7784.
Tom On 04/28/2016 10:18 AM, Robert Williams wrote: Hi,
Since our midnight svn up / rediscover, it appears that every port graph has moved the “Unicast Packets Out” data into the “Errors TX” graph?!
Images below:
[cid:image002.jpg@01D1A159.0B0F7A20]
[cid:image003.jpg@01D1A159.0B0F7A20]
[cid:image004.jpg@01D1A159.0B0F7A20]
This is on all devices on all port graphs, as far as I can see anyway…
Including on our test installation polling some lab devices, on a different VM.
Help please?
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.commailto:Robert@CustodianDC.com http://www.CustodianDC.com
_______________________________________________
observium mailing list
observium@observium.orgmailto:observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I'm sorry - I don't immediately have a clue on how to remove data. You could export to XML, remove a bunch of entries (or replace by NaN?) then import the XML again. It's manual labour I'm afraid though. Not sure if it's scriptable.
You could try running the removespikes script over the RRDs and see if they bring down the giant peak?
Tom
On 04/28/2016 03:24 PM, Robert Williams wrote:
Hi Tom,
Thanks very much for that! – Do you have any pointers on a script to erase the time range from all the RRDs?
It’s messed up most of the long-term views for all the ports now:
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Tom Laermans *Sent:* 28 April 2016 09:37 *To:* Observium Network Observation System observium@observium.org *Subject:* Re: [Observium] Graph data failures
Robert,
Indeed, thanks for the report.
Fixed in r7784.
Tom
On 04/28/2016 10:18 AM, Robert Williams wrote:
Hi, Since our midnight svn up / rediscover, it appears that every port graph has moved the “Unicast Packets Out” data into the “Errors TX” graph?! Images below: This is on _all_ devices on _all_ port graphs, as far as I can see anyway… Including on our test installation polling some lab devices, on a different VM. Help please? Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com <mailto:Robert@CustodianDC.com> http://www.CustodianDC.com _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong -
Robert Williams -
Tom Laermans