DOCSLIB.ORG

IRC Control Bot for Zabb Monitoring System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IRC Control Bot for Zabb Monitoring System MASARYK UNIVERSITY FACULTY OF INFORMATICS IRC control bot for Zabb monitoring system BACHELOR'S THESIS Filip Zachar Brno, Fall 2015 Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Filip Zachar Advisor: RNDr. Adam Rambousek, Ph.D. i Acknowledgement I would like to thank my supervisor RNDr. Adam Rambousek, Ph.D. who supported me during writing this thesis and provided useful feedback. I would also like to thank Marek Mahut for advice and consultation regarding technical details for Zabbix monitoring system and for feedback provided during the test stage of this work. ii Abstract Applications these days runs as distributed systems consisting of many parts working together. This thesis discuss the necessity of mon• itoring these parts and describes the design and implementation of IRC control bot for Zabbix monitoring system that provides extended features through IRC communication network. iii Keywords Zabbix, monitoring, IRC, DevOps, Ruby iv Contents 1 Introduction 1 2 Monitoring 2 2.1 Monitoring system 3 2.2 MRTG -MultiRouter Traffic Grapher 3 2.3 Cacti 5 2.4 Nagios 7 2.5 Zabbix 8 2.5.1 Architecture 8 2.5.2 Data collection 11 2.5.3 Data Visualization 13 2.5.4 Alerts and Triggers 14 2.5.5 Maintenance 15 2.5.6 API 15 3 IRC - Internet Relay Chat 17 3.1 Architecture 17 3.2 Conferencing 18 3.3 Bot 19 4 Zabbirc 21 4.1 Goal 21 4.2 Architecture 21 4.2.1 Zabbix API 22 4.2.2 IRC API 23 4.3 Implementation 24 4.3.1 Zabbix component 24 4.3.2 Services component 25 4.3.3 IRC component 25 4.4 Features 26 4.4.1 Events 26 4.4.2 Hosts 27 4.4.3 Maintenance 28 4.4.4 Settings 28 4.5 Installation 28 5 Conclusion 30 Index 31 Bibliography 31 v List of Tables 3.1 Operator privileged actions 3.2 Operator privileged actions List of Figures 2.1 Screenshot of MRTG web page [4] 4 2.2 Screenshot of RRDtool generated graph 5 2.3 Screenshot of Cacti web interface 6 2.4 Screenshot of Nagios web interface 7 2.5 Zabbix deployment model for large environments 9 2.6 Zabbix deployment model using proxy servers 10 2.7 Graph showing three items in stacked format 12 2.8 Map representing physical infrastructure of a web service 13 2.9 Screen showing map with appropriate graphs alongside 14 2.10 Trigger rules 15 2.11 JSON-RPC API login request 16 3.1 IRC network 18 4.1 Zabbirc basic architecture 22 4.2 Zabbirc components interaction 24 4.3 Definition of the matchers for Zabbirc commands 26 4.4 Event notification and acknowledgment 27 4.5 Host status reporting 27 4.6 Installation steps for Zabbirc 29 vii 1 Introduction Over 3 billion people use Internet on daily basis nowadays and the number is still growing [1]. But Internet does not longer consist of just simple hypertex pages as it was at source of early World Wide Web era. It is full of dynamic web applications and services like social networks, video streaming services, storage exchange services or even office like applications that were used mainly as a desktop software. These applications serves to the millions of people at once. To accomplish this scale of availability they are no longer implemented on a single server but as more sophisticated distributed system. Distributed system consists of many moving parts working to• gether thus more points of failure are present. The whole system can be designed to be able to operate with some parts missing but to achieve the best reliability they should be monitored in order to pretend possible failures or be able to react to the occurred ones as soon as possible. In the Chapter 2 we describe what monitoring of the system con• sists of and discuss several existing monitoring solutions. Later in the chapter the thesis is focused on Zabbix monitoring system, it's capabilities and options to extend the system. The Chapter 3 describes IRC1 protocol used for communication in the bigger scale. It describes the architecture of the IRC network and discusses applicability of the IRC bots. The main goal of this thesis is to design and implement an IRC control bot that will serve as a gateway for controlling a Zabbix moni• toring system. The architecture, implementation and the features of the bot are described in the Chapter 4. The chapter also justifies used technologies and libraries that were used to create the bot. 1. Internet Relay Chat 1 2 Monitoring Most of the applications we use on the daily basis and provides us sim• ple interface to accomplish demanded task are however much more complicated under the hood when we look at the architectural and implementation details. What started as a single server service main• tained by one system administrator can easily grow to the distributed system that sits in the cloud. This more complex distributed architec• ture allows the service providers to handle the enormous amount of the customers that use various internet services these days in order to provide more redundancy, availability and speed. With distributed environment like that, it is really important to keep all the required units in healthy state. The company that is creating a product has to do an important decision about the deployment. • It can build it's own bare metal infrastructure that will run the product. Choosing this option it will have to provide all the maintenance that the infrastructure needs to ensure product's availability. To accomplish this usage of the various monitoring systems is recommended. • It can use some of the existing cloud platforms to host their appli• cation and thus bring a layer of abstraction to the infrastructure. It defines required services in a declarative way and the cloud platform takes care about fulfilling the defined requirements. Despite of what option the company chooses, there must be a bare metal infrastructure somewhere underneath. This cluster of devices in the infrastructure forms a computer network that faces several chal• lenges. The amount of data flowing in the network is almost constantly growing. Application data, media streams, backups, database queries and replication tend to saturate bandwidth just as much as they eat up storage space. To avoid a congestion in the network and outage of storage room on the nodes system administrators need to have good overview of the infrastructure status by visualizing the right data in the right way. This can be achieved by using a monitoring system. In this chapter we will talk about what a monitoring system is and what should it provide. We look at several existing monitoring systems 2 2. MONITORING and we will shortly discuss about their advantages, disadvantages and main characteristics. 2.1 Monitoring system Monitoring system is a piece of software that collects data from several sources, analyzes the data and gives a sophisticated visualization about the data. The data source can be any component in the network. The monitor• ing system usually supports the data collection by standard methods like SNMP1 therefore any device that has implemented this protocol is potential data source for the monitoring system. It can also use custom API2 to retrieve information from the monitored devices using agent approach. Agent is a small program running on the monitored device that gathers information about the device and communicates with the monitoring system using the conventional protocol. Agents are mostly used to monitor computers in the network since they require more computation performance. The collected data are analyzed using the rules configured on the monitoring system. The monitoring system checks if there is any threshold overlap and takes appropriate action to respond to the event. The data visualizations consists of various graphs generated from the data. This graphs shows the data in more informative way and also shows the historical information about the metric. Several monitoring systems are available with good community and enterprise support. This thesis takes into a consideration four of them: MRTG, Cacti, Nagios and Zabbix. 2.2 MRTG - Multi Router Traffic Grapher Multi Router Traffic Grapher (MRTG) was initially just a perl script which used external utilities to perform SNMP queries and create GIF images for display on the HTML pages (Figure 2.1). This script was being executed every 5 minutes and showed accumulated data in the graphs for last day, week, month and year. It was written by Tobias 1. Simple Network Management Protocol 2. Application Programming Interface 3 2. MONITORING M ax S che dule d Che cks: 50.0 Average S che dule d Che cks: 44.0 Current S che dule d Che cks: 45.0 Max On-DemandChecks: 45.0 Average On-DemandChecks: 10.0 Current On-DemandChecks: 10.0 Figure 2.1: Screenshot of MRTG web page [4] Oetiker in 1995 who was working at De Montfort University Leicester in United Kingdom as a System Administrator Trainee. At that time the university had 64 kBit Internet link and the management was not planing to increase this link any soon. The performance data provided by MRTG proved to bey a key argument in convincing management about necessity of the faster Internet link. [2, 3] One of the main problems in the first version of MRTG was perfor• mance. Monitoring 10 switch links worked fine but in larger environ• ments it encountered it's limits.
Load more

Recommended publications
  • 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
    [Show full text]
  • 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.
    [Show full text]
  • 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
    [Show full text]
  • 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..........................
    [Show full text]
  • 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, .
    [Show full text]
  • MRTG the Multi Router Traffic Grapher
    The following paper was originally published in the Proceedings of the Twelfth Systems Administration Conference (LISA ’98) Boston, Massachusetts, December 6-11, 1998 MRTG The Multi Router Traffic Grapher Tobias Oetiker Swiss Federal Institute of Technology, Zurich For more information about USENIX Association contact: 1. Phone: 510 528-8649 2. FAX: 510 548-5738 3. Email: [email protected] 4. WWW URL: http://www.usenix.org MRTG – The Multi Router Traffic Grapher Tobias Oetiker – Swiss Federal Institute of Technology, Zurich ABSTRACT This paper describes the history and operation of the current version of MRTG as well as the Round Robin Database Tool. The Round Robin Database Tool is a program which logs and visualizes numerical data in a efficient manner. The RRD Tool is a key component of the next major release of the Multi Router Traffic Grapher (MRTG). It is already fully implemented and working. Because of the massive performance gain possible with RRD Tool some sites have already started to use RRD Tool in production. Motivation MRTG logged its data to an ASCII file, rewriting it every five minutes, constantly consolidating it, so In Summer 1994, the De Montfort University in that the logfile would not grow over time. The logfile Leicester, UK, had one 64 kBit Internet link for more did only store slightly more data than was needed to than 1000 networked computers. As it was not possi- draw the graphs on the web page. The graphs were ble to get a faster Internet link for another year, it was converted to GIF format by piping a graph in PNM desirable to at least provide the users on campus with format to the pnmtogif tool from the PBM pack- current and detailed information about the status of the age.
    [Show full text]
  • RES Application Guide
    ATTENTION This is NOT the application form to access RES resources. This document has been created only as a guide showing the information needed to fill the application form online. All the applications must be presented through the online form available at https://www.bsc.es/res-intranet/. 1. General Information a) Activity Title b) Area (select): Astronomy, Space and Earth Sciences Life and Health Sciences Physics Engineering and Mathematics Homogeneous Chemistry Heterogeneous Chemistry and Solids 2. Research Project Description a) Is this a Test Activity? Yes / No b) Is this a Long Term Activity that will extend over two application periods? Yes / No c) Brief description of the Project If this Activity takes place in the context of a Scientific Research Project, give a brief description of the Project, including the reference of National or International grants which support it. Summarize the research in the context of the current state-of-the-art, including references if appropriate. (Maximum 5000 characters). d) Grant References e) Brief description of the Project (If this Activity takes place in the context of a Technology or Industrial Project) If this Activity takes place in the context of a Technology or Industrial Project, give a brief description of the Project, including the potential impact resulting from this activity, in measurable terms (potential for patent applications, competitive advance, prototypes, new products, economic impact, etc.). (Maximum 5000 characters). f) Specific Activity proposed Describe the specific Activity proposed. Discuss the need for Supercomputing facilities. Describe in detail the specific calculations you plan to do, and their relevance to the Research Project.
    [Show full text]
  • Ivoyeur Changing the Game, Part 2
    iVoyeur Changing the Game, Part 2 DAVE JOSEPHSEN Dave Josephsen is the Near the end of his poem “The Talking Oak,” Tennyson alludes to the oldest of the author of Building a pagan oracles: Jupiter at Dodona . It was quite different from the oracles that fol- Monitoring Infrastructure lowed it in that no temple, altar, or human contrivance was ever constructed there . with Nagios (Prentice It was merely an oak grove on an island in the Aegean Sea . The Selli tribal priests Hall PTR, 2007) and is senior systems who lived there could decipher the word of Jupiter himself from the sound of the engineer at DBG, Inc., where he maintains wind rustling the leaves of those sacred oak trees (some stories say wind-chimes a gaggle of geographically dispersed server were also employed) . farms. He won LISA ’04’s Best Paper award for I’d read Tennyson’s poem in high school but, that being pre-Google, I never under- his co-authored work on spam mitigation, and stood his reference to “that Thessalian growth” until I recently happened to read he donates his spare time to the SourceMage about the oracle at Dodona . The resolution of that long-forgotten enigma must GNU Linux Project. have made an impression on my subconscious, because I subsequently dreamt that [email protected] I visited that ancient oracular forest and heard the whisper of its long-dead deity . His message to me? “Your Web server is down ”. I often tell people, when the subject of my occupation arises, that I’m a plumber .
    [Show full text]
  • Monitoring Tools for Network Services and Systems Best Practice Document
    Monitoring Tools for Network Services and Systems Best Practice Document Produced by CSC/Funet led working group on AccessFunet Author[s]: Kaisa Haapala, Janne Oksanen 13.05.2011 © TERENA 2010. All rights reserved. Document No: GN3-NA3-T4-Monitoring-Tools Version / date: 13.05.2011 Original language : Finnish Original title: “Verkon palvelujen ja järjestelmien valvontatyökaluja” Original version / date: 1.0 of 13.05.2011 Contact: kaisa.haapala (at) csc.fi CSC/Funet bears responsibility for the content of this document. The work has been carried out by a CSC/Funet led working group on AccessFunet as part of a joint-venture project within the HE sector in Finland. This translated version is based on the Finnish counterpart approved by the CSC/Funet annual general meeting on 13 May 2011 after an open consultation period of two weeks. Parts of the report may be freely copied, unaltered, provided that the original source is acknowledged and copyright preserved. The research leading to these results has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement n° 238875, relating to the project 'Multi-Gigabit European Research and Education Network and Associated Services (GN3)'. 2 Table of Contents 1. Introduction ......................................................................................................................... 4 2. Planning Monitoring ............................................................................................................ 4 3. Different Technical
    [Show full text]
  • List of Application Added in ARL #2607
    List of Application added in ARL #2607 Application Name Publisher .NET Framework 19.0 Microsoft .NET Runtime 6 Preview Microsoft .NET SDK 6 Preview Microsoft 3DMark UL 3uTools 2.35 3uTools 4D 17.6 4D 4K Stogram 3.0 OpenMedia ABACUS Studio 8.0 Avolution ABCpdf .NET 11.1 WebSupergoo Software ACQUITY Column Manager 1.7 Waters Acrobat Elements 17.1 Adobe ACT Enterprise Client 2.12 Access Control ACT Enterprise Client 2.3 Access Control ACTEnterprise 2.3 Vanderbilt Actiance Vantage OpenText Actional Agent 9.0 Progress Software Active Directory (AD) Bridge 8.5 Enterprise BeyondTrust Active Directory/LDAP Connector 5.0 Auth0 Active Intelligence Engine 4.4 Attivio ActivePresenter 8.1 Atomi Systems ActivePython 3.8 ActiveState ActivInspire 2.17 Promethean Activity Monitor 4.0 STEALTHbits Technologies Activity Monitor Agent 2.4 STEALTHbits Technologies ActiViz.NET 8.2 Supported Kitware SAS ActiViz.NET 8.2 Trial Kitware SAS ActiViz.NET 9.0 Supported Kitware SAS Acumen Cumulative 8.5 Deltek AD Tidy 2.6 Cjwdev AdAnalytics Adslytic Add-in Express for Microsoft Office and .NET 8.3 Professional Add-in Express Add-in Express for Microsoft Office and .NET 9.4 Premium Add-in Express Adlib PDF 5.1 Enterprise Adlib AdminStudio 2021 Flexera AdminStudio 2021 ZENworks Flexera Advance Design 2020 GRAITEC Advance Design 2021 GRAITEC Advanced SystemCare 14.0 IObit Advertising Editor 11.29 Microsoft Advisor 9.5 Belarc AFP Viewer 7.50 ISIS Papyrus Europe AG Agile Requirements Designer 3.1 Broadcom Alfresco Content Services 6.0 Alfresco Software AltspaceVR 4.1 Microsoft
    [Show full text]
  • Evaluating Web Development Frameworks: Django, Ruby on Rails and Cakephp
    Evaluating web development frameworks: Django, Ruby on Rails and CakePHP Julia Plekhanova Temple University © September 2009 Institute for Business and Information Technology Fox School of Business Temple University The IBIT Report © 2009 Institute for Business and Information Technology, Bruce Fadem Fox School of Business, Temple University, Philadelphia, PA Editor-in-chief 19122, USA. All rights reserved. ISSN 1938-1271. Retired VP and CIO, Wyeth The IBIT Report is a publication for the members of the Fox Munir Mandviwalla School’s Institute for Business and Information Technology. IBIT reports are written for industry and based on rigorous Editor academic research and vendor neutral analysis. For additional Associate Professor and Executive Director reports, please visit our website at http://ibit.temple.edu. Fox School of Business, Temple University No part of this publication may be reproduced, stored in a Laurel Miller retrieval system or transmitted in any form or by any means, Managing Editor electronic, mechanical, photocopying, recording, scanning Director, Fox School of Business, Temple University or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without the prior written permission of the Publisher. Requests to the Publisher Board of editors for permission should be addressed to Institute for Business and Information Technology, Fox School of Business, Temple Andrea Anania University, 1810 N. 13th Street, Philadelphia, PA 19122, Retired VP and CIO, CIGNA USA, 215.204.5642, or [email protected]. Jonathan A. Brassington Disclaimer: The conclusions and statements of this report Founding Partner and CEO are solely the work of the authors. They do not represent LiquidHub Inc.
    [Show full text]
  • Open Source Licenses
    Threat Protection System v5.1.0 Open Source Licenses The TippingPoint Threat Protection System (TPS) devices use open source components. Many open source license agreements require user documentation to contain notification that the open source software is included in the product. For inquiries about acquiring license code, contact support. The following agreements are for software that this product includes or may include: • "BIND License Agreement" on page 9 • "boost License Agreement" on page 10 • "coreutils License Agreement regarding coreutils & libmspack" on page 11 • "corosync License Agreement" on page 20 • "cpputest License Agreement" on page 21 • "License Agreement regarding dbus; ecryptfs-utils; gdb; glibc; gptfdisk; ipset; keyutils; libcgi; libnih; libstatgrab; linux; lm-sensors; lttng; mxml; net-tools; open-vm-tools; pam-tacplus; rng-tools; RRDTool; syslog-ng; upstart & util-linux" on page 22 • "gSoap License Agreement" on page 26 • "host-sflow License Agreement" on page 33 • "ipmitool License Agreement" on page 38 • "jitterentropy-rngd License Agreement" on page 39 • "libpcap License Agreement" on page 40 • "libxml License Agreement" on page 41 • "NTP License Agreement" on page 42 • "OpenSSH License Agreement" on page 43 • "License Agreement regarding OpenSSL & openssl-fips" on page 49 • "qDecoder License Agreement" on page 52 • "shadow License Agreement" on page 53 • "tcpdump License Agreement" on page 55 TippingPoint acknowledges that the following open source components may be used in this product: • Adaptive Public License
    [Show full text]