Integrations
An integration is how Noemata automatically onboards a source of data - from detecting its availability to installing Frames, eliminating the manual and error-prone labor of defining dashboards and entities. Examples of integrations are the Claude Code integration, and the OpenTelemetry application integration.
Enabling integrations
When you run noemata up for the first time, or noemata up --config, Noemata will auto-detect software that has available integrations. E.g., it will probe for the Claude Code binary, and suggest to install its integration. When you choose to install an integration, it will:
- Configure Noemata’s OTel collector to scrape, ingest and transform data for the specified integration - e.g. by watching and ingesting log files from disk;
- Configure the application itself to send telemetry to Noemata’s OTel collector — this edits that application’s own config, outside the project, so setup asks first and records the answer as
collect.integrations.external_edits; - Install frames and other content that can be viewed in the Noemata app;
- Write relevant skills to your agent’s skill directory (managed by
collect.integrations.skills).
Managed content
Two packs are always installed, regardless of what’s detected: Noemata’s own content, and the OpenTelemetry semantic layer that other dashboards build on.
By default, integrations are managed — Noemata writes their files to disk on noemata up every time, so local edits aren’t persisted. You can instead take ownership of a pack, so it’s seeded once and version-controlled; see Integrations & packs.
Why it matters
Integrations are what make Noemata fast to adopt and easy to grow into. Out of the box you get live dashboards for the things you already run; over time, those same packs are a library of high-quality, real examples — for you and your agent — to learn the authoring model from and adapt into dashboards that fit exactly how you work.
To enable, manage, or browse what’s available, see Integrations & packs.