You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we want to enable some more in depth logging on the front end (especially logging of errors), it would be handy to have an endpoint to which we can submit log reports. I'm not sure if we want this one to be used by anything else or just the frontend (could make it accessible to other third party apps to submit reports but need to be careful about spam).
I propose a POST only endpoint at /logs. Schema will need to be decided but will be quite flexible.
The text was updated successfully, but these errors were encountered:
This won't scale and I think is best avoided, it might make sense for a single client but as soon as we have multiple clients all operating independently the logs will become less useful (also the size of them will rapidly become unmanageable). Better I think just to log attempts to use the gateway and then keep client logs separated.
In that case keeping it internal only seems like a better option. I am going to transfer this over to the frontend repo and adjust it slightly because I will address front-end logging when I get around to the logging and analytics side of the project
If we want to enable some more in depth logging on the front end (especially logging of errors), it would be handy to have an endpoint to which we can submit log reports. I'm not sure if we want this one to be used by anything else or just the frontend (could make it accessible to other third party apps to submit reports but need to be careful about spam).
I propose a
POST
only endpoint at/logs
. Schema will need to be decided but will be quite flexible.The text was updated successfully, but these errors were encountered: