![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
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]