Skip to content
NOEMATA

Integrations

An integration configures collection for a software source and installs frames that describe its data. Examples include the Claude Code and OpenTelemetry integrations.

Enabling integrations

On the first noemata up or with noemata up --config, Noemata detects supported software and offers its integration. For example, it checks for the Claude Code binary. An integration can:

  • Configure Noemata’s OTel collector to receive and transform data, such as log files read from disk;
  • Configure the application to send telemetry to Noemata’s OTel collector. integrations.external_edits controls writes to application config files outside the repository;
  • Install frames and other content, viewable in the Noemata app;
  • Write relevant skills to your agent’s skill directory (managed by integrations.skills).

Managed content

Two packs are always installed: Noemata’s own content (@noemata), and the OpenTelemetry semantic layer that other dashboards build on (@opentelemetry).

By default, Noemata replaces managed integration files on each noemata up. Set integrations.managed to false to seed packs once and version-control them. You can also customize managed packs with overlay files. See Ownership & version control.

Installing and building integrations

Integrations are npm packages. Noemata ships a set with the CLI, and any project can install more from npm; see Installing integrations from npm. To write one, see Build an integration.

To enable, manage, or browse what’s available, see Integrations.