--> dnj@
We could build the url manually in cbuildbot and create a link. Is this the way to go, or is there a better way to get this functionality? None of the logdog logic is in cbuildbot, so it seems to be the wrong place for url manipulation.

If it's down to custom URL, please assign this bug to me.

ping. This is easy to implement in cbuildbot, but that seems to be the wrong place for it.
We should add it to the same place where the rest of the logdog links are genearted. PTAL.

Once we do this, we can start removing the buildbot log links (why have duplicates, especially because people keep linking to the ephermeral logs by habit)

I haven't had much time to work on LogDog stuff lately, sorry. The place to implement this is definitely in "Annotee", the LogDog tee parser, not cbuildbot. Is this something that is >P2?

Not >P2.
Can you ping me a link to the code anyway? :)

Sure! The program that emits the links is called "Annotee", and is homed here: https://github.com/luci/luci-go/tree/master/logdog/client/annotee

Basically it sits in between the running process (recipe engine, cbuildbot) and parses the STDOUT/STDERR streams. It tees the data to BuildBot (injecting links as needed) and also tees the data as a LogDog stream.

In this case, we would want to emit an "alias" link called "stdio" in the first step, and alias it to "<prefix>/+/**/stdout" and "<prefix>/+/**/stderr".

I have no idea who decided to do this (dnj?), but I can confirm that an "all" link has now appeared on the buildbot build landing page.

Yeah I put this in on Friday. Didn't even think of this bug when I did it, so cool free bug fix.