even the stupid ass ai says:

The HTTP logs tool is broken on the backend right now—it's returning validation errors.

Your best option is the deployment logs I just pulled, which show all requests and responses. That's the live traffic data.

If you need something specific from HTTP logs (like filtering by status code, path, or method), I can search the deployment logs with those filters instead. What are you trying to find?

furthermore if i click the activity toggle, it toggles the toolbar in every single railway window that has my project open, in my browser. (same with agent)

can you just give us a normal interface and not ship half baked code?

whoever did this would be fired for breaking production on my own app. your standards as a infrastructure provider are weak and leave me wondering how much ai slop you'll use that might eventually break the reliability of the platform.

The HTTP logs aren't broken and haven't gone anywhere.

https://railway.com/project/2cfdebb0-be71-4807-bc0b-9984236c0b0f/service/ddfb31a0-73a6-4e68-a716-af827094c49c?environmentId=ec7c1944-a2c9-4b4e-8ab5-308834c5926a&id=c1df9d85-16d1-49fc-8d95-420121092358#http

railway logs from the CLI fails right now. i just tested it. Brody you're full of shit.

i recorded it for you. don't lie to customers. fix the platform.

furthermore the real logs screen is supposed to look something like the image attached.

however this view/window is no longer available.

finally the GUI is half baked and doesn't isolate activation per window.

here are two screencast recordings that show the error and my own website that runs on railway and doesn't exhibit such bullshit behavior.

please stop gaslighting customers and fix the UI and the logs. even your own ai said it was broken. i have documented it and show you the errors. FIX IT stop denying the truth.

the fact that the CLI command to show the logs fails completely is high level gaslighting. this ai slop code and interface doesn't help you probably fired the actual developer or vibe coded the interface and that's why this is breaking.

this is utterly pathetic. stop typing and fix the code brody.

The CLI does not support displaying HTTP logs, so if you want to see deploy logs, make sure your CLI is linked to your desired service.

the CLI DID support showing HTTP logs and i was monitoring it last week with that command. it's even in the CLI command list.

FIX THE CODE STOP DENYING YOUR FUCKUP.

There is an open PR to add support for HTTP logs to the CLI - https://github.com/railwayapp/cli/pull/810

It's not merged yet, still under review, so until that is merged, the CLI won't support HTTP logs, only deploy logs.

before the interface change and 1 week ago this log command worked. You guys broke the platform. Fix it instead of denying.

If you want to see deploy logs from the CLI, make sure your CLI is linked to your desired service.

BRODY STFU https://docs.railway.com/observability/logs

even your own webpage and company manual shows the command worked https://res.cloudinary.com/railway/image/upload/v1694195563/docs/CleanShot%5F2023-09-08%5Fat%5F10.52.12%5F2x%5Fyv1d7f.png

I see there is some confusion here. Those are deployment logs from an application that prints its own HTTP logs to stdout, not Railway's HTTP logs that we gather from our proxies.

i am successfully linked. the logs command failed. look at your own manual you provide customers. i'm sick of your bullshit. stop denying this shit.

brody you fucked up and you can't pull a fast one on me.

i dont want to read anymore bullshit replies. fix the broken interface and fix the broken logs system. you guys had an outage related to this and i saw the issue tracker. dont lie to me.

you can keep trying to get the last word but it wont fix the broken system.

Going to close out this thread, as we are just going in a loop. Deploy logs from the CLI do work; we have no other reports of such issues, and, not to mention, you are being extremely disrespectful.