There are different locations where log data is written to. Here is an overview of the most common places.
Webserver Logs
We have two locations where webserver logs are saved: at the loadbalancer upfront and the application servers.
Loadbalancer
access.log
This is an example entry within the access.log:
A.B.C.D - - [25/May/2018:11:58:38 +0200] "GET /ueber-uns HTTP/1.1" 200 6536 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0" "https" "makandra.de" "0.060"
The information which we log is:
- Source IP address
- Timestamp
- HTTP Request
- HTTP Statuscode
- Bytes sent
- HTTP Referer
- Useragent
- Connection method
- Host
- Response Time
We keep those logs for 8 days.
Application server
access.log
See Deployment where the logfiles are stored.
This is an example entry within the access.log:
A.B.C.D - - [25/May/2018:12:00:39 +0200] "GET /ueber-uns HTTP/1.0" 200 6538 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0"
The information which we log is:
- Source IP address
- Timestamp
- HTTP Request
- HTTP Statuscode
- Bytes sent
- HTTP Referer
- Useragent
We keep those logs for 8 days.
Application logs
See Deployment where the logfiles are stored.
We can't control what you're logging with your application but we can provide logrotate configurations for it.
By default, we keep those logs for 8 days.
Data security
We take data protection and security serious. While logging is an important part of IT infrastructure operations to ensure security, we do not save anything longer than necessary and anonymize data wherever possible.
The retention time of all logs at makandra is as short as possible in accordance with data protection laws in Germany (GDPR) while maintaining the highest possible level of IT security. Retention times are agreed upon with our data protection officer.
Please keep in mind that this information is subject to change in case laws and or best practices in IT security change.
