- observium - lists.observium.org

Device Commets and notes
by Andy Lemin 02 Sep '16

02 Sep '16

Hi, I can see that a ticket has been raised for adding a place to add comments and notes to devices on ticket OBSERVUM-249 http://jira.observium.org/browse/OBSERVIUM-249 The workaround is to use the Description field. However this field is too small to store much useful info, and cannot be read easily as the field does not expand to show more characters. It would be really nice to have the field be able to show all our device notes, currently you can see the information is clipped beyond 65 CHARS as seen below in this example; Thanks and keep up the great work (we love Observium here) :) Cheers, Andy *Linux ar1406 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64* Description Old Hypervisor running some networking VMs etc. The disk mode is Hardware Generic x86 [64bit] Operating system Linux 3.16.0-4-amd64 System name ar1406 Contact Me <me(a)example.org> Location Sitting on the Dock of the Bay Uptime 106 days, 20h 10m 13s

1 0

IPMI
by Laurence Mayer 02 Sep '16

02 Sep '16

Hi, I have two servers both with IPMI ports enabled and working. Within Observium I have configured the IPMI Settings for both servers. For one of the servers Observium displays the relevant IPMI information (e.g, CPU Temp etc) however for the second server, the information is not displayed. Firmware are identical. I have confirmed the IPMI configuration a number of times and connectivity does not appear to be the issue. Anyway to troubleshoot this? Thanks Laurence

3 4

HP Storage
by ffuentes 01 Sep '16

01 Sep '16

Any plans on adding HP MSA 2040 as a supported device? The custom MIB from HP is available to the public. Regards, -- Fernando Fuentes Supervisor & Senior Systems Administrator Email: ffuentes(a)aasteel.com American Alloy Steel, Inc. Houston, Texas Website: http://www.aasteel.com Phone: 713-744-4222 Fax: 713-300-5688

1 0

billing outbound/95th same values
by Gregory Storme 01 Sep '16

01 Sep '16

Hi, We configured a billing type CDR/95th, but notice the values for outbound & 95th percentile are the same.Screenshot of the historical usage overview: We have a subscription and this is on version 0.16.3.7703 (22nd March 2016).Today we updated to version 0.16.8.8068 (23rd August 2016). Is this a known issue or it something wrong on our side? Regards, Gregory

2 3

APC NetBotz. Support for 'Dry contact inputs'....?
by Henrik Cednert (Filmlance) 01 Sep '16

01 Sep '16

Hello Not sure if this is the proper channel for feature requests. But it would be awesome to have support for the ‘Dry contact inputs’ on the APC NetBotz devices. Still not sure how to do a proper likeable snmpwalk so someone will probably shake their head and wave their fist in fury over this one. But hey, at least I tired. =) Snmpwalk output: http://pastebin.com/qcV8vX98 That one have 4 connected ‘dry contact inputs’ and you can see their name under for instance ‘emsProbeConfigProbeName.<n>’, ‘emsProbeStatusProbeName.<n>’ and ‘emsInputContactConfigInputContactName.<n>’ and then some... Also normal state and current state are represented in that walk. This particular netbotz is in charge of switching to secondary cooling circuit and firing those pumps up in case of failure on main circuit. So would be really nice to have that monitored in Observium. =) Cheers and thanks Ps. If my snmpwalk sucks, tell me once and for all how to do it and how it is supposed to look. =) -- Henrik Cednert cto | compositor Filmlance International | www.filmlance.se mobile [ + 46 (0)704 71 89 54 ] skype [ cednert ]

1 0

PHP Error
by Nurbek Suleimanov 01 Sep '16

01 Sep '16

Hi, support! Please help me, about this problem, when i make discovery all device, i see always this error: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 22 bytes) in /opt/observium/includes/snmp.i Thanks best regard Nurbek

3 10

Not seeing unix system graphs
by Glenn Cooper 31 Aug '16

31 Aug '16

I’ve got a CentOS 6.7 VM (that runs my Observium instance, currently at version 8068-stable) that I’m trying to monitor with the unix agent described here: http://www.observium.org/docs/unix_agent/ Installation of the agent went fine, as did the telnet testing from the host itself. I got a bunch of data via telnet. Also, SNMP has already been configured on the server and it’s polling itself properly (as far as I can tell) From my Observium web page, I see the system and can some details for it. The Overview shows me high level system info (kernel version, hostname, Location, uptime, etc) and the Event Log. Graphs only show Agent Execution Time, Ping Response, SNMP Response, and Poller Duration. From looking at the live demo on the Observium website, I’m assuming I should be seeing a bunch of additional data (processors, memory, netstat data, load averages, etc, etc, etc). I’ve taken a look at the device configuration settings and can’t see anything that I’m missing. Any ideas for what to look at next will be much appreciated. Thanks, Glenn Cooper

4 5

Observium group alerting?
by Andrew.Jones＠kiewit.com 31 Aug '16

31 Aug '16

Can the grouping system be utilized for alerting at this time? Example: setup alert checker to monitor device status of a group of devices and send single alert if any of those devices goes down. Or is the grouping feature only used for information viewing and scheduled maintenance? We are looking at options for suppressing amount of alerts that can occur at some of our larger locations. Thanks for your help! [Description: Description: Description: Description: Description: Description: cid:image001.jpg@01CB9CF5.E087FC40] Andrew Jones Sr. IM Technician, Network Kiewit Corporation 12720 I st, Omaha, NE 68137 402-938-4402 402-214-2681 cell www.kiewit.com<http://www.kiewit.com>

1 0

Feature Request
by Mike Khalil 31 Aug '16

31 Aug '16

Hello, Can you guys integrate your next release with DataDog? Datadog has their API open source thanks, -- *Michael Khalil* | System Administrator *CONTROLTEC* 999 Republic Drive, Suite 100, Allen Park, MI 48101 *P* 313.438.5107 *F* 313.982.1305 *www.control-tec.com <http://www.control-tec.com/>* *This e-mail, and any attachments, is intended solely for use by the addressee(s) named above.* *It may contain confidential or proprietary information of Control-Tec LLC, its subsidiaries, affiliates or business partners.* *If you are not the intended recipient of this e-mail or are an unauthorized recipient of the information, you are hereby notified that any dissemination, distribution or copying of this e-mail or any attachments, is strictly prohibited.* *If you have received this e-mail in error, please immediately notify the sender by reply e-mail and permanently delete the original and any copies or printouts.* *Computer viruses can be transmitted via email.* *The recipient should check this e-mail and any attachments for the presence of viruses.* *Control-Tec LLC accepts no liability for any damage caused by any virus transmitted by this e-mail.*

1 0

bind_cache failing to write via RRDCached
by Robert Williams 31 Aug '16

31 Aug '16

Hi, Having a good time today…! Got another oddity since the upgrade of the Observium server itself to 16.04 unfortunately :( In summary, all servers running BIND (they are still on 14.04) have now got zero ‘cache content’ stats since the Observium server was upgraded on Tuesday. However, all the other BIND stats are working OK: [cid:image001.jpg@01D1D944.38CA7190] Looking at the debug output, it is getting the data fine, and it’s writing out the values to RRDCacheD OK. I tried disabling RRDCacheD – it started working straight away. So, it looks like RRDCacheD (version 1.5.5 under 16.04) is unhappy with writing the ‘Cache’ elements content output for BIND. If I had to guess, I’d say it’s either: 1) something to do with the quantity of DS elements within that RRD (all 42 of them) 2) something relating to the use of an “!” in the name of the elements (that’s a proper random guess) The write attempt is: mupdate /opt/observium/rrd/x.y.net/app-bind-23-cache-default.rrd N:6:3:::392500:799:13060:27296:825744:29:17815:555:67263:160:8::9660:2238:49:382:23:14:::::::259181:22:2::45094::26347::::::6715::::::: My old RRDCacheD config was: DISABLE=0 OPTS="-w 1800 -z 1800 -f 3600 -s www-data -l unix:/var/run/rrdcached.sock -j /var/lib/rrdcached/journal/ -F -b /opt/observium/rrd -B" MAXWAIT=30 ENABLE_COREFILES=0 The new config has different parameters, so I’ve setup as follows: DAEMON=/usr/bin/rrdcached WRITE_TIMEOUT=1800 WRITE_JITTER=1800 BASE_PATH=/opt/observium/rrd/ JOURNAL_PATH=/var/lib/rrdcached/journal/ PIDFILE=/var/run/rrdcached.pid SOCKFILE=/var/run/rrdcached.sock SOCKGROUP=www-data BASE_OPTIONS="-F -B" Does anyone know of anything which could cause this? Or a magic value in RRDCacheD like “maximum number of DS elements”…? Cheers, Robert Williams Custodian Data Centre Email: Robert(a)CustodianDC.com http://www.CustodianDC.com

2 3