Hey @malteish,
If you’re looking for an automated, easy to set up tool to better understand your production cycles costs while keeping your application topped up I recommend looking into CycleOps. Here’s some onboarding documentation that will get you set up with cycles topups, memory email alerts, and more in just ~10 minutes
If your want to evaluate what individual parts of your code might be costing you the most in terms of cycles costs, Paying for resources in cycles | Internet Computer has documentation on the specific cycle costs per operation. Specifically, I’d recommend looking into the threshold signing and HTTP outcall costs. You can also use instruction counter/cycles balance APIs in your code in order to better understand the expensive operations in your APIs.