> For the complete documentation index, see [llms.txt](https://docs.monokot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monokot.io/tags-and-devices/influxdb-connectivity-connector.md).

# InfluxDB Connectivity (Connector)

To present fields of InfluxDB database as OPC UA items the server provides InfluxDB Connector. The device periodically sends requests to the database and maps the received query result to the associated tags (variables).

{% hint style="info" %}
Variables hereinafter are referred to tags specified in the server, and tags are referred to tags used in InfluxDB to store time series metadata
{% endhint %}

### Key Features <a href="#h.auy1ifvf0z1p" id="h.auy1ifvf0z1p"></a>

* Data fetch by using of Influx Query Language.
* Data writing by using of Influx Line Protocol.
* Data types: Boolean, Byte, Word, Int, DWord, DInt (32-bit signed integer), Float, Double, QWord, Long, String, DateTime.
* Block data reading.
* OPC UA Historical access (raw/aggregated data reading).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.monokot.io/tags-and-devices/influxdb-connectivity-connector.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.