@plusscommunities/pluss-llm-telemetry-aws

Dependency-free CommonJS telemetry for Pluss Communities LLM invocations. The package exports:

• withLlmTelemetry(options), which records one JSON-safe llm.invocation event while preserving the provider result or thrown-error identity.
• GLOBAL_COMMUNITY_ID, the attribution value for model calls that are not scoped to one community.

The event includes the complete normalized prompt and completion, model and operation identifiers, token usage, latency, pricing evidence, feature/community attribution, trace correlation, and projected provider diagnostics. usageIncomplete is 1 when either input or output usage is missing. telemetryError distinguishes a success-extraction failure from legitimately absent provider usage. Callers must provide deployment-pinned USD token pricing and may inject extraction, logging, clock, invocation-ID, and onTelemetryError functions. Logger failures never replace the provider outcome; without an injected reporter they produce a minimal JSON-safe llm.telemetry_error line on stderr.

Import boundary

Backend extensions must not import this package directly. They must use the stable core facade:

const {
  GLOBAL_COMMUNITY_ID,
  withLlmTelemetry,
} = require("@plusscommunities/pluss-core-aws/helper/llmTelemetry");

Parent backend services that do not need the legacy core package may depend on this zero-runtime-dependency package directly.

Release order

Release consumers only in this order:

1. Publish @plusscommunities/[email protected].
2. Publish @plusscommunities/[email protected], whose facade depends on telemetry 1.0.0.
3. Publish every newsletter package variant at 2.0.12, then update and release the parent minuss-aws support-assistant integration.
4. After committing these extension-repository changes, update the pluss-extension-aws gitlink in the real parent minuss-aws repository to that extension commit.

Do not publish core or install it in a registry-exact consumer before telemetry 1.0.0 is available.