Availability report
This document will describe how to prepare Availability reports for our customers.
Availability report is created to provide system status for the past month the terms and agreement are documented in Support Procedure that were agreed with customer.
For each customer there might be different date till which we should provide this report as well as there might be different metrics that should be included.
Below you will find steps how to create the report, the relevant recipient can be found in Support Procedures documentation.
Report preparation steps:
1. You need to go to 10.0.1.15 and login using qcuser acc
2. Then you need to go to scripts folder where you will find scripts to prepare reports (currently EW and LH)
3. You need to run script generateXXReport.sh (the script will generate report and place it under AvailabilityReport/customer)
4. After report is prepared you need to check it (check downtimes and comments) and adjust it if there were unscheduled downtimes or errors.
- Please check comments for Scheduled downtime as it gets from Nagios comments.
5. You need to copy generated report from AvailabilityReport to AvailabilityReportConvertor/output folder
6. Once the file is placed go to AvailabilityReportConvertor and run makePDS.sh script (this script will prepare reports in PDF format)
7. To receive report from environment you can use 2 options:
- Use SFTP and download it directly to your machine
- Go to AvailabilityReportConvertor/output and use this statement (echo "Report" | mailx -A EW-01-06-2022.pdf(name of the file) -s "EuroWings Monthly Report"(subject can be changed) ops@quintessence.net (using this statement report will be sent to ops mailbox where you will be able to download and check it)
8. Once the PDF is created you need to check it again to see if information and formatting is correct
9. When you confirm that everything looks good you can send the report to customer’s mailbox using OPS e-mail.
- Please use as a subject Availability Report XXXX 20XX (where XXXX stands for month and year)
LH specifics:
LH requires better details (and might have more restarts depending on connectivity issues with MW). As such, procedure is slightly different.
- Connect to MG env and browse catalina.out for server restarts
grep -B 1 "INFO: Stopping servic\|INFO: Server startup" catalina.out | less
-
Add lines to prepared availability report (csv) with data from catalina.out
-
Find the reason for restarts and add a proper description to the line
-
Proceed with pdf file and validation as usual