On 27/10/2013 19:31, Adam Armstrong wrote:
And just for the record, this guy hasn't paid us shit, yet he still feels he has the right to repeatedly waste our time via multiple media. All the bullshit he's spewing here he's already done via Twitter, and I've already explained to him why he's wrong.
I tried to stay out of the discussion, but got a bit ticked off by the following: - "The individual behind Observium kept ..." - maybe it's just me, but I find that a little condescending. - "Move the poller to another language". Sure, know-it-all, not going to happen, feel free to start your own. - Cacti does it faster. Sure, but cacti doesn't poll everything we do.
Of course Adam can be an asshole, and he probably was, but never without a reason ;-) As most people realise though, once you've ticked him off you can forget him changing his mind about you before a cooldown period of ... undefined.
We're all pretty allergic to reiterating the same thing over and over again for no reason though.
They don't have a need for efficient polling of Juniper devices do it's very unlikely that it will ever make it into the code.
This isn't really a Juniper thing. But in any event, Tom uses Juniper stuff :)
Yup, but no switch stacks right now.
In any case I'd contact Juniper to fix their shit, because a simple 7x52 Dell Powerconnect stack takes 80 seconds to poll, and that's more than "300 ports" in the J-example taking 300+ seconds.
Shaving 1/3 off of shit by disabling 32bit counter bulkwalks doesnt make it less shit. 200 seconds is ridiculous.
Either way, a lot of BS in my mailbox that is wasting people's time for little gain or benefit.
Parallel polling is not possible in PHP, nor does it help in most cases, usually it hurts.
The strength, and in this case maybe partial weakness, of Observium is the intelligence and walking it uses to get data from devices; it's not a static list of OIDs fired off at a device using spined or whatever, like Cacti does. If you like the latter better, Adam told you where to go ;-)
I would be interested in which vendors are guilty of this and which
software versions are present.
Nice one, our code works very, very fast with Cisco switches with 1000s of ports (yay for bulkwalk, max-rep, etc), so I'd say Juniper is one that comes to mind ;-) (max-rep actually slows it down)
Tom