"Removing such trivial things is quite contra to the design goals of Observium."

What?  Really??  So I need to see 19 interfaces for my windows machine because I see crap like this in its interface list?  Because windows snmp is pretty much broken..

Name/OID: ifDescr.1; Value (OctetString): Software Loopback Interface 1
Name/OID: ifDescr.2; Value (OctetString): WAN Miniport (SSTP)
Name/OID: ifDescr.3; Value (OctetString): WAN Miniport (L2TP)
Name/OID: ifDescr.4; Value (OctetString): WAN Miniport (PPTP)
Name/OID: ifDescr.5; Value (OctetString): WAN Miniport (PPPOE)
Name/OID: ifDescr.6; Value (OctetString): WAN Miniport (IPv6)
Name/OID: ifDescr.7; Value (OctetString): WAN Miniport (Network Monitor)
Name/OID: ifDescr.8; Value (OctetString): WAN Miniport (IP)
Name/OID: ifDescr.9; Value (OctetString): RAS Async Adapter
Name/OID: ifDescr.10; Value (OctetString): WAN Miniport (IKEv2)
Name/OID: ifDescr.11; Value (OctetString): Broadcom NetLink (TM) Gigabit Ethernet
Name/OID: ifDescr.12; Value (OctetString): DW1501 Wireless-N WLAN Half-Mini Card
Name/OID: ifDescr.14; Value (OctetString): TAP-Windows Adapter V9
Name/OID: ifDescr.15; Value (OctetString): Broadcom NetLink (TM) Gigabit Ethernet-QoS Packet Scheduler-0000
Name/OID: ifDescr.16; Value (OctetString): Broadcom NetLink (TM) Gigabit Ethernet-WFP LightWeight Filter-0000
Name/OID: ifDescr.17; Value (OctetString): WAN Miniport (IPv6)-QoS Packet Scheduler-0000
Name/OID: ifDescr.18; Value (OctetString): WAN Miniport (IP)-QoS Packet Scheduler-0000
Name/OID: ifDescr.19; Value (OctetString): WAN Miniport (Network Monitor)-QoS Packet Scheduler-0000

So I got them removed, once I figured out you have to use lowercase.  Even though the documentation on the observium site shows "STRING" with no mention of case, etc.

$config['bad_if'][] = "wan miniport (sstp)";
$config['bad_if'][] = "wan miniport (l2tp)";
$config['bad_if'][] = "wan miniport (pptp)";
$config['bad_if'][] = "wan miniport (pppoe)";
$config['bad_if'][] = "wan miniport (ipv6)";
$config['bad_if'][] = "wan miniport (network monitor)";
$config['bad_if'][] = "wan miniport (ip)";
$config['bad_if'][] = "wan miniport (ikev2)";
$config['bad_if'][] = "tap-windows adapter v9";
$config['bad_if'][] = "broadcom netlink (tm) gigabit ethernet-wfp lightweight filter-0000";
$config['bad_if'][] = "software loopback interface 1";
$config['bad_if'][] = "lo";
$config['bad_if'][] = "vmxnet3 ethernet adapter-wfp lightweight filter-0000";

What should be trivial is the way to delete this noise.. Why can there not be a simple delete interface button?  I saw some thread mention security - come on give me a break, only the ADMIN of observium would have access to do it - so its BS that it would be security issue to delete interfaces you don't want to track.

So its looking much cleaner now..  Noise is gone..  I can understand leaving an interface that may be used on and off, etc.  Like my raspberry pi I have both the wired and the wifi interface - even though wired is currently not being used.  But I sure don't need wan miniport (pppoe) on my windows machine that is only used as file server.

If there was actual forums I would be happy to create a guide, but seems only antiquated mailing lists?  How about a wiki for users to help maintain/improve documentation/howto's, etc.  But can not seem to find such basic tools - but this project has been in the works for 7 years if I read the info I found correctly.


On Fri, Mar 28, 2014 at 9:01 PM, Adam Armstrong <adama@memetic.org> wrote:
On 2014-03-28 18:14, Josh Hopper wrote:
Why not just ignore them so you aren’t alerted but can see graphs if need be?

Yes, one must really ask:

Why do you care?

Removing such trivial things is quite contra to the design goals of Observium.

adam.

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