Large Scale Cacti


Published on

Mike Lindsey's presentation for The Return of Not Nagios

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • First slide. Breathe. Now begins the fleshy monkey talky bits.
  • What you get after a FreeBSDpkg_add, a Redhat rpm –install, or apt-get, etc.
  • Extending graph coverage is easy. Go download a template, and if needed, drop a poller script in /usr/local/cacti/scripts/
  • Graphs
  • Really. Collect –everything-You can never graph too much. You can overdue your Notification system, but you cannot overdo your historical trending data.
  • Sure. Ice Cream.Build sets of graphs from a dozen metrics, in about 20 seconds.
  • Migrating from the PHP Poller, to a compiled C poller gives a huge boost in performance, at the cost of a manageable amount of deployment effort.Install Boost, break the architecture up, and you can scale to quite well.
  • Aggregate graph creation plugin lets you get a more complete view of host clusters. If you have a more volatile environment and a static aggregate isn’t enough, alternate options exist allowing automated rebuild of aggregates.
  • Never deal with graph and tree creation again.
  • $ls –l /usr/local/cacti/cli/Most require you to run them via ‘php –q ./cli/script’.. All have –help. Read the docs.If you have a host database or a cmdb with an export function, or even a zone file with well named hostnames, and you can parse that in a script, wrapped around the cli tools, you can end up with a fully automated self-managing Cacti install. It’s a great place to be.
  • With nearly three years of operation in an extensively monitored, multi-colo, global environment with approx 2000 monitored servers; multi-poller Cacti can be accomplished with recent versions, and small-scale unofficial patches.
  • Current dev branches include integrated functionality for distributed polling.
  • Threshold plugin works like a Mini Nagios, only without the Nagios. Nectar emails off scheduled reports. Both are simple, powerful, and effective.
  • For me, Cacti works best when I can easily get data back out. Pull it out, feed it into a dashboard, use it for Nagios plugins, feed it into your business logic. Looking at your data is great, but parsing it and interpreting it relative to other data to get a complete view of your environment or application is priceless. Or, at least, many companies will charge you a very large price for it.
  • Interactive server utilization Heatmap, thanks to James Gladstone, exported Cacti data, and Google Charts.
  • Poller1’s running a little hot. It’s also on a slightly smaller box, and doesn’t get any new load from automatically added devices. If it was a VM, I’d consider reducing its allocated memory.
  • Participate in the forums, Read the docs, Contribute, Do Awesome Things.
  • Large Scale Cacti

    1. 1. Large Scale CactiAggregation, Automation, CMDB Integration, Extending, Reporting, and Scaling<br />Mike Lindsey – IT Architect - Cisco<br />
    2. 2. Basic Cacti<br /><ul><li> Requires a host with a web</li></ul>Server, a database, and PHP<br /><ul><li> Gives you a pretty interface, some core monitoring templates, access control, and clicky-clicky editing tools
    3. 3. Useful documentation provided online. Large and active community forums.
    4. 4. It’ll get the job done for a few racks of uninteresting servers, but quickly becomes limiting for complex, large, or volatile environments.</li></li></ul><li>Templates<br />A sometimes complicated process, that someone else has probably done for you.<br />Hit the forums. Good templates are stickied at the top of the “Scripts & Templates” forum.<br />If you want to graph it, there are probably templates already.<br />If there are no pre-existing templates, you might still not need to create them.<br />
    5. 5. Graphs For Every Occasion<br />
    6. 6. Graphs For Every Occasion<br />
    7. 7. Graphs For Every Occasion<br />
    8. 8. Graphs For Every Occasion<br />
    9. 9. Graphs For Every Occasion<br />
    10. 10. Custom Data Collection<br />Downloaded scripts, custom PHP/Perl/Python/Bash/etc<br />$ ./script hostname<br />field1:123 field2:456 field3:1.0<br />Product MIBs, Net-SNMP extend variables..<br />Collect everything, graph it.<br /> Forum search: “automatic template generation”<br />
    11. 11. …icecream?<br />
    12. 12. Spine & Boost<br />Cactid - Compiled C poller<br />When 296 seconds from cmd.php isn’t enough.<br />Boost - Decoupled RRD updates<br />Remove local file system latency from polling times.<br />
    13. 13. Aggregate<br />
    14. 14. Aggregate<br />
    15. 15. Aggregate<br />
    16. 16. Aggregate<br />
    17. 17. Autom8Automatic Graph creation and Tree manipulation<br />
    18. 18. Command-Line Tools<br />.. Or, how to stop all the mouse-clicks, and make it work for you.<br />Add hosts<br />Add graphs to hosts<br />Add hosts to trees<br />Never manually add a host or graph again.<br />Or if CMDB integration isn’t your thing, check out the Discovery plugin!<br /><br />
    19. 19. Distributed Polling<br />Scale the bottleneck<br />Toss a poller vm in every colo?<br />
    20. 20. Going Global<br />
    21. 21. Notifications & Reporting<br />Thold plugin<br />Threshold templating, for simple but effective alerting.<br />Nectar plugin<br />Scheduled reports.<br />
    22. 22. Cacti as a Data Warehouse<br />Forum search or dig around GitHub!<br />
    23. 23. Extending<br />Add a little data export to Google Charts…<br />Credit: James Gladstone<br />
    24. 24. Extending<br />Add a little data export to Google Charts… get something awesome.<br />Credit: James Gladstone<br />
    25. 25. Aggregate<br />Autom8<br />Boost<br />Discovery<br />Nectar<br />Spine<br />Thold<br />CLI Tools<br />Templates<br />Forums<br />Participate<br />Contribute<br />Donate!<br />Cacti Developers:<br />Ian Berry<br />Tony Roman<br />Larry Adams<br />J.P. Pasnak, CD<br />Jimmy Conner<br />Reinhard Scheck<br />Andreas Braun<br />RRDTool:<br />Tobias Oetiker<br />me: Mike Lindsey mike@5dninja.netforums: gninja<br />