Monitoring your application
Critical components and key metrics of our hosting and operation packages for your Atlassian applications are monitored around the clock by our central monitoring system. Depending on your applicable SLA, our system administrators are notified of critical incidents by SMS within service hours and immediately start working on them.
Systems that we operate as virtual appliances in your customer infrastructure as part of our operating package are also automatically monitored via a Site2Site VPN connection.
The following components and metrics of a hosting or operation package are monitored by our monitoring system:
Can the login page of your application (e.g. Confluence) be opened within 10 seconds?
|Simultaneous connections||Does the number of simultaneous connections reach critical limits?|
|SSL certificate expiry date||Is the SSL certificate used for secure transmission still valid for an adequate period of time?|
|Atlassian||Java heap memory||Is there still enough memory available for the application in the Java virtual machine?|
|Threads, open files||Are the number of open files and running threads (processes) reaching critical limits?|
|Data security||Local ZFS snapshots||Were file system snapshots taken at the scheduled intervals?|
|Mirroring to backup server||Was a data backup to one of the offsite backup servers performed within the previous 24 hours?|
|System||CPU utilization||Is the CPU utilization reaching critical limits?|
|Disk space||Is there still enough disk space available for your application?|
|Internet access||Can the server system access the public internet?|
|Server time||Are the services for setting the server time running correctly?|
|Email dispatch||Are the local email services on the server operational?|
In addition, metrics from the above categories which take up to 60 seconds to query are regularly checked and logged to save time when troubleshooting.
Below is a sample of the monitored data (this will vary depending on the system):