Except for a few well-known and
long-standing issues (alerting, mostly), most things you'll notice
will be fixed before you notice them. :>
This is because the developers run the current release on their
production systems, so we catch bugs pretty quickly. No one hates
gaps in graphs more than we do. :D
adam.
On 22/06/2012 00:06, Morgan McLean wrote:
I know it isn't compiled, I guess thats just habit
from work :).
I wasn't even sure this was a bug when I emailed in,
I thought maybe I didn't have a flag set. The documentation on
sensors was a bit wonky.
I do see some notes regarding some of the things I mentioned,
so I will svn update and see how that goes. Sorry, this project
is more active than I originally thought!
Morgan
On Thu, Jun 21, 2012 at 3:55 PM, Adam
Armstrong <adama@memetic.org>
wrote:
a) there are no 'builds', observium is not compiled.
rule #1 of reporting bugs is that you make sure the bug
isn't fixed before you report it.
adam.
On 21/06/2012 23:49, Morgan McLean wrote:
I checked out the most recent
build from SVN monday or tuesday.
This is literally all juniper gear. EX
switches, SRX firewalls, MX routers
A server I have added does this:
2012-06-21 12:38:16SystemProcessor
added: type hr index 805 descr Intel Xeon E7540
@ 2.00GHz
2012-06-21 06:38:20SystemProcessor
added: type hr index 805 descr Intel Xeon E7540
@ 2.00GHz
2012-06-21 00:38:34SystemProcessor
added: type hr index 805 descr Intel Xeon E7540
@ 2.00GHz
2012-06-20 18:38:25SystemProcessor
added: type hr index 805 descr Intel Xeon E7540
@ 2.00GHz
2012-06-20 12:38:22SystemProcessor
added: type hr index 805 descr Intel Xeon E7540
@ 2.00GHz
an APC managed 0u strip looks like:
21/Jun/12 12:38:13
Sensor Added: current apc 1 Output
21/Jun/12 12:38:12
Sensor
Added: voltage apc 1 Input
21/Jun/12 12:38:12
Sensor
Added: voltage apc 1 Input
21/Jun/12 06:38:17
Sensor
Added: current apc 1 Output
21/Jun/12 06:38:16
Sensor
Added: voltage apc 1 Input
21/Jun/12 06:38:16
Sensor
Added: voltage apc 1 Input
21/Jun/12 00:38:32
Sensor
Added: current apc 1 Output
21/Jun/12 00:38:30
Sensor
Added: voltage apc 1 Input
21/Jun/12 00:38:29
Sensor
Added: voltage apc 1 Input
20/Jun/12 18:38:21
Sensor
Added: current apc 1 Output
On Thu, Jun 21, 2012 at
3:29 PM, Adam Armstrong <adama@memetic.org>
wrote:
Sounds like nonsense to me.
When did you last update?
adam.
On 21/06/2012 22:51, Morgan McLean
wrote:
The only thing
thats working in the memory graphing
for junos devices. Everything else is
seen by discovery but not acted on.
Inventory doesn't populate
either, but thats maybe another
topic.
Morgan
On Thu, Jun
21, 2012 at 2:02 PM, Adam
Armstrong <adama@memetic.org>
wrote:
Hmm. Did tom not already
fix this?
adam.
On 21/06/2012 21:25,
Adam Armstrong wrote:
Hmm. I think I have
the same problem
elsewhere
(processors), and I
think I know what it
is.
Let me fix it :)
adam.
On 21/06/2012 21:21,
Morgan McLean wrote:
My
logs look like
this...any idea why
its not picking up? I
have about 50 juniper
devices, an APC device
and a couple others
and it doesn't seem to
monitor or graph any
of the sensors. I have
seen some information
about sensor
configuration under
config.php, but it
wasn't very helpful.
Every time the
discovery runs, or
maybe its the
poller, not sure, it
finds all these
sensors for every
device, but it does
nothing with them.
Is there a switch
I need to flip?
Thanks!
Morgan
21/Jun/12
12:39:04
Sensor Added:
temperature
junos 6.1.0.0
TFEB MX80
21/Jun/12
12:39:04
Sensor
Added:
temperature
junos 6.1.1.0
TFEB Intake
21/Jun/12
12:39:04
Sensor
Added:
temperature
junos 9.1.0.0
Routing Engine
21/Jun/12
12:39:03
Processor
added: type
junos index
6.1.0.0 descr
TFEB MX80
21/Jun/12
12:39:03
Processor
added: type
junos index
7.1.0.0 descr
FPC @ 0/*/*
21/Jun/12
12:39:03
Processor
added: type
junos index
7.2.0.0 descr
FPC @ 1/*/*
21/Jun/12
12:39:03
Processor
added: type
junos index
9.1.0.0 descr
Routing Engine