Shipping your logs to ELK from mule app/cloudhub - Part 1A guide by Alex Fernandez

Logs, Logs, Logs

“A server log is a log file (or several files) automatically created and maintained by a server consisting of a list of activities it performed.

A typical example is a web server log which maintains a history of page requests. “

Logs can contain information including client IP address, request date/time, page requested, HTTP code, bytes served, user agent, and

referrer are typically added. This data can be combined into a single file, or separated into distinct logs, such as an access log, error log,

or referrer log

-Wikipedia

Why do we need logs?

- Incident Reports

- Access Logs

- Analytics

A bird’s eye view of what is happening to the application

Tools that we need

1.ELK stack

2.docker/docker-compose

3.log4j configuration

4.Cloudhub Account

ELK stack

ELK(Elasticsearch, Logstash and Kibana) has been the de facto standard for “Operational Intelligence”

Elasticsearch for indexing logs

Logstash for ‘retrieval’ and ‘forwarder’ of logs

Kibana for visualizing and analysis of logs

Docker-ComposeDocker is an open platform for developers and sysadmins to build, ship, and run distributed applications, whether on laptops, data center VMs, or the cloud.

Docker had disrupted the world of system administration and making it the de facto of building isolated apps.

Docker-compose is a tool used for building ‘docker’ containers as a group using a single command.

Referenceshttp://logging.apache.org/log4j/2.x/

https://en.wikipedia.org/wiki/Server_log

https://github.com/splunk/splunk-plugin-eclipse/blob/master/com.splunk.project.java.ui/resources/log4j2.xml

https://gist.github.com/dsummersl/3744192

https://docs.docker.com/engine/installation/mac/