Our documentation has moved!

Our documentation now lives on the Atlassian Support site at https://support.atlassian.com/analytics/resources/.

What is a data source?

Realize the full experience of Atlassian’s analytics offering 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’s analytics offering to create charts and dashboards.

We offer a special Atlassian data source that gives you access to your organization’s product data. Learn more about how you can connect to the Atlassian data lake

Third-party data sources

You must have an Enterprise-edition Atlassian product in order to connect to third-party data sources.

Atlassian’s analytics offering makes it easy to connect to your third-party data sources. It only requires you to allow Atlassian’s IP addresses and provide your connection details.

Atlassian’s analytics offering cannot connect directly to databases on local machines.

Maximum number of connections

You can create up to 10 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’s analytics offering:

  • If possible, limit the access of the database user you provide in the data source connection form. Grant it access to only the essential tables that you need to include in Atlassian’s analytics offering.

  • Do an initial import of the schema into Atlassian’s analytics offering. Afterward, remove unnecessary tables from the schema in Atlassian’s analytics offering. You can then sync the schema and select the tables you'd like to add.

Read-only connections

By default, Atlassian’s analytics offering 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’s analytics offering blocks queries containing malicious keywords. For more protection, we also recommend creating a specific read-only database user for Atlassian’s analytics offering.

SSL encryption

Atlassian’s analytics offering provides SSL encryption for database connections but does not validate SSL certificates at this time.