![](https://secure.gravatar.com/avatar/9110a6da739541b57a7a6cd7051fe472.jpg?s=120&d=mm&r=g)
Ok not sure what I am doing wrong here - there has to be a way to remove these unwanted nics.
So you can see info here
I have this in my config.php
// bad interfaces $config['bad_if'][] = "NC-8100w";
I have gone into the database directly and marked the interfaces deleted. But they just get readded, delete gets removed - see the event log in the above screenshots.
So I have turned off discovery for the device, and gone into the database and deleted the records of the intefaces. Which works for a bit - but then they show up again. This is a brother HL-3170cdw printer.. I don't know how I would delete the interface on the device directly.
How do I remove these wireless interfaces from what observium shows. This printer will never use the wireless interfaces it has. So how do I remove them from observium showing them?
You would think if I disable discovery of ports, and then delete them from the database they would never get put back.. But clearly they do - is there some step I am missing?
If you need any other info just please ask.
TIA
![](https://secure.gravatar.com/avatar/9110a6da739541b57a7a6cd7051fe472.jpg?s=120&d=mm&r=g)
figured it out.. the bad_if needs to be all lowercase!! Arrrgghh, now they go away and I can purge them.
On Fri, Mar 28, 2014 at 1:41 PM, John Poznicek johnpoz@gmail.com wrote:
Ok not sure what I am doing wrong here - there has to be a way to remove these unwanted nics.
So you can see info here
I have this in my config.php
// bad interfaces $config['bad_if'][] = "NC-8100w";
I have gone into the database directly and marked the interfaces deleted. But they just get readded, delete gets removed - see the event log in the above screenshots.
So I have turned off discovery for the device, and gone into the database and deleted the records of the intefaces. Which works for a bit - but then they show up again. This is a brother HL-3170cdw printer.. I don't know how I would delete the interface on the device directly.
How do I remove these wireless interfaces from what observium shows. This printer will never use the wireless interfaces it has. So how do I remove them from observium showing them?
You would think if I disable discovery of ports, and then delete them from the database they would never get put back.. But clearly they do - is there some step I am missing?
If you need any other info just please ask.
TIA
![](https://secure.gravatar.com/avatar/a5d6cf95d845319b33e8cc33db759d20.jpg?s=120&d=mm&r=g)
Why not just ignore them so you aren’t alerted but can see graphs if need be?
-- Sincerely, Joshua Hopper, A+ CE Network Administrator [cid:image001.jpg@01CF4AC2.50E54FB0] 420 3rd Ave NW Hickory NC 28601 Office: 828-449-1839x2160 | Cell: 828-855-7565
From: observium [mailto:observium-bounces@observium.org] On Behalf Of John Poznicek Sent: Friday, March 28, 2014 2:41 PM To: Observium Network Observation System Subject: Re: [Observium] delete ports?
Ok not sure what I am doing wrong here - there has to be a way to remove these unwanted nics. So you can see info here
http://imgur.com/a/XNhO4 I have this in my config.php
// bad interfaces $config['bad_if'][] = "NC-8100w"; I have gone into the database directly and marked the interfaces deleted. But they just get readded, delete gets removed - see the event log in the above screenshots. So I have turned off discovery for the device, and gone into the database and deleted the records of the intefaces. Which works for a bit - but then they show up again. This is a brother HL-3170cdw printer.. I don't know how I would delete the interface on the device directly. How do I remove these wireless interfaces from what observium shows. This printer will never use the wireless interfaces it has. So how do I remove them from observium showing them? You would think if I disable discovery of ports, and then delete them from the database they would never get put back.. But clearly they do - is there some step I am missing? If you need any other info just please ask.
TIA
Protect Plus Air Holdings, LLC and Affiliates, Protect Plus, LLC and Affiliates, Imagine One Resources, LLC and Affiliates, Protect Plus Surfaces, LLC and Affiliates Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
![](https://secure.gravatar.com/avatar/9110a6da739541b57a7a6cd7051fe472.jpg?s=120&d=mm&r=g)
"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
![](https://secure.gravatar.com/avatar/21caf0a08d095be7196a1648d20942be.jpg?s=120&d=mm&r=g)
Hi,
Thanks for your ever so kindly worded, productive e-mail, as usual.
Reading all your posts, It sure looks like you are not our target audience. Deleting ports makes no sense, having a web interface button for it makes even less sense.
You could, perhaps, remove yourself from this antiquated mailing list, and join our superduper modern forum, which we of course have, like all great monitoring products: http://tinyurl.com/observiumforum
Kind regards, Tom
On 29/03/2014 14:23, John Poznicek wrote:
"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 mailto: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 <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
![](https://secure.gravatar.com/avatar/9110a6da739541b57a7a6cd7051fe472.jpg?s=120&d=mm&r=g)
I want to say thanks for such a productive link -- maybe that product has better support ;)
http://tinyurl.com/sweetthankyou
With no help from you or anyone on the list, I have it worked out while providing the info back on how it was accomplished.. Which you would think would be welcome to a list for users of product to help each other..
I would really love to hear why not listing the nonsense windows sends back via snmp makes no sense? Really you want interfaces listed showing nothing and just taking up space? Windows show 19 interfaces via snmp - while there is actually 1 that is in use and showing data. Listing them all is just beyond stupid!!
On Sat, Mar 29, 2014 at 2:01 PM, Tom Laermans tom.laermans@powersource.cxwrote:
Hi,
Thanks for your ever so kindly worded, productive e-mail, as usual.
Reading all your posts, It sure looks like you are not our target audience. Deleting ports makes no sense, having a web interface button for it makes even less sense.
You could, perhaps, remove yourself from this antiquated mailing list, and join our superduper modern forum, which we of course have, like all great monitoring products: http://tinyurl.com/observiumforum
Kind regards, Tom
On 29/03/2014 14:23, John Poznicek wrote:
"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
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
On 2014-03-29 19:07, John Poznicek wrote:
I want to say thanks for such a productive link -- maybe that product has better support ;)
http://tinyurl.com/sweetthankyou [3]
With no help from you or anyone on the list, I have it worked out while providing the info back on how it was accomplished.. Which you would think would be welcome to a list for users of product to help each other..
I would really love to hear why not listing the nonsense windows sends back via snmp makes no sense? Really you want interfaces listed showing nothing and just taking up space? Windows show 19 interfaces via snmp - while there is actually 1 that is in use and showing data. Listing them all is just beyond stupid!!
Our target market is service providers and telcos monitoring primarily carrier-grade network devices and the occasional server. Cisco is by far our most commonly monitored device.
In such environments it's anathema to purposefully remove information, because everything is useful. We automate as much as possible because humans forget to add things to their monitoring system. We make it purposefully difficult to remove things because there are rarely instances where you'd want to do that in an service provider environment.
You'll also find that people who work at SPs rarely have time to micro-manage their monitoring system, thus our approach of "graph everything, look at it if you need it".
We take the approach that as default we don't want to ignore too much, but we certainly provide methods to do it in the config. Users with large windows environments can easily mask the commonly existing interface types they don't want to see either by ifDescr or ifType.
adam.
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
ADAMA ANGRY
ADAMA SMASH
On 2014-03-29 13:01, Tom Laermans wrote:
Hi,
Thanks for your ever so kindly worded, productive e-mail, as usual.
Reading all your posts, It sure looks like you are not our target audience. Deleting ports makes no sense, having a web interface button for it makes even less sense.
You could, perhaps, remove yourself from this antiquated mailing list, and join our superduper modern forum, which we of course have, like all great monitoring products: http://tinyurl.com/observiumforum [2]
Kind regards, Tom
On 29/03/2014 14:23, John Poznicek wrote:
"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 [1]
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [1]
Links:
[1] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2] http://tinyurl.com/observiumforum
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/21caf0a08d095be7196a1648d20942be.jpg?s=120&d=mm&r=g)
We appear to have reached a strange crossover point a while ago where we switched good cop/bad cop roles. ;-)
MET VRIENDELIJKE GROETEN, TOM
On 30/03/2014 03:41, Adam Armstrong wrote:
ADAMA ANGRY
ADAMA SMASH
On 2014-03-29 13:01, Tom Laermans wrote:
Hi,
Thanks for your ever so kindly worded, productive e-mail, as usual.
Reading all your posts, It sure looks like you are not our target audience. Deleting ports makes no sense, having a web interface button for it makes even less sense.
You could, perhaps, remove yourself from this antiquated mailing list, and join our superduper modern forum, which we of course have, like all great monitoring products: http://tinyurl.com/observiumforum [2]
Kind regards, Tom
On 29/03/2014 14:23, John Poznicek wrote:
"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 [1]
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [1]
Links:
[1] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2] http://tinyurl.com/observiumforum
observium mailing list 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 (4)
-
Adam Armstrong
-
John Poznicek
-
Josh Hopper
-
Tom Laermans