These Auth Tokens are designed for Server-to-server traffic and we shouldn't be adding an entry to that particular user activity (this should be tracked a little bit differently since by design there will be a lot of traffic here)
At the moment actions like getting the json of an article are not tracked (which is the desired behaviour) now we need to also make the logins. For reference this is the issue that highlighted this behaviour: https://github.com/TeamMentor/TM_4_0_Design/issues/90
A separate issue can be opened for staring to track how we should log and monitor 'downstream' TM servers (or Clients) access. This needs a separate mode or we will pollute the normal user stats
These Auth Tokens are designed for Server-to-server traffic and we shouldn't be adding an entry to that particular user activity (this should be tracked a little bit differently since by design there will be a lot of traffic here)
At the moment actions like getting the json of an article are not tracked (which is the desired behaviour) now we need to also make the logins. For reference this is the issue that highlighted this behaviour: https://github.com/TeamMentor/TM_4_0_Design/issues/90
A separate issue can be opened for staring to track how we should log and monitor 'downstream' TM servers (or Clients) access. This needs a separate mode or we will pollute the normal user stats