here's a screen grab- after changing the query, I hit enter

Hello,

I'm sorry but I cannot see how this is undesired or dangerous behavior, we maintain the input value across the different environments so the user does not have to retype.

Best,
Brody

I'm sorry but i cannot see how this is intended:
1. I'm in "production" environment in the Logs applet. Let's say my query is "hello brody".

2. I switch to "staging", the query stays the same - "hello brody" (correct!)

3. I change the query to "hello daniel", then hit Enter. The new query is run, but the environment automatically switches from "staging" to "production". So rather than querying "hello daniel" in "staging", i'm now querying "hello daniel" in "production", even though all i did was change my query.

That is wrong. By changing my query I did not intend to switch the environment as well.

If something like this were happening when making architecture changes, that could be dangerous. I would hope that if I'm operating under the assumption that I'm making changes to one environment, those changes wouldn't inadvertently impact another (as it seems that the environment can switch without my explicit action). I haven't experienced this exact thing outside of logging, so it's merely an inconvenience for me.

IDK how your code works, but my hunch is that if something like changing a query in the Log search bar can change the environment without explicitly selecting a new environment, something may be wrong with that UI component.

Just trying to do my part to alert the team to potential bugs- hope that helps!

Ah thank you for the further explanation, I'm seeing the issue here.

I will ticket this.

Update: An internal ticket linked to this thread has been changed to In Progress.

^ Should be fixed now!

awesome- thanks!