search

EIDA / mediatorws

EIDA NG Mediator/Federator web services
GNU General Public License v3.0
6 stars 6 forks source link

fed, stl: Configuration (Docker): Logging #39

Closed damb closed 6 years ago

damb commented 6 years ago

Continued discussion about a proper application logging setup.

damb commented 6 years ago

@Jollyfant,

syslog-ng is a system logger facility similar to rsyslog (see e.g. the gentoo wiki on syslog-ng and rsyslog). syslog-ng already ships with baseimage-docker (https://github.com/phusion/baseimage-docker#logging) and

Syslog messages are forwarded to the console.

Hence, still on top you might use the ELK stack. (I've no clue which approach EIDA is implementing. Maybe you know can tell me more about it.)

Logging seems to be quite an advanced topic when using a container infrastructure and there are several ways to go. Moreover, it depends on the infrastructure you have already implemented.

Jollyfant commented 6 years ago

Hence, still on top you might use the ELK stack. (I've no clue which approach EIDA is implementing. Maybe you know can tell me more about it.)

Logging is very muddy at the moment because nothing has been agreed on by the ETC. And we're running a collection of random tools without any coherent infrastructure.. ODC and RESIF are both trying to work with ELK. This (https://github.com/deviantony/docker-elk) works very well since logstash & ES are pretty liberal in what they accept.

damb commented 6 years ago

Ok. What do you think of the following approach?: First we discuss the topic by the ETC. Then we implement a proper (ideally coherent) solution.

Depending on the outcome our most recent container images should be flexible enough to be extended.

Jollyfant commented 6 years ago

Yeah, okay.

damb commented 6 years ago

Implemented with ebf528666e7a8be5664fff2bdb66a0c2e554c72d. @Jollyfant, decided to go for a file based setup using a TimedRotatingFileHandler. Closing.