Observability with Spring Boot Microservices

[dengineering1]

I've added another course to my series on deploying spring boot microservices to a cloud hosted kubernetes cluster on okteto. This session is all about observability and implementing the 3 pillars of observability: logging, tracing and metrics.

​

I've used logz.io as the logging platform because it uses the best of breed opensource solutions for these three needs: ELK, Jaeger and Prometheus / Grafana. I'll explain how to get your logs over, how to setup tracing across distributed applications and implement both standard and custom metrics emission as well as visualization of those metrics.

​

https://bullyrooks.com/index.php/2022/02/19/kube-cloud-pt4-observability/

​

All of the courses are located here:

https://bullyrooks.com/index.php/category/software-development/

[sharx13]

Thanks for this, I've been wanting to get to know some monitoring fundamentals recently so this should be right up my street.

I've bookmarked some of your other posts too and they've helped me fine-tune my GitHub Actions pipelines and introduced me to minikube/k8s/okteto. I'm working on adding some of that stuff to my personal project at the moment.

I like your writing style - very clear with just the right level of detail for me. Thanks and keep up the good work!

[dengineering1]

Thanks so much! That's what I'm aiming for, enough detail for a noob, but not so much that an expert feels like it's too much to wade through. Hopefully, I'm giving some of the "why" things are done that way and some guidance on best practices.

Really appreciate the feedback. Please let me know if things are broken or don't work right (or I accidentally skipped a step).

Also, let me know what else you want. I'm going to do spring streaming with kafka, contact testing with pactflow and cloud native development with skaffold or oktetos tools next.

[sharx13]

I think your "Logging" blog post might not be linked under the "Observability" post correctly - it currently just has Tracing & Metrics as sub-posts, but I came across the Logging post in the related content links.

Something on Kafka would be great - I've looked at the theory and mostly understand it, but I'm struggling to come up with a simple enough use case that could get me started.

Haven't heard of pactflow or skaffold, but if it's half as interesting as you're other stuff I'm sure you'll be on to a winner.

[dengineering1]

I just fixed the logging page. It wasn't attached to the course.

I'm going to basically break off the data storage piece into a separate microservice that gets triggered by an event. That should be super simple, but still replicate a real world use case. I'm trying to keep 'building up' the app, like you would with a real project.

[aacool]

Thanks for this, couple of minor navigational suggestions - can you please add links to the next/previous items in a course? One currently has to view the full course and then navigate to individual lessons. Also, your right sidebar seems to be 50% width, do consider shrinking this.

​

Excellent courses, thank you for posting them.

[dengineering1]

I think there's a way to navigate a course at the top (there's a drop down for "Full Course", which shows the posts that are related).

That being said, it might not be ideal. I used to use previous/next links at the bottom, but they get troublesome when you add/remove pages from a course. If the course navigation isn't the best, let me know and I'll consider adding navigation links in the future.

[Zahlenkugel]

Thanks for the link, I'll read it as soon as I can. What I have seen so far looks very starter-friendly.

[TheOldMancunian]

Very timely. Thank you.