DOCSLIB.ORG

OTRS (Open Technology Real Services)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
OTRS (Open Technology Real Services) OTRS (Open Technology Real Services) OTRS is one of the most flexible web-based ticketing systems used for Customer Service, Help Desk, IT Service Management. As the name suggests, OTRS is a "ticketing system" which provides users with an application that can create, distribute, answer, manage, and archive trouble tickets received from customers via telephone or e-mail. By default, user roles in the system are configured as Agents who respond to requests, and Users who receive services. Both types of users interface with OTRS through its fully customizable web interface. After the appropriate installation, setup, and configuration, user can access tickets and ticket histories, as well as create new tickets if appropriate to their role in the system. Additional roles can also be created, and out of the box roles can be customized to fit any specification or requirement. Tickets enter the system and are subsequently managed by assignment or movement between queues. All tickets issued for individual customers and companies have unique, customizable numerical identifiers. Actions are stored in the database and can be accessed through the ticket history. Tickets can have different status characteristics, escalation times, and email addresses depending upon the queue in which they reside. This is also preserved in the history and archive. Statistical analysis is also possible. Tickets can be answered with predetermined e-mail responses that can also contain attachments. Automation of responses and notification evens is possible. Since its beginnings OTRS has been implemented in the programming language Perl. The web interface is made more user-friendly by using JavaScript (which can be switched off for security reasons). Different functionalities are implemented as reusable backend modules, making it possible to create custom modules to extend the functionality of the OTRS system. The web interface itself uses its own templating mechanism called DTL (Dynamic Template Language) to facilitate the display of the systems output data. Originally, OTRS worked only on MySQL databases. Support has since been added for PostgreSQL, Oracle, DB2 and Microsoft SQL Server. OTRS may be used on many UNIXor UNIX-like platforms (e.g. Linux, Mac OS X, FreeBSD, etc.) as well as on Microsoft Windows. INSTALLATION 1) Download install files “otrs-4.0.10.tar.gz”. 2) Extract “otrs-4.0.10.tar.gz” to “/opt” directory. 3) Rename “otrs-4.0.10″ directory to “otrs”. 4) Install MySQL server. 5) Install Apache Web server. 6) Install Perl modules. 7) Update source list. 8) Upgrade all installed packages. 9) Check and make sure that all required Perl modules are installed. 10) Create new user for running OTRS, because OTRS should not be run with root user rights. 11) Add created OTRS user in step above to Web server group. 12) Activate OTRS config files by copying them without .dist filename extension. 13) Run syntax check to see if your Perl is properly set up. After every command you should see message “syntax OK”. 14) Set Web server user permissions for OTRS user. 15) Set up working Apache configuration by copying OTRS conf file “apache2-httpd.include.conf” to “etc/apache2/sites-available/” directory. 16) For installing additional packages, like for example ITSM bundle it is required to set MySQL database to accept packages larger than 16 MB which is set by default. OTRS message: Please make sure your database accepts packages over 20 MB in size (it currently only accepts packages up to 16 MB). Please adapt the max_allowed_packet setting of your database in order to avoid errors.“ Change following line from: “max_allowed_packet = 16M” to “max_allowed_packet = 50M” and add the following line “innodb_log_file_size = 512M” 17) Copy Cron jobs scripts without suffix “.dist”. 18) Configure Cron Jobs with “Cron.sh” script. Note: do not run Cron.sh script as root user, run it as OTRS user. 19) Change how often will PostMaster fetch email (by default it is set to fetch emails very 10 minutes). Change following line from: to 20) Run OTRS web based installer and finish installation steps. http://localhost/otrs/installer.pl 21) Improve Web server GUI speed activate mod-headers. 22) Restart your Ubuntu server, and start using OTRS system via following links: Agent Web interface… http://localhost/otrs/index.pl Customer web interface… http:// localhost /otrs/customer.pl Now, we login to system as admin. After login, helpdesk dashboard page is opened. "Don't use the Superuser account to work with OTRS! Create new Agents and work with these accounts instead." error is displaying. Optionally, we can create agents in settings page. Ticket management is important in OTRS System. So ticket components should not removed from dashboard.Some components; Showing new tickets Showing requests in queue Showing tickets that is increasing priority Company or person's emails can be shown as tickets. These tickets are solved by agents. Agents can do these processes; Send e-mail Call phone Change priority Long estimation time Closing All processes are stored on database CONFIGURATION Our scenario is; "We are a hosting company. Groups and Roles, Agent and Customers are in this company. Our company has IT and IK/Finance departmants. There departmants have sub depertmants. Technical request are sending to IT depertmant and Billing requests are sending to Finance depertmant. " GROUPS Groups in OTRS should be thought of as collections of access rights. To some extent, you can also think of Groups as collections of Queues, though that limits their scope a bit. There are a few modules, including Stats (reporting) and FAQs, that don’t have Queues associated with them by default, but you still define access rights to their functionality through Groups. For this reason, you should not get in the habit of thinking of Groups exclusively as collections of Queues. Groups define the following rights: MOVE_INTO (move tickets into these queues) CREATE (create tickets/articles in these queues) NOTE (add notes to tickets in these queues) OWNER (change the owner of tickets in these queues) PRIORITY (change the priority of tickets in these queues) RW (read-write access to tickets/modules in this group) RO (read-only access to tickets/modules in this group) You can see that the first five rights apply primarily to Queues, while the last two (RW/RO) are more closely related to modules like Stats and FAQ. Nevertheless, there is some overlap. Develop a bias toward thinking of Groups as collections of rights rather than collections of Queues. When you associate a Queue with a Group, you are granting all the access rights defined by that Group to the selected Queue. Groups can seen from Admin page. These groups are already exist. We will create custom groups for our system Create group page; After enter group name, define roles on users Our all groups; ROLES Now that you have some Queues that allow you to classify tickets, and you have Groups that define access rights to those Queues, you need to find a way to grant those rights to an Agent. There are two ways to do this. The first is to assign Agents directly to Groups. This is not generally regarded as best practice for large implementations. Instead, I recommend setting up Roles. Using Roles instead of assigning Group rights directly to Agents offers the following advantages: You only have to configure the rights once, for the role. You can associate multiple Agents with a Role in one swoop. When Agents assume or discard a Role, you can add/remove rights by disassociating them from the Role—no need to update multiple rights on multiple groups. When the responsibilities of a Role change, you only have to update them once for everyone associated with that Role. The trade-off of using Roles is it requires a little more work up front. You have to define your Groups and Roles clearly to make sure that Agents get the rights they need. In the long-run, though, it will simplify administration. Create role; We created 16 Roles; AGENTS By clicking the link Agents, you get access to the agent management screen of OTRS (see Figure below). Administrators can add, change or deactivate agent accounts. Furthermore they can also manage agent preferences, including the language and notification settings for the individual agent's interface. NOTE: An OTRS agent account may be deactivated but not deleted. Deactivation is done by setting the Valid flag to invalid or invalid-temporarily. Create agent page; After creating agent, we need add to groups this agent. Our agents; After creating all agents, groups and roles, move the step relations. 1) Manage Role-Agent Relations 2) Manage Role-Group Relations Services Services such as "standard IT workstation", "e-mail" or "web access" are IT products and should be compiled in a "IT service catalog" prior to the adoption of OTRS ITSM. Such a service catalog is usually customer or company specific and can be structured hierarchically. Furthermore, it should be formulated in a user friendly, meaning easily understood, language, as both IT personnel (agents) and IT users (customers) are among its audience. Adding service; Our services; SLA Service levels and the respective agreements (service level agreements, SLAs) document quality pledges for IT services. SLAs are recorded and administered in the admin interface. OTRS:ITSM offers by default up to 99 different calendars to describe the various time zones for work or service times. The SLAs can be allocated to them ("service level window"). Various time spans can be entered (in minutes) which OTRS::ITSM uses to control notification and escalation: [ Response Time ] = reaction time with incidents = start of service request procession ("service request lead time") [ Update Time ] = notification time [ Solution Time ] = time elapsed until incidents are resolved ("maximum time to repair", "MTTR") = delivery time for service requests ("delivery time") [ Min.
Load more

Recommended publications
  • Automated IT Service Fault Diagnosis Based on Event Correlation Techniques
    Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Dissertation an der Fakultat¨ fur¨ Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universitat¨ Munchen¨ vorgelegt von Andreas Hanemann Tag der Einreichung: 22. Mai 2007 1. Berichterstatter: Professor Dr. Heinz-Gerd Hegering, Ludwig-Maximilians-Universit¨at M¨unchen 2. Berichterstatterin: Professor Dr. Gabrijela Dreo Rodosek, Universit¨at der Bundeswehr M¨unchen Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Dissertation an der Fakultat¨ fur¨ Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universitat¨ Munchen¨ vorgelegt von Andreas Hanemann Tag der Einreichung: 22. Mai 2007 Tag der m¨undlichen Pr¨ufung: 19. Juli 2007 1. Berichterstatter: Professor Dr. Heinz-Gerd Hegering, Ludwig-Maximilians-Universit¨at M¨unchen 2. Berichterstatterin: Professor Dr. Gabrijela Dreo Rodosek, Universit¨at der Bundeswehr M¨unchen Acknowledgments This thesis has been written as part of my work as a researcher at the Leib- niz Supercomputing Center (Leibniz-Rechenzentrum, LRZ) of the Bavarian Academy of Sciences and Humanities which was funded by the German Re- search Network (DFN-Verein) as well as in cooperation with the research group of Prof. Dr. Heinz-Gerd Hegering. Apart from the LRZ, this research group called MNM-Team (Munich Network Management Team) is located at the University of Munich (LMU), the Munich University of Technology (TUM) and the University of Federal Armed Forces in Munich. At first, I would like to thank my doctoral advisor Prof. Dr. Heinz-Gerd Hegering for his constant support and helpful advice during the whole prepa- ration time of this thesis. I would also like to express my special gratefulness to my second advisor, Prof.
    [Show full text]
  • Ticketing Systems with RT
    Ticketing Systems with RT Network Startup Resource Center www.nsrc.org These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (http://creativecommons.org/licenses/by-nc/4.0/) Typical Support Scenario • Lots of email traffic requesting help, request for services, etc • Archived as text without classification • Very difficult to find current status or problem history • Sometimes problems were forgotten or never resolved • Difficult for another person to follow up on a problem that someone else started dealing with Why Ticketing Systems? Ticketing Systems Why are they important? • Track all events, failures and issues • Focal point for help desk communication Use it to track all communications • Both internal and external Events originating from the outside: • customer complaints Events originating from the inside: • System outages (direct or indirect) • Planned maintenance, upgrades, etc. Ticketing Systems (Contd.) • Use a ticket system to follow cases, including communication between the support staff • Each case is considered a ticket • Each ticket has a ticket number • Each ticket goes through a similar life cycle: • New – Open – … – Resolved Help Request with Tickets Request Tracker / Trac RT • Heavily used worldwide • Can be customized to your location • Somewhat difficult to install and configure • Handles large-scale operations • A hybrid including wiki & project management features • Web-only ticket system works well but not robust as RT • Often used for ”trac”king group projects.
    [Show full text]
  • OTRS Asterisk PBX Integration Module PIM V2.0.0B Administrator's
    OTRS Asterisk PBX Integration Module PIM v2.0.0b Administrator's Guide 2019 © IP-LAB.RU Contents Introduction .................................................................................................................................................. 3 Preparing Asterisk PBX for integration with OTRS ........................................................................................ 4 Install the PIM package on the OTRS server ................................................................................................. 5 Configuring the PIMv2.0.0b module ............................................................................................................. 6 Definition of "Tracking number" ................................................................................................................... 8 Setting agent extensions ............................................................................................................................... 9 Assign agent extensions to the "Tracking Number" ................................................................................... 10 Customer User identification ...................................................................................................................... 11 CallerID modification ................................................................................................................................... 11 Starting the service ....................................................................................................................................
    [Show full text]
  • Onapp Admin Guide
    2.0 Admin Guide 2.0 Admin Guide Contents 0. About This Guide ............................................................................................... 5 1. OnApp Overview ................................................................................................ 6 1.1 Servers ................................................................................................................... 6 1.2 Networks ................................................................................................................ 7 1.3 Templates .............................................................................................................. 8 1.4 Virtual Machines .................................................................................................... 8 1.5 Scalability .............................................................................................................. 8 1.6 Availability and Reliability .................................................................................... 8 1.7 Security .................................................................................................................. 9 1.8 API and Integration ............................................................................................... 9 2. OnApp Hardware & Software Requirements ................................................. 10 2.1 Hypervisor Servers ............................................................................................. 10 2.2 Control Panel Server ..........................................................................................
    [Show full text]
  • Install Perl Modules
    How to install OTRS (Open Source Trouble Ticket System) on Ubuntu 16.04 Prerequisites Ubuntu 16.04. Min 2GB of Memory. Root privileges. Step 1 - Install Apache and PostgreSQL In this first step, we will install the Apache web server and PostgreSQL. We will use the latest versions from the Ubuntu repository. Login to your Ubuntu server with SSH: ssh [email protected] Update Ubuntu repository. sudo apt-get update Install Apache2 and a PostgreSQL with the apt: sudo apt-get install -y apache2 libapache2-mod-perl2 postgresql Then make sure that Apache and PostgreSQL are running by checking the server port. netstat -plntu You will see port 80 is used by apache, and port 5432 used by PostgreSQL database. Step 2 - Install Perl Modules OTRS is based on Perl, so we need to install some Perl modules that are required by OTRS. Install perl modules for OTRS with this apt command: sudo apt-get install -y libapache2-mod-perl2 libdbd-pg-perl libnet-dns-perl libnet-ldap-perl libio-socket-ssl-perl libpdf-api2-perl libsoap-lite-perl libgd-text-perl libgd-graph-perl libapache- dbi-perl libarchive-zip-perl libcrypt-eksblowfish-perl libcrypt-ssleay-perl libencode-hanextra- perl libjson-xs-perl libmail-imapclient-perl libtemplate-perl libtemplate-perl libtext-csv-xs-perl libxml-libxml-perl libxml-libxslt-perl libpdf-api2-simple-perl libyaml-libyaml-perl When the installation is finished, we need to activate the Perl module for apache, then restart the apache service. a2enmod perl systemctl restart apache2 Next, check the apache module is loaded with the command below: apachectl -M | sort And you will see perl_module under 'Loaded Modules' section.
    [Show full text]
  • OTRS 3.1 - Admin Manual OTRS 3.1 - Admin Manual Copyright © 2003-2012 OTRS AG
    OTRS 3.1 - Admin Manual OTRS 3.1 - Admin Manual Copyright © 2003-2012 OTRS AG René Bakker, Stefan Bedorf, Michiel Beijen, Shawn Beasley, Hauke Böttcher, Jens Bothe, Udo Bretz, Martin Edenhofer, Carlos Javier García, Martin Gruner, Manuel Hecht, Christopher Kuhn, André Mindermann, Marc Nilius, Elva María Novoa, Henning Oschwald, Martha Elia Pascual, Thomas Raith, Carlos Fernando Rodríguez, Stefan Rother, Burchard Steinbild, Daniel Zamorano. This work is copyrighted by OTRS AG. You may copy it in whole or in part as long as the copies retain this copyright statement. The source code of this document can be found at source.otrs.org [http://source.otrs.org/viewvc.cgi/doc-admin/]. UNIX is a registered trademark of X/Open Company Limited. Linux is a registered trademark of Linus Torvalds. MS-DOS, Windows, Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows 2003, Windows Vista and Windows 7 are registered trademarks of Microsoft Corporation. Other trademarks and registered trademarks are: SUSE and YaST of SUSE Linux GmbH, Red Hat and Fedora are registered trademarks of Red Hat, Inc. Mandrake is a registered trademark of MandrakeSoft, SA. Debian is a registered trademark of Software in the Public Interest, Inc. MySQL and the MySQL Logo are registered trademarks of Oracle Corporation and/or its affiliates. All trade names are used without the guarantee for their free use and are possibly registered trade marks. OTRS AG essentially follows the notations of the manufacturers. Other products mentioned in this manual may be trademarks of the respective manufacturer. Table of Contents Preface .......................................................................................................................... xii 1. Trouble Ticket Systems - The Basics ...........................................................................
    [Show full text]
  • Openstackでnecが実現する 「OSSクラウド」の世界
    ＯｐｅｎＳｔａｃｋでＮＥＣが実現する 「ＯＳＳクラウド」の世界 ２０１３年３月１２日 日本電気株式会社 プラットフォームマーケティング戦略本部 ＯＳＳ推進室 技術主幹 高橋 千恵子 目次 ▐ ＯＳＳの動向 ▐ ＮＥＣのＯＳＳ/Ｌｉｎｕｘ事業 ▐ ＯＳＳプラットフォームへの取り組み 高可用Ｌｉｎｕｘプラットフォーム ＯＳＳミドルウェアの活用 ▐ ＯＳＳクラウド ＯｐｅｎＳｔａｃｋへの取り組み ＯＳＳクラウドソリューション ～沖縄クラウドサービス基盤～ ＯｐｅｎＦｌｏｗ+ＯｐｅｎＳｔａｃｋ ▐ 最後に ●本資料に掲載された社名、商品名は各社の商標または登録商標です。 Page 1 © NEC Corporation 2013 ＯＳＳの動向 Page 2 © NEC Corporation 2013 ＯＳＳコミュニティによるプロジェクト ▐ 全般 ・・・・・SaaS型アプリケーションが増加/著名OSSのベンダー配布、有償サポートや買収が進む OSS定点観測は、freecode.com にて実施。 ▐ ｲﾝﾌﾗ系・・・仮想化やクラウド基盤関係のOSSが注目される/システム、ネット管理OSSの伸びがある サイトでの人気度（300以上)で順位付け。 OSSプロジェクトは2012.4時点で32.4万件。 ▐ ﾃﾞﾌﾟﾛｲﾒﾝﾄ系・・PostgreSQL、mySQLが高人気 これらのDB管理、DBクラスタリングOSSも伸びている ビジネス用途を中心に表示。 ▐ ｱﾌﾟﾘ系・・・・SaaS型グループウェアOSS、ソフトウェア分類を越えた統合的な著名OSSの伸びがある コンシューマ・プライベート系は除く。 コンテンツアプリケーション •PHProject [GW] エンジニ ｺﾗﾎﾞﾚｰﾃｨﾌﾞ •EGroupware CRM ERM SCM • Dokuwiki [Wiki] • jGnash アリング • WebGUI [CMF] • phpBB [GW] •OBM [GW] • Enterprise CRM and ア • Tiki Tiki CMS Groupware • ProcessMaker • CorneliOS [CMS] • Ariadne Groupware System • Task Juggler [PM] • Blender オペレーション • TinyMCE [DCM] • XODA • Simple Groupware [GW] プ • OpenWebMail[webmail]• Teamwork [GW] • Dolibarr • Achievo [PM] • mxGraph 製造管理 • Drupal [CMS] • mnoGoSerch • LedgerSMB • white_dune • eZpublish [publish FW]• Managing • ZIm [blog] • Plans [GW] • The Apache Open リ • Tine2.0 [CRM&GW] • GnuCash • Jgraph • OTRS • XWiki [Wiki] • Midgard • Zimbra [GW] for Business • Elastix • GroupOffice [GW] • Twiki [KB] • TUTOS[ERP&PM] • graphviz • FUDForum • OpenSearch Project ｺﾝｼｭｰﾏ 系 • SquirrelMail [Webmail] • Time Trex • BRL-CAD • Asterisk • Plone CMS Server • Citadel [bbs] •
    [Show full text]
  • ITIL: Microsoft and Open Source
    ITIL: Microsoft and Open Source ITIL: Microsoft and Open Source White Paper Microsoft Corporation Published: October 26, 2007 1 White Paper – ITIL: Microsoft and Open Source Contents ITIL: Microsoft and Open Source ........................................................................................ 4 Introduction to ITIL ............................................................................................................. 4 Service Support ............................................................................................................... 5 Service Delivery ............................................................................................................... 5 History of ITIL ...................................................................................................................... 6 Benefits of ITIL .................................................................................................................... 6 IT Service Support: Incident Management ......................................................................... 6 Definition ........................................................................................................................ 6 Product Comparison ....................................................................................................... 7 Open Source ................................................................................................................ 8 Microsoft ....................................................................................................................
    [Show full text]
  • OTRS 2.3 - Admin Manual OTRS 2.3 - Admin Manual Bora Bora Edition Copyright © 2003-2008 OTRS AG
    OTRS 2.3 - Admin Manual OTRS 2.3 - Admin Manual Bora Bora Edition Copyright © 2003-2008 OTRS AG René Bakker, Hauke Böttcher, Jens Bothe, Udo Bretz, Martin Edenhofer, Manuel Hecht, Christopher Kuhn, André Mindermann, Henning Oschwald, Thomas Raith, Stefan Rother, Burchard Steinbild This work is copyrighted by OTRS AG. You may copy it in whole or in part as long as the copies retain this copyright statement. UNIX is a registered trademark of X/Open Company Limited. Linux is a registered trademark of Linus Torvalds. MS-DOS, Windows, Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP and Windows 2003 are registered trademarks of Microsoft Corporation. Other trademarks and registered trademarks are: SUSE and YaST of SUSE AG, Red Hat and Fedora are registered trademarks of Red Hat, Inc. Mandrake is a registered trademark of MandrakeSoft, SA. Debian is a registered trademark of Software in the Public Interest, Inc. MySQL and the MySQL Logo are registered trademarks of MySQL AB. All trade names are used without the guarantee for their free use and are possibly registered trade marks. OTRS AG essentially follows the notations of the manufacturers. Other products mentioned in this manual may be trademarks of the respective manufacturer. Table of Contents Preface ........................................................................................................................................................x 1. Basics about trouble ticket systems......................................................................................................1
    [Show full text]
  • Und Open-Source-Einführung Im Auswärtigen Amt
    Dieser Artikel ist Teil des Open Source Jahrbuchs 2007 GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA Everyone is per- mitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation‘s software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to yourOpen Source Jahrbuch 2007 programs, too. BerndWhen we Lutterbeckspeak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that youMatthias know you Bärwolff can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the soft- ware, or if you modify it.
    [Show full text]
  • Documentation Manual Do OTRS Business Solution™ 6
    Documentation Manual do OTRS Business Solution™ 6 Build Date: 2017-09-27 Manual do OTRS Business Solution™ 6 Copyright © 2017 OTRS AG Este trabalho é registrado pela OTRS AG. Você pode copiá-lo em todo ou em parte desde que mantenha esta declaração de direitos autorais. Todos os nomes são utilizados sem a garantia de seu uso gratuito e são possivelmente marcas registradas. Todos os produtos mencionados nesse manual podem ser marcas registradas dos seus respectivos fabricantes. O código fonte deste documento encontra-se em t github, in the repository doc-otrsbusiness. As contribuições são bem-vindas. Você pode auxiliar traduzindo-a para o seu idioma em Transifex. Table of Contents 1. Introdução .................................................................................................................. 1 2. Atualizando para OTRS Business Solution™ ......................................................... 2 3. Características da OTRS Business Solution™ ........................................................ 3 1. O Chat ................................................................................................................ 3 1.1. Descrição ................................................................................................. 3 1.2. Configuração ............................................................................................ 3 1.3. Setup ........................................................................................................ 5 1.4. Uso geral .................................................................................................
    [Show full text]
  • Bacula Monitoring Mit Nagios Oder Icinga
    http://www.netways.de Bacula Monitoring mit Nagios oder Icinga Julian Hein – NETWAYS GmbH NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Agenda . Kurzvorstellung . Nagios Einführung . AddOns & Erweiterungen . Bacula Überwachung . Fragen & Antworten NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de NETWAYS GmbH Kurzvorstellung NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Allgemeine Daten . Julian Hein . Firmengründung 1995 . GmbH seit 2001 . Open Source seit 1997 . Nagios / Netsaint seit 1999 . 20 Mitarbeiter . Sitz in Nürnberg NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Leistungsbereiche Open Source Open Source Systems Management Data Center Solutions . Monitoring . High Availability Lösungen . Performance Management . Cluster Lösungen . Configuration Management . Loadbalancing . Service Management . Virtualisierung . Knowledge Management . Speicherlösungen . Asset Management . Firewalls . Identity Management . Datenbanken . Backup & Datensicherung . Voice over IP Managed Services Monitoring HW Veranstaltungen NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Konferenzen 4. Monitoring Conference (OSMC) . Mehr als 250 Teilnehmer . 5 Tracks mit Vorträgen & Workshops . 28. - 29. Oktober -> http://netways.de/osmc 2. Open Source Datacenter Conference (OSDC) . Mehr als 80 Teilnehmer . 3 Tracks mit Vorträgen & Workshops . 26. – 27. Mai -> http://netways.de/osdc NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Eigene Nagios AddOns und unzählige Nagios Plugins NETWAYS GmbH . Deutschherrnstr. 15-19 .
    [Show full text]