--- title: "Disk Usage Alerts, Template Payouts Are Coming, RFC for PR Environments" date: 2024-05-03 number: 0184 url: https://railway.com/changelog/2024-05-03-disk-usage-alerts --- # Disk Usage Alerts, Template Payouts Are Coming, RFC for PR Environments Welcome to another week of riding the rails with us. Before we get started, we wanted to let you know that we have a couple spots remaining in the first batch of the [Railway Startup Program](https://startup.railway.app/). Please read the criteria carefully and drop us an application if you think it’s a fit. Next up, let’s talk about the in-app alerting that we’re starting to ship, the dollar-denominated (rather than credits-denominated) template payouts that we’re about to unfurl, and one the recent features we’ve shipped that needs your precious feedback. Ok? Ok! Let’s go. ## Disk Usage Alerts [Video: Disk usage alerts provide a visual indication in the dashboard when your attached volumes are getting full] You wake up, it’s 3 AM to Slack pings from your customers. Your app is down. You jump on Railway and see that your volume is full. You start cursing to the sky. “*Railway doesn’t warn me when I am near my limit? Well I am at my limit! I’ve had it on this garbage product!*” You then ask your friend for a Kubernetes book. End scene. Well, hold up. Put the book down. Because we are coming through with our investment in … **Alerting** This is a big topic because there’s a lot of pipework that needs to be run, a lot of data to be streamed, and a lot of distribution channels to deploy. It’s a lot of complexity. Now we have the first steps of that plumbing in. This week we are introducing an alert for your [Volumes](https://docs.railway.app/reference/volumes). Now if they are approaching their limit, we will update the dashboard with new UI and an event in the sidebar. Caveat here that like everything we build, we roll it out incrementally with [your feedback](https://help.railway.app/feedback?sort=highest_votes). We mention this because we are really trying to focus on reliability of our alerts so *now* there may be hiccups … but it’s an important first step in our plans for improved monitoring on the platform. We’ll be adding more soon, so stay tuned. ## Template Payouts Are Coming [Image: Real payouts are coming soon to the Template Kickback program] In the next few weeks we'll be rolling out real-cash-money payouts for [Template Kickbacks](https://railway.app/open-source-kickback). The template ecosystem is growing into a place where companies and developers can make serious dough building and maintaining templates. There are already some community users who have earned *thousands* of dollars in kickbacks — in fact we've paid out almost $30k to date. (Track the growth [here](https://x.com/Railway/status/1786585216599167301).) Problem is, to this point (and *just* a bit longer), transferring your template kickbacks into real cash-money has been difficult. With Payouts, you'll be able to request a withdrawal of your available kickback balance to a number of payment platforms: Buy Me a Coffee, PayPal, and GitHub Sponsors. Template creators with a significant balance of kickback credit- please form an orderly line on Discord where Matt will give you a special role so we can coordinate the early version of this program. Some time after that, we’ll move to in-house payouts so we can save the community on withdrawal fees.* (aka financial egress fees, yea, we don’t like egress fees either)* ## Request for Comments: PR Environments [Video: Enable PR environments from the Settings panel in the dashboard] Many developers on the platform tell us they love the [PR environments](https://docs.railway.app/guides/environments#enable-pr-environments) on the platform. However, as much you can love something, you can also hope for it to grow. This is us at your front door holding a sign asking you to give us some feedback. Ignore the boombox. So … let’s talk about PR Environments. The Railway team has a number of ideas for where we can see PR Environments heading since we have now have features like [Staged Changes](https://docs.railway.app/guides/staged-changes) and [Config as Code](https://docs.railway.app/reference/config-as-code). We **especially** want to know how you are using PR Environments on your project, or what should be different. As always, we have opinions but we want to know what **you** think. [Thread up](https://help.railway.app/feedback/calling-all-passengers-pr-environments-3fe48685) or fire off in your connected Company Slack channel! ## Fixes and Improvements - We shipped a blogpost about how we run Railway on Railway. You can find it [here](https://blog.railway.app/p/building-railway-on-railway) - We added support for `teamId` when generating a template from project flows - We fixed a bug where team API tokens wouldn't work with the `serviceConnect` mutation - We plugged-in more [Railway Metal](https://railway.app/changelog/2024-04-26-startup-program) (Start head banging soon) - We added a number of fixes on logging to decrease logging latency for intensive applications - We fixed a bug related to accessing logs via API - We also added a helper to find the [App Sleeping](https://docs.railway.app/reference/app-sleeping) setting by typing “serverless” into the settings search 😉