1307271 - Use structured logging for logins, role/client changes

Status: RESOLVED FIXED

(Taskcluster :: Services, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

We will likely find ourselves wanting to quickly find all modifications to role X, or all uses of client Y during a particular timeframe.  Structured logging will be really useful to that end.

Comment 1

[Jonas Finnemann Jensen (:jonasfj)]

Isn't this sort of less important, now that we have audit log?

Comment 2

[Brian Stack [:bstack]]

Sorta kinda but we should still figure out the structured logging stuff.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

Which is https://github.com/taskcluster/taskcluster-rfcs/issues/35

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

Brian, is this more of an audit-logging thing now?  Could we repurpose this bug for that reason?

Comment 5

[Brian Stack [:bstack]]

Yeah, I think maybe medium term what we call "audit logs" now will just be structured logs for all tc stuff.

Comment 6

[Brian Stack [:bstack]]

This is ready to be worked on, I'm just not going to do it right now.

Comment 8

[Dustin J. Mitchell [:dustin] (he/him)]

https://github.com/taskcluster/taskcluster/issues/662 will handle the "logging logins" part of this /cc hassan

Comment 9

[Dustin J. Mitchell [:dustin] (he/him)]

I think monitor.apiMethod has sufficient information in it to extract the remainder.