PAC - BETA problem and change example
This was written only as a companion example to my tutorial on writing shell scripted web applications. It is an example app and not fully implemented, although it has working problem and change process flows.
Obviously this should never be run on a production server. While believe it or not a well written backend shell script is no less secure than a perl or php one, and far more portable, shell scripts can have the potential to cause a lot more damage if badly written. This is an example app to go with the tutorial, do not use it as a live application.
On the main dashboard for a user when they login there are two panels, the first with all problem groups the user is a member of, the second with all change groups the user is a member of. In each panel there are totals of open/assigned and open/unassigned records by group, with the standard zoom-down functions into each as expected.
- problem functions are implemented
- change functions are implemented
- user can change their own passwords, but no other admin functions have been implemented so config files need to be manually edited
This is the tar.gz file containing the application, there is a README.txt file that explains the extremely simple manual editing steps needed to get it running. The last update made was on 2022/08/18.
The main reason I still consider this 'active' rather than 'archived/deleted' is because as it is written in shell scripts I have found it easy to change many of my custom monitoring tools to automatically raise problem tickets into it, on the local server anyway (at some point I will simply add a netcat script to allow all remote servers to log to it) so can use it as a place to automatically collect detailed problem information from multiple places rather than use many disparate APIs in other tools I use.
Still TODO one day
- create a trivial 'netcat' listener script to allow remote servers to hook into the script to raise anonymous problems from batch jobs
- only if I get around to the above create a nagios/nrpe plugin to report when there are any automatically raised problems
- maybe a cron job to move problems to the APIs of the many other disparate tools I use, effectively everything can just dump errors here and a cron job can then sort out where they need to go rather than having each batch job try and have the smarts to select the correct application to report an issue... in which case the problem function also becomes an issue router which has interesting potential
If you are looking for only a bug tracking system I recomend 'bugzilla' as that is provided by most linux distribution repositories already, and is widely used by large sites and actively maintained. It is however extremely resource intensive even with a single user.
If you are looking for a full blown ITIL complient change/problem/inventory solution I would recoment 'iTop'.