Skip to main content

Create a sink connector from Apache Kafka® to InfluxDB®

The InfluxDB® sink connector enables you to move data from an Aiven for Apache Kafka® cluster to an InfluxDB instance for further processing and analysis.

note

See the full set of available parameters and configuration options in the connector's documentation.

Prerequisites​

To setup a InfluxDB sink connector, you need an Aiven for Apache Kafka service with Kafka Connect enabled or a dedicated Aiven for Apache Kafka Connect cluster.

Also collect the following information about the target InfluxDB database upfront:

  • INFLUXDB_USERNAME: The database username to connect

  • INFLUXDB_PASSWORD: The password for the username selected

  • INFLUXDB_HOST: the InfluxDB hostname

  • INFLUXDB_PORT: the InfluxDB port

  • INFLUXDB_DATABASE_NAME: The name of the InfluxDB database

  • TOPIC_LIST: The list of topics to sink divided by comma

  • KCQL_TRANSFORMATION: The KCQL syntax to parse the topic data, should be in the format

    INSERT
    INTO INFLUXDB_TABLe_NAME
    SELECT LIST_OF_FIELDS
    FROM APACHE_KAFKA_TOPIC

  • APACHE_KAFKA_HOST: The hostname of the Apache Kafka service, only needed when using Avro as data format

  • SCHEMA_REGISTRY_PORT: The Apache Kafka's schema registry port, only needed when using Avro as data format

  • SCHEMA_REGISTRY_USER: The Apache Kafka's schema registry username, only needed when using Avro as data format

  • SCHEMA_REGISTRY_PASSWORD: The Apache Kafka's schema registry user password, only needed when using Avro as data format

note

The Apache Kafka and InfluxDB details are available in the Aiven console service Overview tab or via the dedicated avn service get command with the Aiven CLI.

The SCHEMA_REGISTRY related parameters are available in the Aiven for Apache Kafka® service page, Overview tab, and Schema Registry subtab

As of version 3.0, Aiven for Apache Kafka no longer supports Confluent Schema Registry. For more information, read the article describing the replacement, Karapace

Setup a InfluxDB sink connector with Aiven Console​

The following example demonstrates how to setup a InfluxDB sink connector for Apache Kafka using the Aiven Console.

Define a Kafka Connect configuration file​

Define the connector configurations in a file (we'll refer to it with the name influxdb_sink.json) with the following content, creating a file is not strictly necessary but allows to have all the information in one place before copy/pasting them in the Aiven Console:

{
    "name":"CONNECTOR_NAME",
    "connector.class": "com.datamountaineer.streamreactor.connect.influx.InfluxSinkConnector",
    "topics": "TOPIC_LIST",
    "connect.influx.url": "https://INFLUXDB_HOST:INFLUXDB_PORT",
    "connect.influx.db": "INFLUXDB_DATABASE_NAME",
    "connect.influx.username": "INFLUXDB_USERNAME",
    "connect.influx.password": "INFLUXDB_PASSWORD",
    "connect.influx.kcql": "KCQL_TRANSFORMATION",
    "key.converter": "io.confluent.connect.avro.AvroConverter",
    "key.converter.schema.registry.url": "https://APACHE_KAFKA_HOST:SCHEMA_REGISTRY_PORT",
    "key.converter.basic.auth.credentials.source": "USER_INFO",
    "key.converter.schema.registry.basic.auth.user.info": "SCHEMA_REGISTRY_USER:SCHEMA_REGISTRY_PASSWORD",
    "value.converter": "io.confluent.connect.avro.AvroConverter",
    "value.converter.schema.registry.url": "https://APACHE_KAFKA_HOST:SCHEMA_REGISTRY_PORT",
    "value.converter.basic.auth.credentials.source": "USER_INFO",
    "value.converter.schema.registry.basic.auth.user.info": "SCHEMA_REGISTRY_USER:SCHEMA_REGISTRY_PASSWORD"
}

The configuration file contains the following entries:

  • name: the connector name, replace CONNECTOR_NAME with the name to give to the connector.
  • connect.influx.*: sink parameters collected in the prerequisite phase.
  • topics: the comma-separated list of topics to sink
  • key.converter and value.converter: defines the messages data format in the Apache Kafka topic. The io.confluent.connect.avro.AvroConverter converter translates messages from the Avro format. To retrieve the messages schema we use Aiven's Karapace schema registry as specified by the schema.registry.url parameter and related credentials.
note

The key.converter and value.converter sections define how the topic messages will be parsed and needs to be included in the connector configuration.

When using Avro as source data format, set following parameters:

  • value.converter.schema.registry.url: pointing to the Aiven for Apache Kafka schema registry URL in the form of https://APACHE_KAFKA_HOST:SCHEMA_REGISTRY_PORT with the APACHE_KAFKA_HOST and SCHEMA_REGISTRY_PORT parameters retrieved in the previous step.
  • value.converter.basic.auth.credentials.source: to the value USER_INFO, since you're going to login to the schema registry using username and password.
  • value.converter.schema.registry.basic.auth.user.info: passing the required schema registry credentials in the form of SCHEMA_REGISTRY_USER:SCHEMA_REGISTRY_PASSWORD with the SCHEMA_REGISTRY_USER and SCHEMA_REGISTRY_PASSWORD parameters retrieved in the previous step.

Create a Kafka Connect connector with the Aiven Console​

To create an Apache Kafka Connect connector:

  1. Log in to the Aiven Console and select the Aiven for Apache Kafka® or Aiven for Apache Kafka Connect® service where the connector needs to be defined.

  2. Select Connectors from the left sidebar.

  3. Select Create New Connector, it is enabled only for services with Kafka Connect enabled.

  4. Select Stream Reactor InfluxDB Sink.

  5. In the Common tab, locate the Connector configuration text box and select on Edit.

  6. Paste the connector configuration (stored in the influxdb_sink.json file) in the form.

  7. Select Apply.

    note

    The Aiven Console parses the configuration file and fills the relevant UI fields. You can review the UI fields across the various tab and change them if necessary. The changes will be reflected in JSON format in the Connector configuration text box.

  8. After all the settings are correctly configured, select Create connector.

  9. Verify the connector status under the Connectors screen.

  10. Verify the presence of the data in the target InfluxDB service, the table name is equal to the Apache Kafka topic name.

note

You can also create connectors using the Aiven CLI command.

Example: Create a InfluxDB sink connector​

If you have a topic named measurements containing the following data in AVRO format to move to InfluxDB:

{
    "ts":"2022-10-24T13:09:43.406000Z"
    "device_name": "mydevice1",
    "measurement": 17
}

You can sink the measurements topic to InfluxDB with the following connector configuration, after replacing the placeholders for INFLUXDB_HOST, INFLUXDB_PORT, INFLUXDB_DB_NAME, INFLUXDB_USERNAME, INFLUXDB_PASSWORD and schema registry:

{
    "name": "my-influxdb-sink",
    "connector.class": "com.datamountaineer.streamreactor.connect.influx.InfluxSinkConnector",
    "topics": "measurements",
    "connect.influx.url": "https://INFLUXDB_HOST:INFLUXDB_PORT",
    "connect.influx.db": "INFLUXDB_DATABASE_NAME",
    "connect.influx.username": "INFLUXDB_USERNAME",
    "connect.influx.password": "INFLUXDB_PASSWORD",
    "connect.influx.kcql": "insert into measurements select ts, device_name, measurement from measurements",
    "key.converter": "io.confluent.connect.avro.AvroConverter",
    "key.converter.schema.registry.url": "https://APACHE_KAFKA_HOST:SCHEMA_REGISTRY_PORT",
    "key.converter.basic.auth.credentials.source": "USER_INFO",
    "key.converter.schema.registry.basic.auth.user.info": "SCHEMA_REGISTRY_USER:SCHEMA_REGISTRY_PASSWORD"
    "value.converter": "io.confluent.connect.avro.AvroConverter",
    "value.converter.schema.registry.url": "https://APACHE_KAFKA_HOST:SCHEMA_REGISTRY_PORT",
    "value.converter.basic.auth.credentials.source": "USER_INFO",
    "value.converter.schema.registry.basic.auth.user.info": "SCHEMA_REGISTRY_USER:SCHEMA_REGISTRY_PASSWORD"
}

The configuration file contains the following peculiarities:

  • "topics": "measurements": setting the topic to sink
  • "connect.influx.kcql": "select into measurements select ts, device_name, measurement from measurements": the connector logic is to insert every topic message as new document into a table called measurements.

Once the connector is created successfully, you should see a table named measurements in the InfluxDB database referenced by the INFLUXDB_DB_NAME placeholder with the record in it.