Atlassian collector

[ 1 Overview ] [ 2 Devo collector features ] [ 3 Data sources ] [ 4 Vendor setup ] [ 5 Minimum configuration required for basic pulling ] [ 6 Accepted authentication methods ] [ 7 Run the collector ] [ 8 Change log ]

Overview

The Atlassian collector queries the Atlassian cloud and returns audit data from Confluence and Jira.

Devo collector features

Feature	Details

Feature	Details
Allow parallel downloading (`multipod`)	`not allowed`
Running environments	`collector server` `on-premise`
Populated Devo events	`table`

Data sources

Data source	Description	Collector service name	Related remote endpoint	Devo table

Data source	Description	Collector service name	Related remote endpoint	Devo table
Jira	Pulls audit logs from the Jira API	`audit`	https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-audit-records/#api-group-audit-records	`app.atlassian.jira.audit`
Confluence	Pulls audit logs from the Confluence API	`audit`	https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-audit/#api-group-audit	`app.atlassian.confluence.audit`

For more information on how the events are parsed, visit our page.

Vendor setup

The Atlassian collector works over the Atlassian API. We need to enable API access and ensure its permissions in your Atlassian account to allow the collector to get the data correctly.

Log in to https://id.atlassian.com/manage-profile/secuirty/api-tokens
Create the required API token.
From the dialog that appears, enter a label for your token and click Create.
Click Copy to clipboard then paste the token to the config.yaml.

Minimum configuration required for basic pulling

Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.

This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details.

Setting	Details

Setting	Details
`username`	-
`api-key`	-
`verify-ssl`	`true` or `false`
`url`	https://domain.atlassian.net

See the Accepted authentication methods section to verify what settings are required based on the desired authentication method.

Accepted authentication methods

Depending on how you obtained your credentials, you will have to either fill or delete the following properties on the JSON credentials configuration block.

Run the collector

Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).

Change log

Release	Released on	Release type	Details	Recommendations

Release	Released on	Release type	Details	Recommendations
`v1.0.1`	Oct 4, 2023	BUG FIX	Updated dependencies in the `requirments.txt` file.	`Recommended version`
`v1.0.0`	Sep 29, 2023	INITIAL RELEASE	Initial Release with Collector SDK 1.9.2	`-`