# InfluxDB {% hint style="info" %} **Supported event types:** `logs` `metrics` {% endhint %} The *InfluxDB* output plugin lets you flush your records into a [InfluxDB](https://www.influxdata.com/products/influxdb-overview) time series database. The following instructions assume that you have an operational InfluxDB service running in your system. ## Configuration parameters | Key | Description | Default | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ----------- | | `add_integer_suffix` | Use integer type of [InfluxDB's line protocol](https://docs.influxdata.com/influxdb/v1/write_protocols/line_protocol_reference/). | `false` | | `auto_tags` | Automatically tag keys where value is `string`. | `false` | | `bucket` | InfluxDB bucket name where records will be inserted. If specified, `database` is ignored and v2 of the API is used. | *none* | | `database` | InfluxDB database name where records will be inserted. | `fluentbit` | | `host` | IP address or hostname of the target InfluxDB service. | `127.0.0.1` | | `http_header` | Add a HTTP header key/value pair. Multiple headers can be set. | *none* | | `http_passwd` | Password for user defined in `http_user`. | *none* | | `http_token` | Authentication token used with InfluxDB v2. If specified, both `http_user` and `http_passwd` are ignored. | *none* | | `http_user` | Optional username for HTTP Basic Authentication. | *none* | | `org` | InfluxDB organization name where the bucket is (v2 only). | `fluent` | | `port` | TCP port of the target InfluxDB service. | `8086` | | `sequence_tag` | The name of the tag whose value is incremented for consecutive simultaneous events. | *none* | | `tag_keys` | Space-separated list of keys to tag. | *none* | | `uri` | Custom URI endpoint. | *none* | | `workers` | The number of [workers](/manual/administration/multithreading.md#outputs) to perform flush operations for this output. | `0` | ### TLS / SSL The InfluxDB output plugin supports TLS/SSL. For more details about the properties available and general configuration, see [TLS/SSL](/manual/administration/transport-security.md). ## Get started To start inserting records into an InfluxDB service, you can run the plugin from the command line or through the configuration file. ### Command line The InfluxDB plugin can read the parameters from the command line through the `-p` argument (property) or by setting them directly through the service URI. The URI format is the following: ``` influxdb://host:port ``` Using the format specified, you could start Fluent Bit: ```shell fluent-bit -i cpu -t cpu -o influxdb://127.0.0.1:8086 -m '*' ``` ### Configuration file In your main configuration file append the following: {% tabs %} {% tab title="fluent-bit.yaml" %} ```yaml pipeline: inputs: - name: cpu tag: cpu outputs: - name: influxdb match: '*' host: 127.0.0.1 port: 8086 database: fluentbit sequence_tag: _seq ``` {% endtab %} {% tab title="fluent-bit.conf" %} ``` [INPUT] Name cpu Tag cpu [OUTPUT] Name influxdb Match * Host 127.0.0.1 Port 8086 Database fluentbit Sequence_Tag _seq ``` {% endtab %} {% endtabs %} #### Tagging Basic example of `Tag_Keys` usage: {% tabs %} {% tab title="fluent-bit.yaml" %} ```yaml pipeline: inputs: - name: tail tag: apache.access parser: apache2 path: /var/log/apache2/access.log outputs: - name: influxdb match: '*' host: 127.0.0.1 port: 8086 database: fluentbit sequence_tag: _seq # make tags from method and path fields tag_keys: method path ``` {% endtab %} {% tab title="fluent-bit.conf" %} ``` [INPUT] Name tail Tag apache.access Parser apache2 Path /var/log/apache2/access.log [OUTPUT] Name influxdb Match * Host 127.0.0.1 Port 8086 Database fluentbit Sequence_Tag _seq # make tags from method and path fields Tag_Keys method path ``` {% endtab %} {% endtabs %} `Auto_Tags=On` in this example causes an error, because every parsed field value type is `string`. The best usage of this option in metrics like record where one or more field value isn't `string` typed. ### Testing Before starting Fluent Bit, ensure the target database exists on InfluxDB. Using the previous example, insert the data into a `fluentbit` database. 1. Log into the InfluxDB console: ```shell influx ``` Which should return a result like: ``` Visit https://enterprise.influxdata.com to register for updates, InfluxDB server management, and monitoring. Connected to http://localhost:8086 version 1.1.0 InfluxDB shell version: 1.1.0 > ``` 2. Create the database: ``` > create database fluentbit > ``` 3. Check that the database exists: ``` > show databases name: databases name ---- _internal fluentbit > ``` 4. Run Fluent Bit: The following command will gather CPU metrics from the system and send the data to InfluxDB database every five seconds: ```shell fluent-bit -i cpu -t cpu -o influxdb -m '*' ``` All records coming from the `cpu` input plugin have a tag `cpu`. This tag is used to generate the measurement in InfluxDB. 5. Query the data: From InfluxDB console, choose your database: ``` > use fluentbit Using database fluentbit ``` 6. Query some specific fields: ``` > SELECT cpu_p, system_p, user_p FROM cpu name: cpu time cpu_p system_p user_p ---- ----- -------- ------ 1481132860000000000 2.75 0.5 2.25 1481132861000000000 2 0.5 1.5 1481132862000000000 4.75 1.5 3.25 1481132863000000000 6.75 1.25 5.5 1481132864000000000 11.25 3.75 7.5 ``` The CPU input plugin gathers more metrics per CPU core. This example selected three specific metrics. The following query will give a full result: ``` > SELECT * FROM cpu ``` 7. View tags by querying tagged keys: ``` > SHOW TAG KEYS ON fluentbit FROM "apache.access" name: apache.access tagKey ------ _seq method path ``` 8. Query `method` key values: ``` > SHOW TAG VALUES ON fluentbit FROM "apache.access" WITH KEY = "method" name: apache.access key value --- ----- method "MATCH" method "POST" ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fluentbit.io/manual/data-pipeline/outputs/influxdb.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.