Phabricator Collect Slice


Phabricator is a set of tools for developing software. It includes applications for code review, repository hosting, bug tracking, project management, and more.

The Phabricator slice collects data from a Phabricator account and enables data flow into a data warehouse, such as Redshift.

Steps to add this slice to your installation

The steps to launch your slice are:

  1. Generate Phabricator API keys
  2. Specify the slice config
  3. Add the Phabricator slice

1. Generate Phabricator API keys

Setup requirements

Before getting started please make sure to have the following information:

  • Access to an active Phabricator account

Setup instructions

  1. Generate a new API token Use the Conduit API Tokens panel in Settings to generate or manage API tokens.

2. Specify the slice config

To get a template for the Phabricator slice configuration save the output of the describe --input-parameters command as follows:

datacoral collect describe --slice-type phabricator \
--input-parameters > phabricator_parameters_file.json

Necessary input parameters:

  • api_token - your Phabricator API token

Optional input parameters:

  1. collect all supported loadunits
"api_token": "YOUR_API_TOKEN",

Modify the phabricator_parameters_file.json file to add the api_token from Phabricator

3. Add the Slice

datacoral collect add --slice-type phabricator --slice-name <slice-name> --parameters-file <params-file>
  • slice-name Name of your slice. A schema with your slice-name is automatically created in your warehouse
  • params-file File path to your input parameters file. Ex. phabricator_parameters_file.json

Supported load units

  • revisions
  • users


By default, the slice runs daily. If desired, you can change the slice configuration and specify different schedules for the revisions and revisions loadunits.

Slice output

Output of this slice is stored in S3 and Redshift.

AWS S3 Data stored in AWS S3 is partitioned by date and time in the following bucket s3://datacoral-data-bucket/<sliceName>

AWS Redshift: Schema - schema name will be same as a slice-name. Tables produced by the slice are:

- schema.revisions
- schema.users

Questions? Interested?

If you have questions or feedback, feel free to reach out at or Request a demo