Hi Adam,
I do not have any I/O issues on that box. As far as I understand the Observium graph.php all graphs are build in realtime when accessing the device on the web interface (rrdtool_graph in includes/graphs/graph.inc.php). The CPU issue is properly generated because the apache2 has to generate about 2.4K (I currently have about 2.4K interfaces on that system) with rrdtool.
I'll search for a workaround to avoid apache generating all that access layer graphs. If I do not find one I'll switch over to mrgt.
With best Regards, Philip Möller
Von: observium-bounces@observium.org [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong Gesendet: Montag, 16. April 2012 15:23 An: Observium Network Observation System Betreff: Re: [Observium] Remove ports from Web Overview
It sounds like you have enough RAM to fit all of the RRDs in a RAM disk. We'd recommend doing this in preference to rrdcached, as rrdcached doesn't really gain very much at all.
adam.
On 2012-04-16 12:12, Philip Möller wrote: Hi Adam,
I don't think that your answer is constructive in any kind. I'm running Observium on this box: 2x4 core Intel(R) Xeon(R) CPU E5620 @ 2.40GHz 24GB Memory Hardware RAID-10 I also use all performance tweaks (xcache / rrdached etc ) you suggest to use.
That is pretty much a potent box. I also understand that the idea of Observium is to avoid special configuration of certain ports. I just hoped that there might be a way to fix my issues that are properly not related to Observium but to CISCOs way to handle their new FEX system (report all Ports without a FEX index on one device is pretty bad ) in any way. Your answer could have been more constructive even if you do not have a solution and do not want to add a solution for this issue.
With best regards, Philip Möller
Von: observium-bounces@observium.orgmailto:observium-bounces@observium.org [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong Gesendet: Montag, 16. April 2012 13:04 An: Observium Network Observation System Betreff: Re: [Observium] Remove ports from Web Overview
Buy a faster server.
Adam. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. "Philip Möller" <p.moeller@bigpoint.netmailto:p.moeller@bigpoint.net> wrote: Hi,
I have a performance issue with the Observium Web Interface. The Apache2 webserver needs about 4-5 minutes to load all graphs of some devices. The devices are CISCO NEXUS 5548 switches with CISCO NEXUS 2248 FEX (Fabric Extenders). One 5548 switch will have about 7488 Interfaces when fully populated (48 local interfaces + 48 local virtual interfaces + 24 * 52 + 52 interfaces for the extenders). I do not need to monitor or graph all the edge / access layer ports but only the backbone ports ( 144 ports ). As far as I understand the documentation all ports flagged as disabled are not polled any more and all ports that are deleted are not shown by the Apache2. Unfortunately the poller.php run updates disabled = 0 for all ports found on the device and they are back in the web interface overview. I cannot find the statement in the poller.php debug output but all Ports with deleted = 1 set manually are updated to deleted = 0 after a poller.php run. My question is if there is any way to delete available ports I do not want to have in the web overview or to drain those ports from the web interface.
With bet regards,
--- Philip Möller Senior Linux Systemadministrator International IT Operations
Bigpoint GmbH Drehbahn 47-48 20354 Hamburg | Germany
Tel: +49(0)40.88 1413-356 Cell: +49(0)151 27471095 E-Mail: p.moeller@bigpoint.netmailto:p.moeller@bigpoint.net --- CEO: Heiko Hubertz Business Registration: HRB-Hamburg 94148
_______________________________________________
observium mailing list
observium@observium.orgmailto:observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium