How logging works on GOV.UK
Each machine sends its syslog to a central
logging machine (logging-1.management) which listens on UDP port 514.
The logging machine sends all the syslog messages it receives to a local logstash, which sends
those logs to
The logging machine keeps the logs at
Logstream, logship and redis
We have a defined type in our Puppet code which uses logship to tail logfiles.
The tailed logs are sent to
logs-redis machines. The logging Elasticsearch cluster has a
river to pull logs from redis.
logship provides multiple shippers. We’re using the redis shipper and the statsd shipper (for sending nginx status codes to Graphite).
Logstash runs on the
logging machine. It listens for data on TCP and UDP ports which are specified
in its config and then applies filters to the log lines.
grok patterns for applying filters. A useful tool to test patterns is
The output for logstash is our logging Elasticsearch cluster.
We run a logging Elasticsearch cluster:
fab production class:logs_elasticsearch hosts
We use estools to rotate Elasticsearch indices daily, and apply
an alias of
logs-current for the current day’s logs.
Kibana is the interface for viewing logs in Elasticsearch. We made kibana-gds as a wrapper to put Kibana behind GOV.UK Signon.
It’s deployed to the backend application servers.
There’s some documentation on useful Kibana queries for 2nd line.This page is owned by #2ndline and needs to be reviewed