Hi, @mstrelex, thanks for reaching out!
Technically speaking you can use external service to access the app logs following this approach, however to allow this call to work, you must disclose these external domains by adding them as new entries in the permissions.external.fetch.backend section of the manifest.yml file of your app. Customers installing the app will need to consent to the data egress and this can be an adoption blocker for some customers as data egress is outside of their risk appetite. Based on recent feedback, we are seeing that data egress is becoming more and more important for our mutual customers, this is why we made the decision to put the control of the log access in the hands of the customer.
With the first release of Forge app monitoring you will be able to see the count of errors along with the types of errors. Initially we will categorise the errors in the following categories:
Out of memory ,
Unhandled exception . We will be open for feedback on this categorisation to see if there is an opportunity to improve it. As advised during the webinar, with the initial release (currently scheduled for next month), developers will have a view of the overall health of the app, drilling down to individual installations is planned for the subsequent release which will be coming later the same quarter.
BTW, I am curious to hear if you encountered any roadblocks when asking customers to enable log sharing?