`data_sharing`¶

The data_sharing section controls what the gateway forwards to the LunarGate Dashboard on app.lunargate.ai.

By default, LunarGate is zero-leakage with respect to prompt and response content: request bodies do not leave your infrastructure unless you explicitly enable sharing.

This section is also hot-reloadable. Updating data-sharing config reconciles the in-process collector and remote-control client without restarting the gateway.

Fields¶

Field	Type	Default	Notes
`enabled`	bool	`false`	master switch for Dashboard forwarding
`share_prompts`	bool	`false`	forward prompt content
`share_responses`	bool	`false`	forward response content
`backend_url`	string	gateway default backend base URL	normalized to versioned backend base URL; `/collector` suffix is trimmed if provided
`api_key`	string	empty	gateway API key created in the `Gateways` section of app.lunargate.ai; LunarGate resolves the internal `gateway_id` from this key
`gateway_lat`	string	empty	optional latitude for live flow map
`gateway_lon`	string	empty	optional longitude for live flow map
`remote_control`	bool	`false`	enable remote-control websocket/sandbox flow

Metrics-only mode¶

data_sharing:
  enabled: false
  share_prompts: false
  share_responses: false

Debug / request-inspection mode¶

data_sharing:
  enabled: true
  share_prompts: true
  share_responses: true
  api_key: "${LUNARGATE_GATEWAY_API_KEY}"

Create that key in the Gateways section of app.lunargate.ai.

Flow map / geo tags¶

If you use the live flow map in the dashboard, you can also set:

data_sharing:
  gateway_lat: "52.2297"
  gateway_lon: "21.0122"

Remote control¶

If you want the gateway to participate in LunarGate remote control features, enable:

data_sharing:
  remote_control: true

remote_control is the gateway's outbound control-plane channel to the LunarGate Dashboard on app.lunargate.ai.

Today it is primarily used for the sandbox flow exposed by the LunarGate Dashboard on app.lunargate.ai.

The intended scope is wider than that: over time, the same control channel is expected to support automated A/B tests, controlled experiments, and other remote orchestration capabilities that act on a connected gateway without changing the client-facing API shape.

In other words:

enabled controls collector-style observability export
remote_control controls whether the gateway also joins the Dashboard control channel

When remote_control, backend_url, or api_key change, the gateway reconnects or reconfigures the in-process Dashboard clients with the new settings. If enabled, backend_url, or api_key are incomplete, collector export stays effectively off even if this section exists in YAML.

Streaming nuance¶

When share_responses: true, the gateway can accumulate streamed chunks so it can reconstruct a final response object for downstream request inspection.

Practical guidance¶

Keep prompt/response sharing off unless your team explicitly wants request inspection in the LunarGate Dashboard on app.lunargate.ai.
backend_url usually does not need to be set manually.
Create the gateway in the Gateways section of app.lunargate.ai and export its LUNARGATE_GATEWAY_API_KEY when you enable this section.
Treat share_prompts and share_responses as privacy decisions, not just observability toggles.
Treat remote_control as joining a Dashboard-managed control plane, not just turning on another metrics feature.
If you toggle this section live, verify the gateway logs once so you can see whether collector export and remote control are actually enabled with the resolved values.

data_sharing¶