When only one resource is in the app host, we should default to that resource in the console logs page instead of [none]

[maddymontaquila]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

No response

Describe the solution you'd like

~35 min into today's AspiriFriday (will post link later) - we created an app host with just one resource, and the console logs page still defaults to [none]. It would be nice if this defaulted to the sole available resource!

Additional context

No response

[willdean]

So pleased to see my favourite irritation appear in the live stream!

But could the [None] option just go away altogether?
Who would ever want to select a specific option (from a drop-list, of all UI horrors) just to allow themselves to stare at a blank browser window?

[davidfowl]

None could could be all like structured logs

[willdean]

None could could be all like structured logs

I was going to make a "witty" (facetious) reply about whether it would be most entertaining to interleave the different streams by line, by word or by character. But obviously you would actually tag the lines with their source somehow.

And that made me think: tagged console lines in a readonly console are like structured logging anyway. Could you get rid of the console altogether and just tag console lines appropriately and feed them into the structured logging. That would mean:

• There's only one place to look for problems - the console vs logging distinction is fairly arbitrary anyway.
• Psuedo-service-console sources (like providing the app-host console which comes up every Friday) would be less of an outlier
• It might be possible to lean on filtering which was provided for structured logging to make stuff easier to find within console output.
• Dev effort can be focused more tightly on making the structured logging better.

Has this been discussed?

[davidfowl]

No I don't think it makes sense to merge these views or remove any existing views. Console needs to be remain to be the lowest level way to see the output of a process.

I did file this though #7257 because I do think there's an opportunity for visualizing certain types of console logs (for those programs that decide to destroy their stdout stream with JSON).