![](https://secure.gravatar.com/avatar/aafc0bcc6e27a9411007ffa1005a653a.jpg?s=120&d=mm&r=g)
I would like to ensure that interface names conform to certain standard. I'm stuck at 'Check Conditions' phase of making an alert.
If I understand everything right, then there's no ifName metric available for a match condition, or am I doing something else wrong?
Any suggestions? If I'm right, then can ifName be added as a metric?
![](https://secure.gravatar.com/avatar/21caf0a08d095be7196a1648d20942be.jpg?s=120&d=mm&r=g)
Hi,
IfName isn't a metric, it's not something that changes imo - it's an entity match attribute. I don't think we'll add it as a metric (I'll let Adam chime in) - as a workaround you could entity (not)match ifname and then add a bogus always-true check condition to have your alert fire, perhaps?
Tom
On 27/05/2014 18:53, Paweł Tyll wrote:
I would like to ensure that interface names conform to certain standard. I'm stuck at 'Check Conditions' phase of making an alert.
If I understand everything right, then there's no ifName metric available for a match condition, or am I doing something else wrong?
Any suggestions? If I'm right, then can ifName be added as a metric?
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/aafc0bcc6e27a9411007ffa1005a653a.jpg?s=120&d=mm&r=g)
Hello Tom,
I've added $port['alert_array']['ifName'] = $port['ifName']; in ports.inc.php just to see if it all works as I wanted and -- yes, it does exactly what I need.
I of course agree this is not the right way of doing it, because it adds needless work every poll (which I'm doing every minute, instead of usual five) -- which brings me to next question, and I would be perfectly happy with checking it every hour.
Maybe Alerting facility could be extended with some low-load low-severity alert class, which gets checked every n poll cycles? Or some option similar to Alert Delay, like Check Interval.
Thank you for your reply :)
PS. Observium is great. I'm using it for 3 days and already can't figure out how I managed without it so far :)
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
Seems like a bizarre thing to monitor. Are you doing this one some brain-dead platform that lets you change ifNames, like Extreme?
I don't think it's something which is particularly overhead-intensive, but it still strikes me as an odd thing to want to monitor.
adam.
On 2014-05-27 14:50, Paweł Tyll wrote:
Hello Tom,
I've added $port['alert_array']['ifName'] = $port['ifName']; in ports.inc.php just to see if it all works as I wanted and -- yes, it does exactly what I need.
I of course agree this is not the right way of doing it, because it adds needless work every poll (which I'm doing every minute, instead of usual five) -- which brings me to next question, and I would be perfectly happy with checking it every hour.
Maybe Alerting facility could be extended with some low-load low-severity alert class, which gets checked every n poll cycles? Or some option similar to Alert Delay, like Check Interval.
Thank you for your reply :)
PS. Observium is great. I'm using it for 3 days and already can't figure out how I managed without it so far :)
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/9113800bbd271c46f4585a9549d85c15.jpg?s=120&d=mm&r=g)
Pawel: you are not confusing ifName with ifDescr perhaps?
2014-05-28 8:43 GMT+02:00 Adam Armstrong adama@memetic.org:
Seems like a bizarre thing to monitor. Are you doing this one some brain-dead platform that lets you change ifNames, like Extreme?
I don't think it's something which is particularly overhead-intensive, but it still strikes me as an odd thing to want to monitor.
adam.
On 2014-05-27 14:50, Paweł Tyll wrote:
Hello Tom,
I've added $port['alert_array']['ifName'] = $port['ifName']; in ports.inc.php just to see if it all works as I wanted and -- yes, it does exactly what I need.
I of course agree this is not the right way of doing it, because it adds needless work every poll (which I'm doing every minute, instead of usual five) -- which brings me to next question, and I would be perfectly happy with checking it every hour.
Maybe Alerting facility could be extended with some low-load low-severity alert class, which gets checked every n poll cycles? Or some option similar to Alert Delay, like Check Interval.
Thank you for your reply :)
PS. Observium is great. I'm using it for 3 days and already can't figure out how I managed without it so far :)
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
![](https://secure.gravatar.com/avatar/aafc0bcc6e27a9411007ffa1005a653a.jpg?s=120&d=mm&r=g)
Pawel: you are not confusing ifName with ifDescr perhaps?
Nope; we are using lots of tunnels and they are named indicating customer names. I never was a fan of eth0, eth1, eth1337 and stuff and I use proper interface names that have sense to humans pretty much everywhere I can. Both FreeBSD and Mikrotik lets you name interfaces how you see fit. Unfortunately FreeBSD doesn't expose description in SNMP, which I'd love to use to describe customers (ID, bw).
Our use for Observium is mainly monitoring our access network and customers' CPEs.
![](https://secure.gravatar.com/avatar/aafc0bcc6e27a9411007ffa1005a653a.jpg?s=120&d=mm&r=g)
Seems like a bizarre thing to monitor. Are you doing this one some brain-dead platform that lets you change ifNames, like Extreme?
Worse. Mikrotik ;)
I don't think it's something which is particularly overhead-intensive, but it still strikes me as an odd thing to want to monitor.
Too many admins. Some of them have arbitrary approach to keeping things tidy ;>
participants (4)
-
Adam Armstrong
-
Markus Klock
-
Paweł Tyll
-
Tom Laermans