InfluxDB
Since Camel 2.18
Only producer is supported
This component allows you to interact with InfluxDB https://influxdata.com/time-series-platform/influxdb/ a time series database. The native body type for this component is Point (the native influxdb class), but it can also accept Map<String, Object> as message body and it will get converted to Point.class, please note that the map must contain an element with InfluxDbConstants.MEASUREMENT_NAME as key.
Aditionally of course you may register your own Converters to your data type to Point, or use the (un)marshalling tools provided by camel.
Influxdb component requires at least Java 8.
Maven users will need to add the following dependency to their pom.xml
for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-influxdb</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
URI Options
The producer allows sending messages to a influxdb configured in the registry, using the native java driver.
The InfluxDB component supports 3 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
influxDB (producer) |
Autowired The shared Influx DB to use for all endpoints |
InfluxDB |
|
lazyStartProducer (producer) |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
autowiredEnabled (advanced) |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
boolean |
The InfluxDB endpoint is configured using URI syntax:
influxdb:connectionBean
with the following path and query parameters:
Path Parameters (1 parameters):
Name | Description | Default | Type |
---|---|---|---|
connectionBean |
Required Connection to the influx database, of class InfluxDB.class |
String |
Query Parameters (8 parameters):
Name | Description | Default | Type |
---|---|---|---|
autoCreateDatabase (producer) |
Define if we want to auto create the database if it’s not present |
false |
boolean |
batch (producer) |
Define if this operation is a batch operation or not |
false |
boolean |
checkDatabaseExistence (producer) |
Define if we want to check the database existence while starting the endpoint |
false |
boolean |
databaseName (producer) |
The name of the database where the time series will be stored |
String |
|
lazyStartProducer (producer) |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
operation (producer) |
Define if this operation is an insert or a query |
insert |
String |
query (producer) |
Define the query in case of operation query |
String |
|
retentionPolicy (producer) |
The string that defines the retention policy to the data created by the endpoint |
default |
String |
Example
Below is an example route that stores a point into the db (taking the db name from the URI) specific key:
from("direct:start")
.setHeader(InfluxDbConstants.DBNAME_HEADER, constant("myTimeSeriesDB"))
.to("influxdb://connectionBean);
from("direct:start")
.to("influxdb://connectionBean?databaseName=myTimeSeriesDB");
For more information, see these resources…
Spring Boot Auto-Configuration
When using influxdb with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-influxdb-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 4 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
|
Whether to enable auto configuration of the influxdb component. This is enabled by default. |
Boolean |
||
The shared Influx DB to use for all endpoints. The option is a org.influxdb.InfluxDB type. |
InfluxDB |
||
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |