Consider democratizing access to production logs #135
Description
I am interested in investigating instances of unexpected Highfive behavior. For example, sometimes, but not consistently, Highfive sends the welcome message to existing contributors. Another example: in rust-lang/rust#49849, Highfive did not take any action at all. It's difficult to know what is going on there without access to the logs. Looking at Highfive's code I can speculate that maybe the diff request failed, but there's several other possibilities.
The first question is: are the organization members comfortable granting access to the logs to a non-member?
If the answer is yes, we should find a reasonable, low-cost-to-@nrc way to accomplish it. A lot of options come to mind, but they generally branch on whether we want to provide access to the host Highfive runs on or whether we want to ship the logs to somewhere else.
- Provide access to host running Highfive.
- Continue running Highfive where it is now?
- Move Highfive to another location?
- Ship the logs elsewhere.
- Add application logic to handle this?
- Use external process to ship logs to somewhere?
I'm happy to talk more about the possibilities, if the answer to the first question is yes.