[WIP] Document recommendation for Telegraf with InfluxDB 3 - use the v2 plugin and concurrent writes

[Copilot]

• Review existing Telegraf documentation structure in /content/shared/influxdb3-write-guides/use-telegraf/
• Create new section in configure.md documenting concurrent_writes recommendation
• Add recommendation to use influxdb_v2 output plugin with concurrent_writes configuration
• Document tuning guidelines: start with min(number of cores / 2, 10)
• Include note that concurrent_writes should be at least 2 in nearly all cases
• Add note about using v2 plugin instead of v1 plugin for v3
• Add concurrent_writes to main configuration example (conditionally for core/enterprise)
• Test the documentation build locally
• Verify rendered output on core and enterprise pages
• Verify it doesn't appear on cloud-dedicated or cloud-serverless
• Run code review and address any feedback
• Run CodeQL security check
• Take screenshots of rendered documentation
• Address PR review feedback - wrap concurrent_writes with show-in directive

Summary

Successfully documented the recommendation for using Telegraf with multiple concurrent writers for InfluxDB v3 Core and Enterprise. The documentation:

1. Added concurrent_writes parameter documentation with:

   • Recommendation to set it to at least 2 in nearly all situations
   • Tuning guidance: start with min(number of CPU cores / 2, 10)
   • Warning that concurrent writes don't guarantee metric ordering

2. Updated configuration examples to include concurrent_writes = 5 (conditionally displayed only for Core and Enterprise versions using {{% show-in "enterprise,core" %}})

3. Added note about plugin choice: Emphasizes using influxdb_v2 output plugin instead of v1 plugin for InfluxDB v3

4. Updated table of contents to include the new concurrent_writes section

All changes are in the shared content file /content/shared/influxdb3-write-guides/use-telegraf/configure.md, which is automatically included in both Core and Enterprise documentation pages.

Changes in latest commit

Fixed the conditional rendering by properly wrapping the entire concurrent_writes section with {{% show-in "enterprise,core" %}}...{{% /show-in %}} directive as requested in review feedback. This ensures the content only appears on Core and Enterprise documentation, not on Cloud Serverless or Cloud Dedicated.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Use multiple concurrent writers and the v2 influxdb output plugin with Telegraf</issue_title>
<issue_description> if you're using telegraf to write to monolith, you should be using multiple concurrent writers in nearly every situation. See the docs for the v2 influxdb output plugin: https://github.com/influxdata/telegraf/blob/release-1.36/plugins/outputs/influxdb_v2/README.md
concurrent_writes = 5 # should definitely be at least 2; for tuning, i'd start at min(number of cores for 3ent / 2, 10)
Note: the v1 output plugin for telegraf likely works with v3 but please use the v2 plugin instead.</issue_description>

<agent_instructions>Document the recommendation for using Telegraf with influxdb3/core and influxdb3/enterprise. This can go in /content/shared</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Use multiple concurrent writers and the v2 influxdb output plugin with Telegraf #6561

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

PR Preview Action v1.4.8
🚀 Deployed preview to https://influxdata.github.io/docs-v2/pr-preview/pr-6589/
on branch gh-pages at 2026-01-16 14:13 UTC

[github-actions]

PR Preview

Status	Details
Preview	View preview
Pages	2 page(s) deployed
Build time	68s
Last updated	2026-01-16 14:13:33 UTC

Pages included in this preview

• /influxdb3/enterprise/write-data/use-telegraf/configure/
• /influxdb3/core/write-data/use-telegraf/configure/

---

_{Preview auto-deploys on push. Will be cleaned up when PR closes.}

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[Copilot]

The TOC entry for concurrent_writes should be conditionally rendered to match the content visibility. Since the concurrent_writes section (lines 115-137) is wrapped in show-in "enterprise,core", this TOC entry should also be wrapped to avoid showing a link to non-existent content on other product pages. Consider wrapping this line with the same show-in directive.

Suggested change

	- [bucket](#bucket)
	- [concurrent_writes](#concurrent_writes)
	- [bucket](#bucket)
	{{% show-in "enterprise,core" %}}
	- [concurrent_writes](#concurrent_writes)
	{{% /show-in %}}

[Copilot]

The code example uses DATABASE_NAME as a placeholder but doesn't wrap it with the code-placeholders shortcode like the main example does (lines 54-63). For consistency, either wrap this code block with the code-placeholders shortcode or add a note indicating that DATABASE_NAME should be replaced with the actual database name. This ensures users understand which values need to be customized.