Hello All,
The more we automate the stuff, the better the user experience becomes and also the less we will face client calls.
This will offload some technical work load from the Application Support Engineers and use this time for other feature improvements.
A Quick Overview of the Dashboard Features:
---------------------------------------------------------------
1. Webmin alike feature to manage SSH Session on Web, Local User and Groups Creation on Web and many more.
2. Quickly searching the provided REGEX pattern and providing details in a set of 1000 lines.
3. Able to upload a new log file ( compressed or normal plain text file ) so that same REGEX pattern search can be done on that file or files.
4. Easily Extract the respective grepped log lines into a .TXT file
5. Adding a send on email feature is an addition.
I have personally faced the new of a web based dashboard which is effective for such good debugging.
-----------------------------------------------------------------------------
Requirement of such Web based Debugging Dashboard:
-----------------------------------------------------------------------------
1. Not all client will provide ssh session to the SafeSquid-SWG Instance for troubleshooting purposes.
2. It is hard for the customer end technician to get around with the linux based app troubleshooting.not all technician will be well aware or comfortable with the linux command line.
3. It becomes more time consuming for the technician to get the file and search through the command line.
4. It will make debugging and troubleshooting easy for any technician managing SafeSquid-SWG Instance.
5. Dashboard based Debugging is more convenient for all and it adds a good plus point for SafeSquid-SWG product.
The dashboard attached to safesquid.cfg which can search around the log files using the web interface.
It can also take time stamp as the filter
Fields:
1. Search ( REGEX )
2. Time Frame Filter
3. Log File To Search ["extended", "native"]
4. Count Control
Raw Command Line Approach:
-------------------------------------------------
This is the same way we do we do grep on command line.
The way we get the details about the the approx time when the problem was faced by the client and find the respective file holding the details for that period error and debug info.
And then we do a grep on the file for specific keywords to find the Root Cause of the problem.
Sometimes extended log it self explains the actual problem for that particular url , domain or web application.