3 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.
4 Ticketing Systems Use ticket system to follow each case, including internal communication between technicians Each case is assigned a case number Each case goes through a similar life cycle: New Open... Resolved Closed
5 Ticketing Systems cont. Help Request with Tickets Ticket System Helpdesk Tech Eqpt T T T T query from ----> customer --- request ---> <- ack. -- <-- comm --> - fix issue -> eqpt <- report fix - customer <- <-- respond ----
6 RT trac Request Tracker & Trac Heavily used worldwide. Can be customized to your location. Somewhat difficult to install and configure. Handles large-scale operations. A hybrid system that includes a wiki and project management features. Ticketing system not as robust as rt, but works well for web-only ticket interface. Often used for trac king group projects.
7 RT: Request Tracker
8 What's it Look Like?
9 Topics What is a ticket management system Necessities and advantages Common functionalities Practice with RT (Request Tracker) Global configuration Create users Create queues Assign actions to the queues Create message filters
10 Ticket Management Systems Why do we use the term ticket? In order to resolve a problem... Who wants what? Who's going to work on this? When did they ask, when was it done? How much time did it take (billing, hours)? What's left to do? Everything is summarized and presented in a simple and intuitive manner.
11 Applications User support Security problem management Issue Tracking / Incident Management
12 Essential Functionality Several interfaces Web, CLI, , etc. Multiuser At different levels: admin, general user, gues Authentication and authorization Event history Handles dependencies Notifications
13 Components Register an event (i.e., ticket creation) Assign an owner Assign interested parties Maintain change history Inform interested parties of each change Initiative activities based on status or priority
14 Example: Why Used at the UO? Lots of traffic requesting help, services, etc. Archived as text without classification Very difficult to find current status or problem history. Sometimes problems were forgotten or never resolved.
15 RT: Advantages Open source and free Heavily used and tested Very active development Quite flexibile Web interface and via
16 RT: Disadvantages A bit tricky to install the first time... It's powerful, so you'll need to spend some time learning how it works. Most distributions have packages that make installation a bit easier: Gentoo, Debian, FreeBSD, etc.
17 Problem Classification: Queues RT allows you to create queues so that problems are classified by type: Services: DNS, IP addresses, Radius, LDAP Connectivity: Communications infrastructure problems Security: Attacks, scans, abuse, etc. Systems: accounts, passwords, etc General help
18 Site Configuration You'll see this in the installation exercises. Edit the file /etc/requestracknn/rt_siteconfig.pm and edit the variables as needed. For example: $rtname: Short name for the install $Organization: Long name for the instllation $CorrespondAddress: default address for correspondence: $CommentAddress: default address for comments: $Timezone: (Eg. 'US/Eastern') possibly autoconfigured $WebBaseURL: - might want https $WebPath: /rt
19 Web Server Configuration Two Options Virtualhost Subdirectory Root user ('root') Change the default password on first login ('password') Assign the complete for the root account Assign all user rights: Global -> User Rights
20 Gateway Configuration Example using sendmail and rt-mailgate ln -s /usr/local/rt3/bin/rt-mailgate rt-mailgate Add the necessary aliases # vi /etc/aliases rt: " rt-mailgate --queue general --action correspond --url rt-comment: " rt-mailgate --queue general --action comment --url # newaliases Check the configuration # echo testing rt mail -s test
21 User Creation Create a userid for each member of your NOC team. Assign privileges to each user.
22 Create Groups Create groups of users: Administering privileges by group is more efficient that doing so for each user.
23 Create Queues Create queues for problem categories For example security accounts connectivity Assign users to each queue Different between AdminCC and CC Don't forget to create aliases for each queue
24 Scrips (actions) For each queue create automatic actions There is a group of scrips that apply to all queues. Possible to customize per queue or globally scrips are snippets of Perl code
25 Extensions You can extend the functionality of RT. For example: Send daily s to remind users of tickets that have not been taken Send daily s to each user reminding them of their pending tickets. Periodically increment ticket priority You can execute commands via
26 References Best Practical Web site RT Essentials. Dave Rolsky et al. O'Reilly
28 What's it Look Like?
29 What's it Do? Software Configuration Management wiki for collaboration Interface to subversion for change management. Timeline for milestones, progress reports, etc. Ticketing system Integration with
30 Installation You can create a fairly complex trac project... Multiple trac environment configuration. Authentication via trac not Apache. trac user admin via web interface. write-protected for anonymous users. Ability to add subversion later. Aztech calendar plug-in.
31 trac: Some Details Let's look at the wiki... Let's look at the ticketing system... Let's look at different user views... Then we'll install.
32 Sample Trac Projects An open project: Class web server: Fully available live demo: Available installation cookbook:
33 Suggested Trac Exercises Let's do the following: 1.) Install (use the available cookbook) 2.) Review the install 3.) If time, do a few more exercises: Allow anonymous user to see tickets. (add TICKET_VIEW and REPORT_VIEW permissions) Find a plugin you want and install.
Network Management & Monitoring Request Tracker (RT) Installation and Configuration Notes: Commands preceded with "$" imply that you should execute the command as a general user - not as root. Commands
firstname.lastname@example.org DeskPRO Helpdesk Software: Agent Interface Quick Start Guide The DeskPRO helpdesk platform is designed to make it easy to handle problems and questions from your users. Your helpdesk
Data Center Services Production Support Providing Call, Incident, and Change Management for customers throughout the Johns Hopkins Enterprise The Johns Hopkins Health Systems And The Johns Hopkins University
Table of Contents INTRODUCTION... 2 HOME PAGE... 3 Announcements... 7 Personalize & Change Password... 8 Reminders... 9 SERVICE CATALOG... 11 Raising a Service Request... 12 Edit the Service Request...
Parallels Panel Contents About This Document 3 Integration and Automation Capabilities 4 Command-Line Interface (CLI) 8 API RPC Protocol 9 Event Handlers 11 Panel Notifications 13 APS Packages 14 C H A
KANA Express Service Overview Introduction KANA Express provides a complete suite of integrated multi channel contact and knowledge management capabilities, proven to enable significant improvements in
Frontline Service Desk Technical Product Datasheet Meet Frontline Frontline is an all-in-one helpdesk system that helps you track problems and deliver solutions fast and effectively. It enables constant
FileMaker Server 13 FileMaker Server Help 2010-2013 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker,
HelpDesk Connect Operator Manual rev. 1.0. 2003-2009 Eastwright Corp. www.eastwright.com 1 1.System Overview 1.1. Concepts The HelpDesk Connect is a web based help desk system. The program allows efficient
4. Client-Level Administration Introduction to Client Usage The Client Home Page Overview Managing Your Client Account o Editing Your Client Record View Account Status Report Domain Administration Page
e11 Help Desk User Manual Representative Section (Version 4.4) Page 1 of 30 Preface The e11 Helpdesk Representative Manual Version 4.4 is intended for the customer support representatives who are responsible
Liebert Nform Infrastructure Monitoring Software User Manual - Version 4 TABLE OF CONTENTS 1.0 ABOUT LIEBERT NFORM................................................1 1.1 How Do You Contact Emerson Network
PRTG Network Monitor 7 User Manual 2 PRTG Network Monitor 7 - User Manual Table of Contents Part I System Requirements 6 Part II Installation 8 1 Downloading... the Software 8 2 Upgrading to... Version
Getting Started with Richmond SupportDesk Richmond SupportDesk is a Help Desk, Service Management and Asset Management software solution designed for internal support (IT support, facilities management
Managed Workplace 2012 Setup Guide On Premise See All. Manage All. Service All. www.levelplatforms.com TABLE OF CONTENTS Welcome... vii About this Document... viii Where To Get More Help... viii Contact
Copyright 2010 LockLAN Systems Pty Ltd The right of LockLAN Systems Pty Ltd to be identified as author and copyright owner of this work is asserted by LockLAN Systems Pty Ltd in accordance with Australian
Best Practices for Deploying and Managing Linux with Red Hat Network Abstract This technical whitepaper provides a best practices overview for companies deploying and managing their open source environment
Dell KACE K1000 Management Appliance Service Desk Administrator Guide Release 5.3 Revision Date: May 13, 2011 2004-2011 Dell, Inc. All rights reserved. Information concerning third-party copyrights and
Network Management & Monitoring Network and Server Statistics Using Cacti These materials are licensed under the Creative Commons Attribution-Noncommercial 3.0 Unported license (http://creativecommons.org/licenses/by-nc/3.0/)
Case Management Implementation Guide Salesforce, Summer 15 @salesforcedocs Last updated: June 30, 2015 Copyright 2000 2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark
FileMaker Server 12 FileMaker Server Help 2010-2012 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc.
Evaluation Guide Powerful & Immediate Business Web Security via the Cloud Contents 1 Introduction & Product highlights 2 Set up & Configuration 3 Managing your WebTitan Cloud Service 4 Reporting 5 Support
Journyx Technical Document System Administration and Disaster Recovery Guide For Journyx Timesheet version 8.7m5 Document Version: 3.0.9 (January 2012) for version 8.7m5 For product versions prior to 8.7m5