16-17 Centralised Application Logging

Proposal Sponsor:

Stefan Kaempf

Overview

Need

Other contributors:

Richard Good

What would happen if the project did not take place?:

Logging is per application, per server. Individuals would have to log into each server manually and read the logs manually. We would also keep separate database logs for support purposes, which would have to be queried manually. Security of server/database access would continue to be a concern. Individuals would continue to receive a large number of emails related to application information and errors.

Additional information:

We don’t have an effective method of proactively monitoring application errors/exceptions at the university. It is highly likely that there are are errors in our log files that we’re not aware of.

Currently logs are stored on multiple servers and some run-time errors are sent via email to a mailing list, which most Production Management staff subscribe to. The volume of errors is high, which mean a large number of emails going to a range of people. It's not easy to proactively make sense of errors that occur by filtering the thousands of emails, and there is a better way to do log management.

Additionally, access to production servers is required so that support staff can look at logs, which creates an additional security concern.

This project would look to implement a centralised monitoring tool for application logs, either by using the in-house Microsoft SCOM software, or a free piece of software like Sentry (https://getsentry.com/welcome/).

Who does it affect?:

Support staff

Why is it needed/What are the benefits?:

To introduce a scalable solution for monitoring our application software.

Particular benefits are:

Allow a central point for monitoring of applications
Allow support staff to better understand problem points in our application estate
Allow reporting on error rates across applications for KPI purposes
Allow better understanding of the impact of software releases
Remove the need for support staff to manually log into production servers, and therefore improve security.

BI/MI requirement?:

n/a

External costs?:

n/a

Compliance justification (if relevant):

n/a

Fit with University strategy:

Goals – Excellence in Education		Infrastructure updates - enable better cross-application monitoring and reporting - rationalisation of logging to enable easier support and reduce costs - to increase security by removing the need to log into servers manually.
Goals – Excellence in Research
Goals – Excellence in Innovation
Enablers - People
Enablers - Infrastructure	x
Enablers - Finance
Themes – Outstanding student experience
Themes – Global Impact
Themes – Lifelong community
Themes – Social responsibility
Themes – Partnerships
Themes – Equality & widening participation

Planning Status:

Proposal

Programme Priority:

Overall Priority:

Portfolio:

ISG

Planned Start:

16/17

Multi-Year:

Project Owner:

ISG

Procurement > £50K:

Funding Source:

Core Grant

IS Admin Tab

Estimation Type:

3rd Party IT Solution Implementation

Estimation Confidence:

Highly Confident (done this before)

Estimated IS Apps Days:

Small

Estimated Business Partner Days:

Small

Estimated Service Management Days:

Small