---
title: "Talk to an Engineer, RFC for New CLI, Fast Logs"
date: 2023-02-10T15:00:00.000+00:00
number: 0120
url: https://railway.com/changelog/2023-02-10-talk-to-an-engineer
---

# Talk to an Engineer, RFC for New CLI, Fast Logs

Happy Friday! We have a mix of updates all focused on improving your experience on Railway.

Let’s jump into the Changelog!

## Talk to an Engineer

[Image: You can now use the Talk to an Engineer feature in the dashboard to reach a Railway engineer]

David and Faraz spent some time looking at the inbound flow on how you can reach us and… it was less than ideal. Want to get a hold of us faster? Now you can. 

We’ve added a new **Talk to an Engineer** button in the profile menu in the dashboard. After you select the dropdown option- you will be able to send us a message straight into our shared inbox.

If you want technical support, we’ll provide technical support. If you want purchasing support, we’ll provide that too. 

Either way, you’re going to get an engineer on the other end of the line to help you out. More to come on this front.

## RFC for New CLI

[Image: Railway CLI]

We’re upgrading and expanding the [Railway CLI](https://docs.railway.app/reference/cli-api) to meet the growing surface area of the product. 

We have questions for you! 

- What commands would you like to see implemented in the next version of the CLI? 
- What aspects of the CLI have been confusing to you in the past?
- Where would you like to see the most performance increases?

Let us know by [dropping us a line in Discord](https://discord.com/invite/railway) in the #cli channel. 

## Logs are Fast Again

The team is working hard to overhaul our services to make things snappier.Build and deployment log latency is now back to a ~1 second delay!

If you’ve viewed logs in the past month you’ll likely have noticed a 5-30 second delay. This wasn’t acceptable, so we did some spelunking and found that a majority of total logs were coming from a handful of misbehaving services — slowing the entire system down. 

To address this, we introduced new throttling logic to prevent a single container from affecting global log latency. We also made sure that these limits are well above any regularly-behaving deployment, so you don’t have to worry.

[Image: Example deployment logs]

## Improvements and Fixes

- Nixpacks upgraded to [v.1.3.1](https://github.com/railwayapp/nixpacks/releases/tag/v1.3.1)
- Fixed a bug when loading V2 metrics
- Numerous improvements on our Templating engine - more to come here!