Books, courses and notes

Changing Logback log level at runtime using etcd watch feature

Until now, we've only set up a 3-node etcd2 cluster in Amazon EC2 and added/removed a node from the etcd2 cluster. This tutorial is less focused in etcd administration and brings a real situation where etcd could help solving a common problem in the real world. Description of the problem Imagine that you have a load balancer and five machines behind it running a spring boot application in production and these five machines have access to an etcd cluster (this is a typical worker scenario when using CoreOS, etcd and fleet in production). Suddenly your team realizes that something is weird with the application behavior, although it's not generating any error logs. In order to find out what's g

FOLLOW ME
  • Black Facebook Icon
  • Black Twitter Icon
  • github-black-icon
SEARCH BY TAGS
FEATURED POSTS
ARCHIVE

Jorge Acetozi is a software engineer who spends almost his whole day having fun with things such as AWS, CoreOS, Kubernetes, Docker, Terraform, Ansible, Cassandra, Redis, Elasticsearch, Graylog, New Relic, Sensu, Elastic Stack, Fluentd, RabbitMQ, Kafka, Java, Spring, and much more! He loves deploying applications in production while thousands of users are online, monitoring the infrastructure, and acting quickly when monitoring tools decide to challenge his heart’s health!

  • White Facebook Icon
  • White Twitter Icon
  • github-white-icon_edited