Cybersecurity
DevOps Cloud (ADM)
IT Operations Cloud
This is my first Cool Solution so go easy on me
This article is related to the Data Synchronizer server running on SLES11.
During the initial setup phase of our Datasync server and through to the troubleshooting with devices we had to access the logs frequently, this soon got rather cumbersome.
There must be a better way to diagnose these logs ... let's make something!
We have numerous non-Linux people in our Operations Team who will need ongoing access to these logs to diagnose issues and I needed a way for these people to quickly access the logs to locate the information, so I created a simple script.
This is just a simple bash script with letters to corresponding sequences that grep's and tail's files to show specific information easily.
Here is a screenshot of the interface start screen
Options A thru F are taken from the following link, under Connector Monitoring
Data Synchronizer Mobility Pack Best Practices >
They show:
Option G is one I thought would be useful, by entering the user's email ID the script will then search [grep] for that user's ID from the Pipeline logs.
Option H is handy as it runs options A thru F then emails the output to the system administrator.
Options J, K and L give a brief run down on the log files and what they log.
Options R thru Y continuously output the eight log files so you can watch them live.
Assuming that your log folder is under /var/log/datasync these actions will show you the information specified in each option.
At the top of each of these outputs the 'current time' has been configured to show the same format as the log files, this makes it easy to see when each entry has occurred.
After each option is selected the information from the log is displayed, some options simply search [grep] then display, other options will tail -f [continuously display] and a CTRL C then ENTER is required to return back to the menu.
After you have explored the menu, selected a couple of options, seen the output and returned to the menu you will get the hang of it.
There are several things to confirm / check before running the script.
The initial start screen has been optimized for the default putty screen size of 80x24, if you maximize the putty window you will be able to see more information.
Further development suggestion and possible modifications.