a609a3f900
* docs(influxdb3): document how to disable Processing Engine Add documentation for disabling the Processing Engine in Docker and systemd deployments. Key points: - Processing Engine is enabled by default in Docker images and DEB/RPM - Empty string does not disable — must unset or remove config - Enterprise: use INFLUXDB3_UNSET_VARS feature - Core Docker: requires custom entrypoint workaround - systemd: comment out or remove plugin-dir from TOML config closes influxdata/DAR#590 * docs(influxdb3): add cross-references for Processing Engine defaults Add notes and cross-references explaining that the Processing Engine is enabled by default in Docker and DEB/RPM installations: - plugins/_index.md: Add deployment behavior table and link to disable docs - get-started/processing-engine.md: Add note with cross-reference * docs(influxdb3): clarify Processing Engine vs process mode distinction Add notes explaining that --plugin-dir (Processing Engine activation) and --mode=process (cluster node specialization) are independent configurations. * docs(influxdb3): document --plugin-dir auto-enables process mode - Update clustering, get-started, plugins, and reference pages - Add example for enabling Processing Engine without --mode=process - Clarify --mode=process is only needed for dedicated process-only nodes - Synthesize notes into inline content for better flow in guides * Update content/shared/influxdb3-reference/influxdb3-processing-engine.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update content/shared/influxdb3-cli/config-options.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| glossary.md | ||
| influxdb3-processing-engine.md | ||
| naming-restrictions.md | ||
| telemetry.md | ||