FAQ - Data Center

Installation

1. I have an instance of Bitbucket with a lot of heavily branched repositories. Can I install Awesome Graphs on it right away?

For large Bitbucket instances, it's highly recommended to try Awesome Graphs on a staging environment first. If it runs smoothly, install it on a production instance. If you run into issues, please contact us.

2. I want to install Awesome Graphs on my Bitbucket Server, but new Server apps are no longer available for purchase on Atlassian Marketplace. What should I do?

You can buy or generate a trial Data Center license on Atlassian Marketplace and install it on your Bitbucket Server as they are compatible.

Indexing

1. Where does Awesome Graphs store indexed data?

The indexed data is stored in the Bitbucket database. This data is then used for building graphs and reports.

2. Does Awesome Graphs use the throttling approach to indexing data?

Yes. Indexing repositories is a resource-intensive process. With adaptive throttling, Bitbucket examines the total physical memory on the machine and determines a maximum ticket number that the machine can safely support. This approach improves the system's performance during indexing.

3. Awesome Graphs is indexing data and completely loads one CPU core. Is it normal?

Yes. On large Bitbucket instances, Awesome Graphs can load one core completely. We recommend installing it on a server with at least a dual-core CPU for better performance.

4. It takes too long to index my repositories. What is the problem?

On large Bitbucket instances, Awesome Graphs may need some time to index all data. In this case, we recommend running our app on a staging environment first. Delays in indexing may also happen when a repository is corrupted and Awesome Graphs waits until the repository indexing timeout is over. For Bitbucket Server and Bitbucket Data Center, the timeout is 16 hours.

5. How will the size of my database grow after installing Awesome Graphs?

The amount of space Awesome Graphs tables and their indexes consume in the database depends on the number of commits in all repositories. See this page to estimate the growth of your database size.

6. I experience indexing issues. What should I do?

You can always reach out to our support team.

If you would like to approach resolving this issue faster, please try either of the following:

1) Use the REST API to restart tickets in the indexing queue.

2) Disable and enable the app to see if the issue persists.

Please note that this action will trigger the process of indexing relevancy checks with consequent re-indexing of repositories that need to be updated. On large Bitbucket instances, it can take some time. Consider performing this in the hours of the lowest user activity.

3) If total app restart is not a viable option, try restarting the indexing of repositories with FAILED and INVALID statuses by executing the following query to your database

PostgreSQL, Oracle, MS SQL:

UPDATE "AO_6292E3_GRAPHS_IDX_QUEUE"
SET "STATUS" = 0
WHERE "STATUS" IN (3,4);

MySQL:

UPDATE AO_6292E3_GRAPHS_IDX_QUEUE
SET STATUS = 0
WHERE STATUS IN (3,4);

Performance

1. We are experiencing Bitbucket performance issues after installing Awesome Graphs. Why?

Our app is tested to work on various Bitbucket instances and should not cause performance issues. Every year we successfully pass Atlassian Data Center certification on a large test profile. If you encounter performance issues, please contact our support team providing as much detail about your situation as possible.

REST API

1. How do I use your REST API?

If you have Awesome Graphs already installed:

Navigate to the People page
Click the Export button
In the dropdown menu select REST API - this action will take you to a page with detailed REST API usage instructions together with pre-made prompts

Alternatively:

Navigate to this page with detailed information on REST API capabilities and usage instructions.

2. My REST API prompt does not work. What should I do?

Please, make sure that your prompt is correct. To learn more about REST API follow the steps provided in the answer above.

If issues persist, please contact our support team.

Graphs and Reports

1. Are commits from forks included in your graphs?

Yes, but only unique commits are counted.

2. Are merge commits counted in the graphs?

No. Only regular commits are taken into account.

3. What time zone is used for displaying statistics?

Awesome Graphs uses user timezones set in the Bitbucket. If a user doesn't set their individual timezone in their account settings, their timezone is defined by the default time zone set for all users. You can learn more about Bitbucket timezones here.

4. Why do some people show up in my graphs and reports twice?

This happens when a certain user makes commits from different emails that are not associated with the same Bitbucket user. To solve this we recommend merging different user names and emails for one person using our Aliases feature.

5. Why there's no link to Contributions from the Contributors graph?

The Contributors graph displays a link to Contribution only if a contributor is a Bitbucket user and:

either their email is the same as in the Git settings,
or their Git username is the same as their Bitbucket display name.

You can learn how to merge different user names and emails for one person here.

6. How to view the Contributions of disabled users when using Crowd?

The Contributions page in the user profile is available only if a user exists in Bitbucket. When disabling Bitbucket users in Crowd by making them inactive, they disappear from the list of users.

As a workaround, you can leave a user active in Crowd and not disable that user, but delete that user's Bitbucket User permission by removing that user from the group that defines Bitbucket Users. Refer to Removing Users from a Group to learn how to do that. This user will be considered unlicensed and will not count towards your Bitbucket license limit.

7. Is it possible to calculate the number of added/deleted lines of code per repository/project using Awesome Graphs?

Yes. You can get this information using our REST API. Please follow the instructions here.

8. I can't access a graph/report. What should I do?