Atlassian Bitbucket Integrations

Introduction   

 The Bitbucket integration collects audit logs from the audit log files or the audit API .   

 Reference:  https://developer.atlassian.com/server/bitbucket/reference/rest-api/   

 

 

 

 

 Assumptions   

 The procedures described in Section 3 assume that a Log Collector has already been set up .    

 

 

 

 

 Requirements   

 For more information on auditing in Bitbucket and how it can be configured, see View and configure the audit log on Atlassian's website.   

 Reference: https://confluence.atlassian.com/bitbucketserver/view-and-configure-the-audit-log-776640417.html   

   

 Logs   

 Audit   

 The Confluence integration collects audit logs from the audit log files or the audit API from self-hosted Confluence Data Center. It has been tested with Confluence 7.14 .2 but is expected to work with newer versions. As of version 1.2.0, this integration added experimental support for Atlassian Confluence Cloud. JIRA Cloud only supports Basic Auth using username and a Personal Access Token.   

 

 

 

 

 Atlassian Bitbucket I ntegration Procedures   

 

 

 

 

 Please provide the following information to CyTech :   

 Collect Bitbucket audit logs via log  files   

 

 

 

 

 Path   

 

 

 

 

 

 

 Preserve O riginal E vent ? (Enable Yes/No)   

 

 

 

 

 

 

 Preserves a raw copy of the original event, added to the field event.original   

 

 

 

 

 

 

 Tags   

 

 

 

 

 

 

 Processors (Optional)   

 

 

 

 

 

 

 Processors are used to reduce the number of fields in the exported event or to enhance the event with metadata. This executes in the agent before the logs are parsed.   

 

 

 

 

 

 

 Indexing settings (experimental ) (Enable Yes/No)   

 

 

 

 

 

 

 Select data streams to configure indexing options. This is an experimental feature and may have effects on other properties.   

 

 

 

 

 

 Collect Bitbucket audit logs via API (Enable Yes/No)   

 

 

 

 

 

 API URL - The API URL without the path.   

 

 

 

 

 

 

 Bitbucket Username - JIRA Username. Needs to be used with a Password. Do not fill if you are using a personal access token.   

 

 

 

 

 

 

 

 

 Bitbucket Password - JIRA Password. Needs to be used with a Username. Do not fill if you are using a personal access token.   

 

 

 

 

 

 

 Personal Access Token - The Personal Access Token. If set, Username and Password will be ignored.   

 

 

 

 

 

 

 Initial Interval - Initial interval for the first API call. Defaults to 24 hours.