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
{{ message }}
This repository has been archived by the owner on Aug 20, 2021. It is now read-only.
Right now if we log errors or messages they will show up in the console of the dev tools in the browser. This is not what we want as we would not be able to see the messages ourselves unless we are testing.
To best aid a user is to have those messages logged on our server so that we can refer to them when encountering an unexpected issue. Log the issue as well as the logged in user's info so we can find messages related to the user with ease.
Currently I am thinking of having a back end with a REST API hook which we can send messages to and it would write them to logs. We would then be able to access those logs in a dashboard or some form of GUI so we do not have to open the actual file. Is there already a service like this?
The text was updated successfully, but these errors were encountered:
There are services like sentry.io and trackjs.com that provide services like this. They both provide dashboards for this purpose as well as email and slack notifications
Right now if we log errors or messages they will show up in the console of the dev tools in the browser. This is not what we want as we would not be able to see the messages ourselves unless we are testing.
To best aid a user is to have those messages logged on our server so that we can refer to them when encountering an unexpected issue. Log the issue as well as the logged in user's info so we can find messages related to the user with ease.
Currently I am thinking of having a back end with a REST API hook which we can send messages to and it would write them to logs. We would then be able to access those logs in a dashboard or some form of GUI so we do not have to open the actual file. Is there already a service like this?
The text was updated successfully, but these errors were encountered: