Jira Source Connector for Confluent Cloud

The fully-managed Jira Source connector for Confluent Cloud is used to move data from Jira to an Apache Kafka® topic. This connector polls data from Jira through Jira v2 APIs, converts data into Kafka records, and moves the records into the Kafka topic. Each row from a Jira table is converted into exactly one Kafka record.

Note

This is a Quick Start for the fully-managed cloud connector. If you are installing the connector locally for Confluent Platform, see Jira Source Connector for Confluent Platform.

Features

The Jira Source connector supports the following features:

  • At least once delivery: The connector guarantees that records are delivered at least once to the Kafka topic (if the file row parsed is valid).
  • Supports multiple tasks: The connector supports running one or more tasks. More tasks may improve performance. One Jira resource (table) is covered by one task only.

For more information and examples to use with the Confluent Cloud API for Connect, see the Confluent Cloud API for Managed and Custom Connectors section.

Limitations

Be sure to review the following information.

Jira Resources

The connector can fetch from the following resources:

Quick Start

Use this quick start to get up and running with the Confluent Cloud Jira Source connector. The quick start provides the basics of selecting the connector and configuring it to get data from one or more Jira resources.

Prerequisites

Using the Confluent Cloud Console

Step 1: Launch your Confluent Cloud cluster.

See the Quick Start for Confluent Cloud for installation instructions.

Step 2: Add a connector.

In the left navigation menu, click Connectors. If you already have connectors in your cluster, click + Add connector.

Step 3: Select your connector.

Click the Jira Source connector card.

Jira Source Connector Card

Step 4: Enter the connector details.

Note

  • Make sure you have all your prerequisites completed.
  • An asterisk ( * ) designates a required entry.

At the Add Jira Source Connector screen, complete the following:

  1. Select the way you want to provide Kafka Cluster credentials. You can choose one of the following options:
    • Global Access: Allows your connector to access everything you have access to. With global access, connector access will be linked to your account. This option is not recommended for production.
    • Granular access: Limits the access for your connector. You will be able to manage connector access through a service account. This option is recommended for production.
    • Use an existing API key: Allows you to enter an API key and secret part you have stored. You can enter an API key and secret (or generate these in the Cloud Console).
  2. Click Continue.

Step 5: Check for records.

Verify that records are being produced in the Kafka topic.

For more information and examples to use with the Confluent Cloud API for Connect, see the Confluent Cloud API for Managed and Custom Connectors section.

Using the Confluent CLI

To set up and run the connector using the Confluent CLI, complete the following steps.

Note

Make sure you have all your prerequisites completed.

Step 1: List the available connectors.

Enter the following command to list available connectors:

confluent connect plugin list

Step 2: List the connector configuration properties.

Enter the following command to show the connector configuration properties:

confluent connect plugin describe <connector-plugin-name>

The command output shows the required and optional configuration properties.

Step 3: Create the connector configuration file.

Create a JSON file that contains the connector configuration properties. The following example shows the required connector properties.

{
  "connector.class": "JiraSource",
  "name": "JiraSourceConnector_0",
  "kafka.auth.mode": "SERVICE_ACCOUNT",
  "kafka.service.account.id": "<service-account-resource-ID>",
  "jira.url": "https://<server-name>.atlassian.net",
  "jira.username": "<authorized-user>",
  "jira.api.token": "*********************************",
  "jira.since": "2020-06-14 09:30",
  "jira.resources": "issues, users, worklogs",
  "output.data.format": "JSON",
  "tasks.max": "1",
}

Note the following property definitions:

  • "connector.class": Identifies the connector plugin name.
  • "name": Sets a name for your new connector.
  • "kafka.auth.mode": Identifies the connector authentication mode you want to use. There are two options: SERVICE_ACCOUNT or KAFKA_API_KEY (the default). To use an API key and secret, specify the configuration properties kafka.api.key and kafka.api.secret, as shown in the example configuration (above). To use a service account, specify the Resource ID in the property kafka.service.account.id=<service-account-resource-ID>. To list the available service account resource IDs, use the following command:

    confluent iam service-account list
    

    For example:

    confluent iam service-account list
    
       Id     | Resource ID |       Name        |    Description
    +---------+-------------+-------------------+-------------------
       123456 | sa-l1r23m   | sa-1              | Service account 1
       789101 | sa-l4d56p   | sa-2              | Service account 2
    
  • Enter the GitHub connection details.

  • "jira.url": The Jira server URL. For example: https://<server-name>.atlassian.net.

  • "jira.api.token": API key for the Jira account.

  • "jira.since": Records created or updated after this time will be processed by the connector. The expected format for this property is yyyy-MM-dd HH:mm. Note that the value should be configured according to the timezone set in the Jira environment for the jira.username configured.

  • "jira.resources": One or more resources that the connector extracts and writes to Kafka. See Jira Resources for details.

  • output.data.format": Enter an output data format (data going to the Kafka topic): AVRO, JSON_SR (JSON Schema), PROTOBUF, or JSON (schemaless). Schema Registry must be enabled to use a Schema Registry-based format (for example, Avro, JSON_SR (JSON Schema), or Protobuf). For additional information, see Schema Registry Enabled Environments and Cloud connector limitations.

    Note

    For Schema Registry-based output formats, the connector attempts to deduce the schema based on the source API response returned. The connector registers a new schema for every NULL and NOT NULL value of an optional field in the API response. For this reason, the connector may register schema versions at a much higher rate than expected.

  • "tasks.max": The connector supports running one or more tasks. More tasks may improve performance.

See Configuration Properties for all property values and descriptions.

Step 4: Load the properties file and create the connector.

Enter the following command to load the configuration and start the connector:

confluent connect cluster create --config-file <file-name>.json

For example:

confluent connect cluster create --config-file jira-source-config.json

Example output:

Created connector JiraSourceConnector_0 lcc-do6vzd

Step 5: Check the connector status.

Enter the following command to check the connector status:

confluent connect cluster list

Example output:

ID           |             Name            | Status  | Type   | Trace
+------------+-----------------------------+---------+--------+-------+
lcc-do6vzd   | JiraSourceConnector_0       | RUNNING | source |       |

Step 6: Check the Kafka topic.

Verify that records are being produced at the Kafka topic.

For more information and examples to use with the Confluent Cloud API for Connect, see the Confluent Cloud API for Managed and Custom Connectors section.

Configuration Properties

Use the following configuration properties with the fully-managed connector. For self-managed connector property definitions and other details, see the connector docs in Self-managed connectors for Confluent Platform.

How should we connect to your data?

name

Sets a name for your connector.

  • Type: string
  • Valid Values: A string at most 64 characters long
  • Importance: high

Kafka Cluster credentials

kafka.auth.mode

Kafka Authentication mode. It can be one of KAFKA_API_KEY or SERVICE_ACCOUNT. It defaults to KAFKA_API_KEY mode.

  • Type: string
  • Default: KAFKA_API_KEY
  • Valid Values: KAFKA_API_KEY, SERVICE_ACCOUNT
  • Importance: high
kafka.api.key

Kafka API Key. Required when kafka.auth.mode==KAFKA_API_KEY.

  • Type: password
  • Importance: high
kafka.service.account.id

The Service Account that will be used to generate the API keys to communicate with Kafka Cluster.

  • Type: string
  • Importance: high
kafka.api.secret

Secret associated with Kafka API key. Required when kafka.auth.mode==KAFKA_API_KEY.

  • Type: password
  • Importance: high

Which topic name pattern do you want to send data to?

topic.name.pattern

The pattern to use for the topic name, where the ${resourceName} literal will be replaced with each resource name.

  • Type: string
  • Default: ${resourceName}
  • Importance: high

How should we connect to your Jira server?

jira.url

Jira server url, e.g. “https://server-name.atlassian.net”.

  • Type: string
  • Importance: high
jira.username

Username or email associated with the Jira account.

  • Type: string
  • Importance: high
jira.api.token

API key for this Jira account.

  • Type: password
  • Importance: high

Jira details

jira.since

Records created or updated after this time will be processed by the connector. The expected format for jira.since is yyyy-MM-dd HH:mm. Note that the value should be configured according to timezone set by the user(defined in Jira Username config) in Jira environment.

  • Type: string
  • Importance: medium
jira.resources

The resources that are to be extracted and written to Kafka.

  • Type: list
  • Importance: high

Connection details

max.batch.size

The maximum number of records that should be returned and written to Kafka at one time.

  • Type: int
  • Default: 100
  • Importance: low
max.in.flight.requests

The maximum number of requests that may be in-flight at once.

  • Type: int
  • Default: 10
  • Importance: low
max.poll.interval.ms

The time in milliseconds between requests to fetch changed or updated entities.

  • Type: long
  • Default: 3000 (3 seconds)
  • Importance: low
request.interval.ms

The time in milliseconds to wait before checking for updated records.

  • Type: long
  • Default: 15000 (15 seconds)
  • Importance: low
max.retries

The maximum number of times to retry on errors before failing the task.

  • Type: int
  • Default: 10
  • Importance: low
retry.backoff.ms

The time in milliseconds to wait following an error before a retry attempt is made.

  • Type: long
  • Default: 3000 (3 seconds)
  • Importance: low

Output messages

output.data.format

Sets the output Kafka record value format. Valid entries are AVRO, JSON_SR, PROTOBUF, or JSON. Note that you need to have Confluent Cloud Schema Registry configured if using a schema-based message format like AVRO, JSON_SR, and PROTOBUF

  • Type: string
  • Importance: high

Number of tasks for this connector

tasks.max

Maximum number of tasks for the connector.

  • Type: int
  • Valid Values: [1,…]
  • Importance: high

Next Steps

For an example that shows fully-managed Confluent Cloud connectors in action with Confluent Cloud ksqlDB, see the Cloud ETL Demo. This example also shows how to use Confluent CLI to manage your resources in Confluent Cloud.

../_images/topology.png