Performance monitoring and error logging

This document outlines how we monitor for performance issues and log error data

• The performance of any bulk task depends on your network as well as the response of your Atlassian instance environment. If your instance handles high load, the iteration will be much faster for the bulk operation you are running given that you’re on a good network. If it’s not then it will reduce to your instance capability. This way, your operational task doesn’t cause excessive requests which ends up in a 429 error rate limit.

  • For example a typical bulk task of 4K rows for delete-account or change-email can be done within 30 mins just to give you a benchmark.

• We keep track of the frontend performance in relation to how each page render for users. We do not track users outside the context of the app and we tag each user as anonymous, we only get information relating to the pages visited and how much time it took for the page to render. This information helps us improve the frontend performance as much as possible based on trends from usage.

• We log error data from end-user activities (Note: we do not log end-user data itself but the actions or features within that app that was used). If any error occurs, we keep track of what those errors are, so we can mitigate them in the future. For the purpose of the scheduling feature we will store the data to re-use at a later time based on your request. Once that request is completed, we allow a leeway of 1hr for rollback then the data is purged from our systems.

• Our logs are kept for 7 days after which it is purged from our systems. We will still retain information about errors that might have triggered app failure while being used by users or errors as a result of server failure.