Skip to content
Log filter @level:warn OR @level:error shows other services’ logs in a service’s log view (depends on term order)
sandsalamand
OP

18 hours ago

What happens

In the log view for one service (our backend), the filter @level:warn OR @level:error also shows logs from our Postgres service in the same project. The leaked lines have that service’s ID. Swapping the terms to @level:error OR @level:warn shows only the backend’s logs, as expected. @level:warn and @level:error used alone also show only the backend’s logs. Bracketing each term, (@level:warn) OR (@level:error), still shows the Postgres logs. Wrapping the whole query in parentheses, (@level:warn OR @level:error), shows only the backend’s logs as expected.

Expected

OR shouldn’t depend on term order, and a service’s log view should only show that service’s logs.

My guess

The service filter is combined with the query without brackets, so it reads as (service AND warn) OR error, and the error term matches every service.

Example leaked lines (from Postgres):

P00 INFO: archive-push command begin 2.59.3: [pg_wal/…] …

SDK 2026/11/15 04:07:20 WARN Response has no supported checksum. Not validating response payload.

IDs

Environment: production

Service where the log filter was applied (backend): 6ec37cdd-3d4a-4617-b9f9-4a5d2d3941c7

Service the leaked logs come from (Postgres): 32449673-ac96-4aed-8f9b-16871492ac0c

Unrelated

While searching the forums, I saw this issue, which is not related but explained by the fact that PostgreSQL spams the deploy logs with "level" : "error" for normal PITR backup logs.

Awaiting User Response

1 Reply

Status changed to Awaiting Railway Response Railway • about 18 hours ago


2 hours ago

You were right about the missing grouping. We’ve fixed how the log view combines your filter with its scope, and the fix is now live. Please refresh the dashboard and try your original filter again.


Status changed to Awaiting User Response Railway • about 2 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...