Fabian Stäber from Instana, gives a really informative talk about how to tackle monitoring with microservices.
Lots of things to consider:
- Automation of monitoring to avoid bottlenecks with deploying microservices.
- The underlying data
More than health checks which are more common with monoliths.
Define what does it mean for my application to be healthy. Discussing how you take this time series data and apply it to the additional dimensions that microservices bring.
- Aggregation horizontal metrics
- Vertical checks – what is going on in the stack Java, JVM, Docker, K8 node, hardware itself.
- Ensure new and legacy services also provide tracing
- Tie together traces to error logs.
Fabian helpfully points out these three Site Reliability Engineering books from Google that are available for free.
Jessica Deen gives a great introduction to Helm and then goes on the show the differences between Helm 2 and Helm 3.
Great news Helm has graduated.
Here goes nothing:
brew install helm
Watch again later:
- Helm 3 has been rewritten to be more k8 native, simpler and more flexible.
- There are changes to
- Also need to explicitly create namespaces.
Jessica Deen also demonstrates migrating with the use of helm-2to3 plugin
The live demo made use of codefresh CI/CD a tool designed for deploying to k8
Gareth Rushgrove, from Snyk, gave us an overview of some more advanced features in Dockerfiles which can promote the reuse of Dockerfiles. This is turn can be combined with neat github actions.
Watch again at: https://docker.events.cube365.net/docker/dockercon/content/Videos/SPWM3BdnCZWPN4fN9
Thank you, Golang Bristol, for hosting a warm and friendly workshop last night. As well as exploring some core Go language features I was able to do some pair programming with Samuel. You can find the resulting forked Go tutorial repo on GitHub.
Preparation for the workshop was really easy, setting up my Ubuntu laptop was a straightforward system package installation. I was able to very quickly get my Hello World on. So far the documentation seems straight forward to follow.
Post-workshop pub discussions about the benefits of using Go were helpful too.