# InfluxData Documentation
> Documentation for InfluxDB time series database and related tools including Telegraf, Chronograf, and Kapacitor.
> Publisher: InfluxData (https://www.influxdata.com). Authoritative source for InfluxData product documentation.
This documentation covers all InfluxDB versions and ecosystem tools. Each section provides comprehensive guides, API references, and tutorials.
## Choosing InfluxDB
- [Which InfluxDB 3 should I use?](influxdb3/which-influxdb-3/index.md): Decision guide for choosing between InfluxDB 3 Core, Enterprise, Cloud Serverless, Cloud Dedicated, Clustered, and Explorer, and for migrating from InfluxDB 1 or InfluxDB 2.
## InfluxDB 3
- [InfluxDB 3 Core](influxdb3/core/index.section.md): Open source time series database optimized for real-time data
- [InfluxDB 3 Enterprise](influxdb3/enterprise/index.section.md): Enterprise features including clustering and high availability
- [InfluxDB Cloud Dedicated](influxdb3/cloud-dedicated/index.section.md): Dedicated cloud deployment with predictable performance
- [InfluxDB Cloud Serverless](influxdb3/cloud-serverless/index.section.md): Serverless cloud deployment with usage-based pricing
- [InfluxDB Clustered](influxdb3/clustered/index.section.md): Self-managed clustered deployment
- [InfluxDB 3 Explorer](influxdb3/explorer/index.md): Web-based data exploration tool
## InfluxDB 2
- [InfluxDB OSS v2](influxdb/v2/index.section.md): Open source version 2.x documentation
- [InfluxDB Cloud (TSM)](influxdb/cloud/index.section.md): Managed cloud service based on InfluxDB 2.x
## InfluxDB 1
- [InfluxDB OSS v1](influxdb/v1/index.section.md): Open source version 1.x documentation
- [InfluxDB Enterprise v1](enterprise_influxdb/v1/index.section.md): Enterprise features for version 1.x
## Tools and Integrations
- [Telegraf](telegraf/v1/index.section.md): Plugin-driven server agent for collecting and sending metrics
- [Chronograf](chronograf/v1/index.section.md): User interface and administrative component
- [Kapacitor](kapacitor/v1/index.section.md): Real-time streaming data processing engine
- [Flux](flux/v0/index.section.md): Functional data scripting language
## API References
For API documentation, see the API reference section within each product's documentation.
## Full corpora (flattened Markdown)
Per-product Markdown corpora. Fetch a single file for the full documentation of one product.
- [InfluxDB 3 Core full corpus](influxdb3/core/llms-full.txt)
- [InfluxDB 3 Enterprise full corpus](influxdb3/enterprise/llms-full.txt)
- [InfluxDB 3 Cloud full corpus](influxdb3/cloud/llms-full.txt)
- [InfluxDB 3 Explorer full corpus](influxdb3/explorer/llms-full.txt)
- [InfluxDB Cloud Serverless full corpus](influxdb3/cloud-serverless/llms-full.txt)
- [InfluxDB Cloud Dedicated full corpus](influxdb3/cloud-dedicated/llms-full.txt)
- [InfluxDB Clustered full corpus](influxdb3/clustered/llms-full.txt)
- [InfluxDB OSS v2 full corpus](influxdb/v2/llms-full.txt)
- [InfluxDB OSS v1 full corpus](influxdb/v1/llms-full.txt)
- [InfluxDB Cloud (TSM) full corpus](influxdb/cloud/llms-full.txt)
- [Telegraf full corpus](telegraf/v1/llms-full.txt)
- [Telegraf Controller full corpus](telegraf/controller/llms-full.txt)
- [Telegraf Enterprise full corpus](telegraf/enterprise/llms-full.txt)
- [Chronograf full corpus](chronograf/v1/llms-full.txt)
- [Kapacitor full corpus](kapacitor/v1/llms-full.txt)
- [InfluxDB Enterprise v1 full corpus](enterprise_influxdb/v1/llms-full.txt)
- [Flux full corpus](flux/v0/llms-full.txt)
Measured from the saved file
Linked document
UTF-8 text size
3.5 KB3537 bytes
Token count
941o200k_base encoding
Markdown links
3232 distinct URLs
Fenced code blocks
063 lines in the file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Project H1
InfluxData Documentation
Opening blockquote
Documentation for InfluxDB time series database and related tools including Telegraf, Chronograf, and Kapacitor. Publisher: InfluxData (https://www.influxdata.com). Authoritative source for InfluxData product documentation.
Context architecture
How the content is divided
7 H2 sections organize 32 parsed Markdown links. 15 links point to .md or .markdown paths; 0 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
Choosing InfluxDBLine 9
1
249
71
InfluxDB 3Line 13
6
688
161
InfluxDB 2Line 22
2
194
58
InfluxDB 1Line 27
2
196
54
Tools and IntegrationsLine 32
4
360
83
API ReferencesLine 39
0
92
16
Full corpora (flattened Markdown)Line 43
17
1211
379
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Code, installation and API examples
Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
The Optional section
No H2 section named “Optional” was detected in this file.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP references and configuration text
No MCP or Model Context Protocol term was detected in the captured file. 0 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
These are text and link observations. No MCP server connection, authentication or tool call was tested.
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
What can be said about freshness
This capture establishes a baseline. Update frequency cannot be determined from one observation.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.