Learn how to connect and manage your connected Atlassian data and external data.
Learn how to create insightful charts and dashboards with your organization’s data.
Learn how to use Visual SQL to create queries and transform data for making charts.
Need feedback on data? Learn how to share charts and dashboards with teammates so they can leave comments.
Learn how to grant resource access to the people who need it.
Learn how to manage your workspace and how to monitor your workspace activity.
Atlassian Analytics is in an early access program
Only people who are part of this invite-only early access program have access to Atlassian Analytics.
Realize the full experience of Atlassian Analytics by connecting some of your data to it. A data source is a supported database or application housing the data you’d like to access. Connecting to a data source lets you query its data in Atlassian Analytics to create charts and dashboards.
We offer a special Atlassian data source that gives you access to your organization’s product data. Learn how to connect to the Atlassian Data Lake.
Third-party data sources
Atlassian Analytics also lets you connect to your third-party data sources. For greater insights, you can blend your Atlassian data and your third-party data together into a single chart.
The supported data sources include:
Microsoft SQL Server
Note that Atlassian Analytics cannot connect directly to databases on local machines.
Maximum number of connections
You can create up to ten connections to the Atlassian Data Lake and an unlimited number of connections to third-party data sources.
Maximum tables and columns per schema
There’s a maximum limit of 5,000 tables and 50,000 columns per schema in a data source. If you hit these limits, you could do either of the following to bring the necessary tables into Atlassian Analytics:
If possible, limit the access of the database user you provide in the data source connection details. Grant it access to only the essential tables that you need to include in Atlassian Analytics.
Do an initial import of the schema into Atlassian Analytics. Afterward, remove unnecessary tables from the schema in Atlassian Analytics. You can then sync the schema and select the tables you'd like to add.
By default, Atlassian Analytics sets data sources to read-only at the connection level. This provides an added layer of security against malicious queries.
Some databases, such as Redshift, disallow some functions when connections are set to read-only. For example, you won’t be able to create variables and temporary tables. For this reason, we allow Redshift users to disable the enforcement of read-only in their data source settings if needed.
If you see an error message like Error: Transaction is read-only, disabling the read-only setting should resolve this issue.
Even with read-only disabled, your database is still protected from malicious queries. Atlassian Analytics blocks queries containing malicious keywords. For more protection, we also recommend creating a specific read-only database user for Atlassian Analytics.
Atlassian Analytics encrypts database connections with TLS but does not provide hostname validation. This may allow man-in-the-middle attacks to happen undetected.
Man-in-the-middle attacks allow unauthorized third parties to eavesdrop or potentially modify the data being transmitted. Without TLS hostname or certificate verification on a connection, Atlassian Analytics is unable to confirm the certificate being used for encryption is actually coming from the intended source.
We do not recommend establishing connections to sensitive data. Additionally, we recommend understanding the risks before connecting PostgreSQL or MySQL databases.
Was this helpful?