FITB: Network graphing done right
1 like1,934 views
The document introduces FitB, a network monitoring tool designed for easy and precise port monitoring across switches using rrdtool. It emphasizes features like automatic discovery of ports, simple configuration, and detailed graphing capabilities. FitB aims to streamline the monitoring process with a user-friendly interface while being open source and adaptable.
FITB: Network graphing done right
- 1. FITB Network Graphing Done Right Laurie Denness http://laur.ie @lozzd
- 2. Monitoring • Everyone knows it’s important • “If it moves, graph it” - Me, 2009 • BTW: ##monitoringsucks on Freenode
- 3. What is your network doing? Saturating your network in unexpected places can cause unexpected problems
- 4. What is your network doing?
- 5. What we wanted • Every port, on every switch to be monitored • Previously this meant a lot of clicking and overhead to maintain • 1 minute polling interval, for extra detail • New switches to be monitored within minutes of them coming up
- 6. How hard can that be? • There are *a lot* of graphing solutions out there, old and new • Kept thinking to myself “can it really be this difficult” • Everyone has their own set of requirements
- 7. Introducing FITB • Fit-bee or “Fill in the Blank” • Based on RRDTool, same data structure as many other RRDTool based systems • Written in PHP
- 8. Feature Overview • Automatic Discovery • Every “up” port on every switch • Handles the ports going up/down and being renamed • Simple Config • One line to add a new switch • Precise, 1 minute polling
- 9. Feature Overview • Simple, but powerful interface • Search interface name, alias • Filters on every page to drill down • Monitors any combination of • bits/sec, packets/sec, errors/discards/sec
- 10. Getting Started • Some sort of webserver with PHP • and the PHP CLI • RRDTool • MySQL • Cron • Some devices to monitor
- 11. Installation • Get the code • Import the database schema • Set up cron • Make a safe place for your RRD files • Put a switch in the config • Resume looking at pictures of cats online
- 13. List of devices
- 14. Set time period (5 mins to months) List of devices
- 15. Set time period (5 mins to months) Refresh interval List of devices
- 16. Set time period Search (5 mins to months) Refresh interval List of devices
- 17. Set time period Search (5 mins to months) Refresh interval Graph type filter (bits, errors, packets) List of devices
- 18. Set time period Search (5 mins to months) Refresh interval Graph type filter (bits, errors, packets) List of devices Host filter
- 19. Adding a switch
- 20. Adding a switch prettyname Display Name
- 21. Adding a switch enabled Polling enabled? prettyname Display Name
- 22. Adding a switch enabled Polling enabled? showoninterface Display in GUI prettyname Display Name
- 23. Adding a switch enabled ip Polling enabled? IP or hostname showoninterface Display in GUI prettyname Display Name
- 24. Adding a switch enabled ip Polling enabled? IP or hostname showoninterface Display in GUI prettyname snmpcommunity Display Name SNMP details
- 25. Adding a switch enabled ip graphtypes Polling enabled? IP or hostname Graphs required showoninterface Display in GUI prettyname snmpcommunity Display Name SNMP details
- 40. What happens when a new port comes up? • Next polling run it will be added automatically • No config, no fuss
- 41. What if a port goes down? • All the pages have graphs ordered by last update • Keep stale things at the bottom out of the way • The graphs are marked as stale
- 42. What if a port goes down?
- 43. What if a port goes down? • The “stale” time is configurable • Config option to permanently delete old graphs
- 46. What else? • Dashboard support has been written • https://github.com/etsy/dashboard • Network Weathermap patch available
- 49. What next? • This is version 1 • Bugs? • Features? • Stacked graphs • Config editor • Less than 1 minute polling? • Open source!
- 51. FITB http://github.com/lozzd/FITB Laurie Denness http://laur.ie @lozzd
Editor's Notes
- #2: \n
- #3: We all know monitoring is important; lets not discuss how much here, Theo did a great job\nIf it moves graph it.. I’m the guy who graphs how many spaces are available in his local car parks so he knows when to go shopping\nMention if you want to discuss how much you hate your current monitoring solution, join #monitoringsucks on Freenode\n
- #4: Quickly explain the story of when Git maxed out the network and caused actual site issues\nGit is faster.. Network was only 1gbps links... So many deploys means more unit tests which means more git traffic which caused problems with apache\n
- #5: \n
- #6: Discuss briefly the requirements\n
- #7: Evaluating lots of different solutions, none of them tick every box.\n
- #8: Everyone pronounces everything wrong, who cares\n\n
- #9: \n
- #10: \n
- #11: \n
- #12: Go back to reading reddit\n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: Next slide is live demo if poss. Use sw306c, host web0086\n
- #20: Next slide is live demo if poss. Use sw306c, host web0086\n
- #21: Next slide is live demo if poss. Use sw306c, host web0086\n
- #22: Next slide is live demo if poss. Use sw306c, host web0086\n
- #23: Next slide is live demo if poss. Use sw306c, host web0086\n
- #24: Next slide is live demo if poss. Use sw306c, host web0086\n
- #25: Here’s what it looks like. Notice when you click on a host, you get everything on that host (all types all ports)\nNotice the filter in the top right has changed to show the host you selected. Now I’ll search for a host on this switch. \n
- #26: Here’s what it looks like. Notice when you click on a host, you get everything on that host (all types all ports)\nNotice the filter in the top right has changed to show the host you selected. Now I’ll search for a host on this switch. \n
- #27: Here’s what it looks like. Notice when you click on a host, you get everything on that host (all types all ports)\nNotice the filter in the top right has changed to show the host you selected. Now I’ll search for a host on this switch. \n
- #28: Notice now I’ve found all the results for the port matching web0086, which is in the search box. \nNow I can decide I only care about bits/sec and not about anything else, I change the dropdown filter at the top\n
- #29: Notice now I’ve found all the results for the port matching web0086, which is in the search box. \nNow I can decide I only care about bits/sec and not about anything else, I change the dropdown filter at the top\n
- #30: \n
- #31: An example of searching for an interface name across all hosts\n
- #32: An example of searching for an interface name across all hosts\n
- #33: An example of searching for an interface name across all hosts\n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n