Graphite Documentation Release 1.2.0
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Naemonbox Manual Documentation Release 0.0.7
NaemonBox Manual Documentation Release 0.0.7 NaemonBox Team September 16, 2016 Contents 1 Introduction 3 1.1 Target audience..............................................3 1.2 Prerequisite................................................3 2 About Naemonbox 5 2.1 Project..................................................5 2.2 Features..................................................6 3 Installation Guide 7 3.1 System requirements...........................................7 3.2 Recommended system requirements...................................7 3.3 Client Operating Systems........................................7 3.4 Openvz VPS installation.........................................8 3.5 GNU/Linux Debian 7 (or later) Installation...............................8 3.6 Installing Naemonbox..........................................8 4 Getting Started 9 4.1 Step one.................................................9 4.2 Step two................................................. 10 4.3 Step three................................................. 10 4.4 Step four................................................. 10 5 Configuring Naemon 11 5.1 Introduction............................................... 11 5.2 Actions.................................................. 11 5.3 Hosts Definition............................................. 12 5.4 Services.................................................. 13 5.5 Commands................................................ 14 5.6 Time periods............................................... 15 5.7 Contacts................................................ -
Munin Documentation Release 2.0.44
Munin Documentation Release 2.0.44 Stig Sandbeck Mathisen <[email protected]> Dec 20, 2018 Contents 1 Munin installation 3 1.1 Prerequisites.............................................3 1.2 Installing Munin...........................................4 1.3 Initial configuration.........................................7 1.4 Getting help.............................................8 1.5 Upgrading Munin from 1.x to 2.x..................................8 2 The Munin master 9 2.1 Role..................................................9 2.2 Components.............................................9 2.3 Configuration.............................................9 2.4 Other documentation.........................................9 3 The Munin node 13 3.1 Role.................................................. 13 3.2 Configuration............................................. 13 3.3 Other documentation......................................... 13 4 The Munin plugin 15 4.1 Role.................................................. 15 4.2 Other documentation......................................... 15 5 Documenting Munin 21 5.1 Nomenclature............................................ 21 6 Reference 25 6.1 Man pages.............................................. 25 6.2 Other reference material....................................... 40 7 Examples 43 7.1 Apache virtualhost configuration.................................. 43 7.2 lighttpd configuration........................................ 44 7.3 nginx configuration.......................................... 45 7.4 Graph aggregation -
Josh Malone Systems Administrator National Radio Astronomy Observatory Charlottesville, VA
heck What the #%!@ is wrong ^ with my server?!? Josh Malone Systems Administrator National Radio Astronomy Observatory Charlottesville, VA 1 Agenda • Intro to Monitoring • Internet protocols 101 • • Nagios SMTP • IMAP • Install/Config • HTTP • Usage • Custom plugins • Packet sniffing for dummies • Intro to Troubleshooting • Tools • telnet, openssl • grep, sed • ps, lsof, netstat 2 MONITORING 3 Automated Monitoring Workflow 4 Monitoring Packages: Open Source • • Pandora FMS • Opsview Core • Naemon • • • • • • Captialware ServerStatus • Core • Sensu All Trademarks and Logos are property of their respective trademark or copyright holders and are used by permission or fair use for education. Neither the presenter nor the conference organizers are affiliated in any way with any companies mentioned here. 5 Monitoring Packages: Commercial • Nagios XI • Groundwork • PRTG network monitor • CopperEgg • WhatsUp Gold • PRTG network monitor • op5 (Naemon) All Trademarks and Logos are property of their respective trademark or copyright holders and are used by permission or fair use for education. Neither the presenter nor the conference organizers are affiliated in any way with any companies mentioned here. 6 Why Automatic Service Monitoring? • Spot small problems before they become big ones • Learn about outages before your users do • Checklist when restoring from a power outage • Gives you better problem reports than users • Problems you might never spot otherwise • Failed HDDs in RAIDs • Full /var partitions • Logs not rotating • System temperature rising 7 Why Automatic Service Monitoring? • Capacity planning • Performance data can generate graphs of utilization • RAM, Disk, etc. • Availability reports - CAUTION • Easy to generate -- even easier to generate wrong • Make sure your configurations actually catch problems • Will also include problems with Nagios itself :( • If you’re going to quote your availability numbers (SLAs, etc.) make sure you understand what you’re actually monitoring. -
Rrdtool – Perl Module • Net::Snmptrapd(Install It from CPAN by Root) • Netsnmp::Agent(Embedded on Net-Snmp) Requirement – SNMP Agent
Homework 5 DNS、HTTPD、SNMP Requirements One dedicated domain name for yourself Setup DNS server with following records SOA, NS, MX Make them reasonable NS Delegation (with team mates) Dedicate a sub domain to each of your team mates Building a slave server for your team mate And a stub server for another team mate Updates should be synchronized Reverse resolution for your NAT 192.168.x.0/24 for each of team mates Requirements (Cont.) slave a.nctucs.net 140.113.a.a stub 192.168.0.1/24 b.nctucs.net c.nctucs.net 140.113.b.b 140.113.c.c 192.168.0.2/24 192.168.0.3/24 Requirements (Cont.) View Create view.example.csie.net A record: Queries from 192.168.0.0/24: view.example.csie.net A 192.168.0.1 Otherwise, get your normal ip Logging Record all records to /var/log/named.log Do log rotate Note: you will be asked for explaining the what does the log entry means in named.log Requirements (Cont.) SPF/DomainKeys record for your server Add resonable SPF/DomainKeys records Configure your mail system to support these feature SSHFP record for your server Make a reasonable setting Requirements (Cont.) Dynamic DNS update Your DNS should accept the update requests from 140.113.17.225 and your team mates You should know how to update a dns record Management Your DNS server should support TSIG and allow the connection from 140.113.17.225 Your DNS server should only allow the AXFR request from 140.113.17.225 Only allow recursion query from your team mates and 140.113.17.225 Appendix Use ldap as backend database dns/bind9-sdb-ldap http://www.openldap.org/ http://bind9-ldap.bayour.com/ SPF setup wizard http://old.openspf.org/wizard.html DKIMproxy http://dkimproxy.sourceforge.net HTTPD Requirements HTTPD apache, lighttpd, nginx, etc. -
Time Series Database (TSDB) Query Languages
Time Series Database (TSDB) Query Languages Philipp Bende [email protected] Abstract—Time series data becomes became more and One can define time series data by the following rules: more relevant since the so called 4th industrial revolution. A large amount of sensors are continuously measuring Time series data data, so called time series data. This paper aims to • is a sequence of numbers representing the measure- explain what time series data is and why it is relevant. It goes into detail of storing large amounts of time series ments of a variable at equal time intervals. data and the problems with conventional relational SQL- • can be identified by a source name or id and a metric style databases. Further, so called time series databases name or id. (TSDBs), which are databases specialized for handling • consists of ftimestamp , valueg tuples, ordered by large quantities of time series data, are introduced. Re- timestamp where the timestamp is a high precision quirements for designing an efficient TSDB, as well as Unix timestamp (or comparable) and the value is a different TSDB designs are presented. Finally a choice of float most of the times, but can be any datatype. multiple TSDBs is introduced, emphasizing on their design and how queries for data are performed on the example of OpenTSDB. I. TIME SERIES DATA II. DIFFERENCE BETWEEN TSDB AND CONVENTIONAL DATABASES In this section we give the reader an overview of what time series data is, where and why one might After explaining what time series data is in the previ- be interested in it and a few real world example use ous chapter, this chapter focuses on illustrating the dif- cases of where time series data is accumulated and used. -
Market Impact Report Juniper Networks’ Appformix: Intent-Driven Cloud-Scale Infrastructure
Market Impact Report Juniper Networks’ AppFormix: Intent-Driven Cloud-Scale Infrastructure EXECUTIVE SUMMARY Today, we live in a cloud-centric world with cloud-native applications and services reaching hundreds of millions of users globally via massive data centers located KEY FEATURES around the world. Until recently, the cloud has been the domain of a relatively • Autonomous, intent-driven small number of web-scale giants, cloud computing platforms, cloud-native infrastructure operation for businesses and global software companies. However, enterprises are now workload and resource migrating IT applications to hybrid clouds and network service providers are optimization reducing costs and increasing service agility by deploying cloud-scale platforms to • Smart agents streamline support Network Functions Virtualization (NFV). infrastructure monitoring by applying machine learning to Cloud-scale infrastructure presents significant operational challenges that arise metrics local to each node because of the massive scale, software-driven complexity and highly dynamic nature of applications deployed in run-time environments supported by the • Analytics modules monitor Docker, Kubernetes and Openstack frameworks, in which workloads and SLAs and correlate anomalies and events across the entire resources fluctuate constantly. infrastructure Traditional monitoring solutions rooted in legacy infrastructure are not well • Policy-driven controller suited to the real-time, full stack monitoring requirements of today’s cloud-scale assures pre-defined -
The Cacti Manual.Pdf
The Cacti Manual Ian Berry Tony Roman Larry Adams J.P. Pasnak Jimmy Conner Reinhard Scheck Andreas Braun The Cacti Manual by Ian Berry, Tony Roman, Larry Adams, J.P. Pasnak, Jimmy Conner, Reinhard Scheck, and Andreas Braun Published 2017 Copyright © 2017 The Cacti Group This project is licensed under the terms of the GPL. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. All product names are property of their respective owners. Such names are used for identification purposes only and are not indicative of endorsement by or of any company, organization, product, or platform. Table of Contents I. Installation...................................................................................................................................................................................1 1. Requirements.....................................................................................................................................................................1 2. Installing Under Unix.......................................................................................................................................................2 -
Towards a Representative Benchmark for Time Series Databases
CONFIDENTIAL UP TO AND INCLUDING 03/01/2017 - DO NOT COPY, DISTRIBUTE OR MAKE PUBLIC IN ANY WAY Towards a representative benchmark for time series databases Thomas Toye Student number: 01610806 Supervisors: Prof. dr. Bruno Volckaert, Prof. dr. ir. Filip De Turck Counsellors: Dr. ir. Joachim Nielandt, Jasper Vaneessen Master's dissertation submitted in order to obtain the academic degree of Master of Science in de industriële wetenschappen: elektronica-ICT Academic year 2018-2019 ii CONFIDENTIAL UP TO AND INCLUDING 03/01/2017 - DO NOT COPY, DISTRIBUTE OR MAKE PUBLIC IN ANY WAY Towards a representative benchmark for time series databases Thomas Toye Student number: 01610806 Supervisors: Prof. dr. Bruno Volckaert, Prof. dr. ir. Filip De Turck Counsellors: Dr. ir. Joachim Nielandt, Jasper Vaneessen Master's dissertation submitted in order to obtain the academic degree of Master of Science in de industriële wetenschappen: elektronica-ICT Academic year 2018-2019 PREFACE iv Preface I would like to thank my supervisors, Prof. dr. Bruno Volkaert and Prof. dr. ir. Filip De Turck. I am very grateful for the help and guidance of my counsellors, Dr. ir. Joachim Nielandt and Jasper Vaneessen. I would also like to thank my parents for their support, not only during the writing of this dissertation, but also during my transitionary programme and my master's. The author gives permission to make this master dissertation available for consul- tation and to copy parts of this master dissertation for personal use. In all cases of other use, the copyright terms have to be respected, in particular with regard to the obligation to state explicitly the source when quoting results from this master dissertation. -
Examensarbete Nätverksövervakning
Examensarbete Nätverksövervakning En jämförelse av Sensu och op5 Monitor Författare: Kristoffer NILSSON & Ashour SHAMOUN Handledare: Marcus WILHELMSSON Examinator: Jacob LINDEHOFF Termin: VT2014 Ämne: Datavetenskap Nivå: G1E Kurskod: 1DV41E Sammanfattning Rapporten beskriver arbetet och resultaten av en jämförelse mellan Sensu och op5 Monitor, vilka är verktyg som används för att övervaka enheter i nätverk, så kallade network monitoring systems. Arbetet har utförts för att utbudet av nätverksövervak- ningsverktyg ständigt växer och det ansågs värdefullt att jämföra en ny aktör med ett äldre verktyg som är byggd på ett annat tankesätt. Det som ansågs intressant att testa var hur dessa verktyg hanterade de rapporter som skapades och samlades in, om det slutgiltiga resultatet från detta skulle skilja sig åt eller inte. För att testa detta sattes en virtuell testmiljö upp, där Sensu och op5 Monitor rullade parallellt med varandra och övervakade samma system och använde sig utav samma plugin för övervakningen. Experimenten utfördes på två stycken tjänster, BIND9 samt Apache2, i och med att de två pluginen som användes var uppbyggda på olika sätt konstruerades även olika experiment. Under dessa experiment samlades information in om hur de två över- vakningsverktygen hanterade de rapporter de fick in, vilket sedan sammanställdes och analyserades. Slutsatsen av det hela var att Sensu och op5 Monitor hanterar sina insamlade rapporter på ett likvärdigt sätt, de rapporterade resultaten blev i samtliga fall detsamma, således fungerade de två övervakningsverktygen på ett jämgott vis. Nyckelord: Sensu, op5 monitor, Nagios, nätverksövervakning, nms Abstract The report describes the work and results of a comparison between Sensu and op5 Monitor, which are both tools used to monitor devices in a network, more commonly known as network monitoring systems. -
Storage of Network Monitoring and Measurement Data
Storage of Network Monitoring and Measurement Data A report submitted in partial fulfillment of the requirements for the degree of Bachelor of Computing and Mathematical Sciences at The University of Waikato by Nathan Overall c 2012 Nathan Overall Abstract Despite the limitations of current network monitoring tools, there has been little investigation into providing a viable alternative. Network operators need high resolution data over long time periods to make informed decisions about their networks. Current solutions discard data or do not provide the data in a practical format. This report addresses this problem and explores the development of a new solution to address these problems. Acknowledgements I would like to show my appreciation to the following persons who have made this project possible. Members of the WAND Network group for their continued support during the project, including my supervisor Richard Nelson. I would also like to give a special mention to Shane Alcock and Brendon Jones for their ongoing assistance to the project while they developed the WAND Network Event Monitor. DR. Scott Raynel for his support and advice throughout the project. The WAND network group and Lightwire LTD for providing the resources necessary to conduct the project. Contents List of Acronyms vi List of Figures vii 1 Introduction1 1.1 Network Operation.......................1 1.2 Overview of the Problem....................2 1.3 Goals...............................2 1.4 Plan of Action..........................3 2 Background4 2.1 Introduction...........................4 2.2 Round Robin Database.....................4 2.3 Tools using Round Robin Database (RRD)..........8 2.3.1 Smokeping...........................8 2.3.2 Cacti..............................9 2.4 The Active Measurement Project...............9 2.5 OpenTSDB.......................... -
Performance-Analyse in Großen Umgebungen Mit Collectd
Performance-Analyse in großen Umgebungen mit collectd Performance-Analyse in großen Umgebungen mit collectd Sebastian tokkee\ Harl " <[email protected]> FrOSCon 2009 2009-08-22 Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Gliederung Was ist collectd? Wichtige Eigenschaften Wichtige Plugins Eigene Erweiterungen Uber¨ den Tellerrand Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Was ist collectd? I collectd sammelt Leistungsdaten von Rechnern I Leistungsdaten sind zum Beispiel: I CPU-Auslastung I Speichernutzung I Netzwerkverkehr I Daten werden erhoben, verarbeitet und gespeichert I H¨aufig: Darstellung als Graphen I Nicht verwechseln mit Monitoring! Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Kontakt I Homepage: http://collectd.org/ I Mailinglist: [email protected] I IRC: #collectd auf irc.freenode.net Web 2.0\: http://identi.ca/collectd I " Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Wichtige Eigenschaften Wichtige Eigenschaften I Daemon I Freie Software (gr¨oßtenteils GPLv2) I Portierbar (Linux, *BSD, Solaris, . ) I Skalierbar (OpenWrt, . , Cluster / Cloud) I Effizient (Default-Aufl¨osung: 10 Sekunden) I Modular (Uber¨ 70 Plugins) Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Wichtige Eigenschaften Wichtige Eigenschaften I Daemon I Freie Software (gr¨oßtenteils GPLv2) I Portierbar (Linux, *BSD, Solaris, . ) I Skalierbar (OpenWrt, . , Cluster / Cloud) I Effizient (Default-Aufl¨osung: 10 Sekunden) I Modular (Uber¨ 70 Plugins) Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Wichtige Eigenschaften Wichtige Eigenschaften: 10-Sekunden-Aufl¨osung Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Wichtige Eigenschaften Wichtige Eigenschaften I Daemon I Freie Software (gr¨oßtenteils GPLv2) I Portierbar (Linux, *BSD, Solaris, . -
Forcepoint Appliances Command Line Interface (CLI) Guide
Forcepoint Appliances Command Line Interface (CLI) Guide V Series, X Series, & Virtual Appliances v8.4.x ©2018, Forcepoint All rights reserved. 10900-A Stonelake Blvd, Quarry Oaks 1, Suite 350, Austin TX 78759 Published 2018 Forcepoint and the FORCEPOINT logo are trademarks of Forcepoint. Raytheon is a registered trademark of Raytheon Company. All other trademarks used in this document are the property of their respective owners. This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine- readable form without prior consent in writing from Forcepoint. Every effort has been made to ensure the accuracy of this manual. However, Forcepoint makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose. Forcepoint shall not be liable for any error or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual or the examples herein. The information in this documentation is subject to change without notice. Contents Topic 1 Forcepoint Appliances Command Line Interface . .1 Conventions . .1 Logon and authentication . .2 CLI modes and account privileges . .2 Basic account management . .3 Command syntax. .9 Help for CLI commands . .9 System configuration . .10 Time and date . .11 Host name and description . .14 User certificates. .15 Filestore definition and file save commands. .16 Appliance interface configuration. .18 Appliance vswitch configuration . .29 Content Gateway Decryption Port Mirroring (DPM) . .29 Static routes. .31 Appliance status . .35 SNMP monitoring (polling) . .35 SNMP traps and queries . .38 Module-specific commands .