Cloud
Data Center 5.0
Versions
- 9.4
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- See all
Diagnostics for third-party apps
Administering Bitbucket Server
- Users and groups
- External user directories
- Global permissions
- Setting up your mail server
- Integrating Bitbucket Server with Atlassian applications
- Connecting Bitbucket Server to an external database
- Migrating Bitbucket Server to another server
- Specifying the base URL for Bitbucket Server
- Configuring the application navigator
- Managing add-ons
- Audit logging in Bitbucket Server
- Running Bitbucket Server as a Windows service
- Updating your Bitbucket Server license details
- Bitbucket Server config properties
- Moving Bitbucket Server to a different context path
- Data recovery and backups
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- Smart Mirroring
- Git Large File Storage
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Lockout recovery process
- Proxying and securing Bitbucket Server
- High availability for Bitbucket Server
- Enabling JMX counters for performance monitoring
- Bitbucket Server debug logging
- Scaling Bitbucket Server
- Getting started with Bitbucket Server and AWS
- Add shortcut links to a Bitbucket Server repository
- Data Center Migration
- Git Virtual File System (GVFS)
- Diagnostics for third-party apps
- Administer code search
On this page
In this section
Related content
- No related content found
Overview
The diagnostics tool displays a summary of the alerts that have been raised on the instance in the past 30 days, grouped by issue and app combination.
There are three levels of severity:
- Error: a serious problem has occurred that impacts system stability and/or availability
- Warning: an issue has been detected that impacts performance or can lead to more serious problems in the future
- Info: something worth noting has happened.
The alerts can be filtered by severity, component, app, node and time.
Alert Details
The alert details page is accessed by clicking into an alert, and displays individual alerts for the selected issue and app combination.
When many alerts are raised in a short time window, just one representative alert is displayed per 1 minute window.
Clicking Show displays information relating to the issue, that was collected when the alert was raised.
You can also set up alerts using JMX metric details.
Last modified on Jan 16, 2019
In this section
Related content
- No related content found
Powered by Confluence and Scroll Viewport.