Merge pull request #5940 from influxdata/docs/v3/processing-engine

Clarifying usage of the Python Processing Engine across instances

Author: MeelahMe

content/shared/v3-core-plugins/_index.md

@@ -36,6 +36,28 @@ influxdb3 serve \
   --plugin-dir /path/to/plugins
 ```
 
+Replace `/path/to/plugins` with the directory where you want to store your Python plugin files. All plugin files must be located in this directory or its subdirectories.
+
+
+
+### Configure distributed environments
+
+If you're running multiple {{% product-name %}} instances (distributed deployment):
+
+1. Decide where plugins should run
+   - Data processing plugins, such as WAL plugins, run on ingester nodes
+   - HTTP-triggered plugins run on nodes handling API requests
+   - Scheduled plugins can run on any configured node
+2. Enable plugins on selected instances
+3. Maintain identical plugin files across all instances where plugins run
+   - Use shared storage or file synchronization tools to keep plugins consistent
+
+> [!Note]
+> #### Provide plugins to nodes that run them
+>
+> Configure your plugin directory on the same system as the nodes that run the triggers and plugins.
+
+
 ## Add a Processing engine plugin
 
 A plugin is a Python file that contains a specific function signature that corresponds to a trigger type.
@@ -630,3 +652,13 @@ docker exec -it CONTAINER_NAME influxdb3 install package pandas
 ```
 
 This creates a Python virtual environment in your plugins directory with the specified packages installed.
+
+{{% show-in "enterprise" %}}
+### Connect Grafana to your InfluxDB instance
+
+When configuring Grafana to connect to an InfluxDB 3 Enterprise instance:
+
+- **URL**: Use a querier URL or any node that serves queries
+
+Example URL format: `https://querier.your-influxdb.com:8086`
+{{% /show-in %}}