Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This feature is EXPERIMENTAL. Learn what this means…

When this feature matures, its documentation will move into Products.

App Logs allow users with the admin.app-repository.* role to see the standard out logs of an app which was deployed via the Hosted SDK option.

Apps that are self-hosted or not deployed via Unique will not show any logs at this time.

The App Logs setup is neither simple nor rocket science but was chosen with a bit of scalability in mind. This is why logs get written to a Storage Account via a Diagnostic setting. Instead of putting the logs into the clients database, producing unnecessary load to the database, the development debug logs (App Logs) are put into a Storage Account and get read back from there to display them in the App Repository.

Get started

Pre-requisites

In order to leverage the logs, these bullets have to be fulfilled:

  • Valid contract holder of Hosted SDK

  • Acknowledged https://unique-ch.atlassian.net/wiki/x/moB5I

  • Push permissions on a Unique owned/controlled and deployed GitHub Repository

  • admin.app-repository.* on the Unique instances where the logs should be seen

  • Noted down environment names (provided inside the GitHub Repository) and the module names

Security

Storage Account

Retention

Log scrubbing

https://unique-ch.atlassian.net/wiki/x/moB5I


  • No labels