Skip to main content

Telemetry and plugins

Both features are off by default because each widens the installation's trust boundary.

Telemetry​

Jiandu does not send remote telemetry in the local profile. An administrator can explicitly configure bounded OTLP/HTTP export. Product-use metrics require separate consent.

Before enabling export:

  • identify the exact collector and who can read it;
  • use TLS for any non-loopback destination;
  • confirm retention and access rules at the collector;
  • test failure behavior when the collector is unavailable;
  • avoid treating telemetry as a backup or audit archive.

Jiandu rejects plaintext OTLP to a non-loopback destination unless the operator makes the required explicit opt-in.

Plugins​

Plugins are an expert, owner-reviewed feature. They are disabled by default and run with reduced isolation when enabled. Install only a package whose source and requested capabilities you understand.

For each plugin:

  1. Pin the reviewed package and version.
  2. Grant the smallest capability set that makes it useful.
  3. Keep secrets out of plugin configuration where possible.
  4. Test with non-sensitive documents.
  5. Review logs and generated changes.
  6. Know how to disable it without losing access to originals.

Plugin authoring belongs in Development; operating one belongs here.