Last week you automated the deployments: every merge now tests itself, builds an image, and ships to Render without you. Which means your app is out there right now, running, serving requests, and completely out of sight. But how do we know if our application still runs and not crashed? How can be sure that it works properly? What if we have not one but 100 difference API services to monitor?
This week you grow new senses. You will make your Spring Boot app tell you what it is doing through structured logs, ship those logs off the server to Grafana Cloud so they outlive the container that wrote them, and expose a health endpoint that Render can watch on your behalf. Then you will use only those signals to hunt down a bug that may have been quietly deployed. By the end of the week you can answer the question every backend developer is often asked: "The service is slow / throwing 500s - can you find out why?"
application.yaml, and decide what is worth logging and what is noise.The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*
Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.