Find data about indexing for troubleshooting

Awesome Graphs entries about indexing are recorded in the awesome-graphs.log file located in <Bitbucket home directory>/log.

Information about data indexed by Awesome Graphs is available in Bitbucket Administration> Troubleshooting and support tools> System Information and in a support zip. This information is helpful when troubleshooting an app related issue and includes the following statistics.

In Bitbucket UI and Support Zip

Awesome Graphs adds the following data in Bitbucket Administration> Troubleshooting and support tools> System Information and in a support zip:

Each status in the indexing queue has two figures X/Y:

Only in Support Zip

Awesome Graphs adds the following data about each repository in a support zip: 

Performance monitoring with the help of JMX

JMX (Java Management eXtensions) can be used to expose Awesome Graphs data from Bitbucket to monitor how indexing goes. Details about the statistics that you can capture are below.

Statistics about Awesome Graphs indexing queue (com.stiltsoft.bitbucket.graphs:name=Tickets)

Tickets mean tasks of indexing repositories and refs by our app.

NameDescription
RepositoryTickets




Tickets for indexing of a whole repository in the indexing queue
#invalidNumber of failed tickets because of corrupted Git repositories
#failedNumber of failed tickets because of problems while indexing repositories
#in_progressNumber of in progress tickets
#pendingNumber of pending tickets
#reindexingNumber of reindexing tickets
#timeout

Number of failed tickets because of a timeout during indexing a repository

RefChangeTickets




Tickets for indexing of changes happened after 'git push'
#invalidNumber of failed tickets because of corrupted Git repositories
#failedNumber of failed tickets because of problems while indexing repositories
#in_progressNumber of in progress tickets
#pendingNumber of pending tickets
#reindexingNumber of reindexing tickets
#timeoutNumber of failed tickets because of a timeout during indexing a repository
Total Total number of tickets in the indexing queue
RepositoryTicketsTotalNumber of tickets for indexing of a whole repository in the indexing queue
RefChangeTicketsTotalNumber of tickets for indexing of changes happened after 'git push'

You can learn more about JMX and benefits of its usage from Enabling JMX counters for performance monitoring.

Alerts to admins about repository indexing problems

If a repository could not be indexed, admins will get a notification via Bitbucket alerts. It helps to quickly detect and solve problems.