We all agree that tracing a bug in a monolithic app is hard, but this tracing gets even harder in a distributed solution, since we've many different services running on different machines may be involved in responding to a single request.Not only for debugging purposes, it’s essential that
I'm not a big fan of Websphere application server (at all), but I found myself lately dealing with it and I think it worth sharing my small experience with WAS on setting up a CD pipeline using Jenkins CI. This write up is based on WAS 8.5.5 and
Last week, I've wrote a post about setting up a port forwarding strategy manually on a kvm/libviert network. Today we'll automate this process taking advantage of the many cool feature of libvirt. As explained in the previous post, We want to to make a service that is on a
I've been playing in the past few weeks with kvm/qemu and libvirt to set up some VMs. If you've been using libvirt before, you'll for sure agree that Libvirt is particularly awesome when it comes to managing virtual machines, their underlying storage and networks. However, if you happen to
If you've been using Elastic stack, you've probably faced the issue of using kibana with multiple elasticsearch instances and got the frustrated answer: NO, kibana only support one Elasticsearch instance to use for all the queries. Many issues have been opened on github and asked on the Elastic Forum on