3 Pro Tips To Get The Most Out Of Qovery - Part 1
1. Filter the logs
For the first tip, we’ll be speaking about logs; let’s say you have plenty of pod names in your application logs. Still, suppose you want to focus on only one. In that case, looking for all the pods with the same name can become quickly messy and time-consuming. To avoid the headache, you can filter the logs by pod name.
How does it work?
- Head to your application logs
- Click on the pod name you wish to select
- A filter will make only the one select visible.
- To unselect, click on the cross near your pod name
Here is a small video to show you how it works in action 🎬
2. Cost Optimization
Developers in your company work from 9-to-5, five days a week. Keeping all development environments running during the weekend, at night, and outside working hours may be a considerable expense that gives you no benefits.
Using the Deployment Rules is a good practice to reduce your cost drastically. Indeed, Qovery knows how to optimize your Cloud resources when your applications are not running. Then you can expect to reduce your Cloud cost by up to 60% using the Deployment Rules.
How does it work?
- Navigate to Console
- Select your project
- In the project overview, click the Settings button:
- In the popup, select Deployment Rules and add New:
Then you need to add the rules that apply to your company, and all set 🤩
3. Clickable message on Rollback
This tip will be handy if you are using the rollback feature (more about it on this changelog); when you make a rollback, the commit messages are clickable, so you can easily access your commit on git without having to search for it for hours, camera, live, action!
How does it work?
- Head to the console and in your application, click on the action panel.
- Then click on deploy other version and choose the version you want to open.
- Once clicked, you will be automatically redirected to the Git page of the selected branch.
Magic, isn’t it? 🪄
Wrapping up
Whether you’re planning to filter the logs, click on a rollback message, or start with cost optimization, I hope that those small tips were helpful to you and if after your time spent on Qovery you have tips or tick, don’t hesitate to post it on the forum and maybe we can even share one of yours in the second part 🚀
.svg)
.svg)
.svg)
Suggested articles
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
By adopting GitOps and utilizing management platforms like Qovery, fintech teams can automatically generate DORA-compliant audit trails, transforming regulatory compliance from a manual, time-consuming chore into an automated, native byproduct of their infrastructure.
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
.webp)