User Tools
Writing /app/www/public/data/meta/support/daily_status_report.meta failed
support:daily_status_report
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| support:daily_status_report [2016/09/09 16:21] – created cokeeffe | support:daily_status_report [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Daily Applications Status Report ====== | ||
| + | Author: Cathal O' | ||
| + | |||
| + | The Daily Applications Status Report is an email that is sent out from each of the application servers each day. It contains a list of exceptions that occurred in each application as well as data on potential trap parsing issues. | ||
| + | |||
| + | The report emails have six sections. | ||
| + | |||
| + | - Breakdown of exceptions spotted in each application log ordered by frequency | ||
| + | - Breakdown of trap rules that threw exceptions while running | ||
| + | - Breakdown of traps received that had no associated trap rule | ||
| + | - Breakdown of how long traps took to run on the server | ||
| + | - Breakdown of traps that took more than 5 seconds to complete | ||
| + | - Breakdown of traps that did not create general trap summaries | ||
| + | |||
| + | The exception breakdowns are given for all applications (including CAS). The other sections are of course only relevant for servers performing trap parsing. All sections except for the last one are based on data gathered from application logs and thus only reflect exceptions and traps on that particular handler. The last section relies on database queries and thus the data represents all handlers across a given production system. | ||
| + | |||
| + | |||
| + | ====== Second Level Support ====== | ||
| + | |||
| + | Whoever on second level support is on watchdog duty on a given morning is in charge of checking that morning' | ||
| + | |||
| + | |||
| + | ====== Support Leads ====== | ||
| + | |||
| + | Once a week (Monday or Tuesday after a bank holiday) the reports from the previous week should be reviewed by the support technical lead and the most pressing issue in the reports identified. | ||
| + | |||
| + | The Repeating Watchdogs report in the Reporting Manager instance for each customer should also be checked. | ||
| + | |||
| + | What the biggest issue is should be a simple judgement of common sense and technical knowledge and is not something to agonise over - just pick something. An internal support ticket should be opened and assigned that morning to resolve the issue with the intent that it be closed by the end of the week. | ||
Page Tools
