Tieing into Kevin Lee's wip/mqtt uploader, with event log access, the support team has been thinking about how helpful it would be to somehow see what is actually happening on an uploader rather than relying on what a user says or thinks is happening --
Had a nice conversation with Kevin..... here is what we talked about... concept:
If the uploader had a button to upload the last N lines (e.g., 250 lines) to the users own Mongo database to a new collection for "EventLogs" (or some other name), and there was a new mapping in the website API for the support technician to query /api/v1?action=viewUploadLogs
and the output simply dumped everything in the collection to the screen.
There is a chicken/egg for "first time users"... if they are having troubles getting setup, then will Azure be created? And to do this, the Support Team may need to alter instructions to have the user create Mongo, Azure, and then the Uploader to ensure Azure is connected as a prerequisite.
Tieing into Kevin Lee's wip/mqtt uploader, with event log access, the support team has been thinking about how helpful it would be to somehow see what is actually happening on an uploader rather than relying on what a user says or thinks is happening --
Had a nice conversation with Kevin..... here is what we talked about... concept: If the uploader had a button to upload the last N lines (e.g., 250 lines) to the users own Mongo database to a new collection for "EventLogs" (or some other name), and there was a new mapping in the website API for the support technician to query/api/v1?action=viewUploadLogs
and the output simply dumped everything in the collection to the screen.
There is a chicken/egg for "first time users"... if they are having troubles getting setup, then will Azure be created? And to do this, the Support Team may need to alter instructions to have the user create Mongo, Azure, and then the Uploader to ensure Azure is connected as a prerequisite.