Instruments, loggers, and groups

The Instruments area contains views for instruments, loggers, groups, and sites. The views you see depend on your project access.

Add an instrument

Choose Create instrument, enter its name, and select a site. You can assign groups, a position, and a logger when those controls are available. Connected ingestion workflows can also create or map instruments as part of their setup.

Choose the name before you begin sending data: instrument names are fixed after creation. Use a consistent field identifier such as PZ-01 or TILT-NORTH-03. Confirm that the name produced by an FTP parser or API sender is the name you intend to use.

On the detail page you can inspect the graph and values, edit the site, groups, logger assignment, and location, and manage variables and calculations.

Represent acquisition hardware with loggers

A logger is acquisition or transport hardware that may serve zero or more instruments. It has its own display name, metadata, location, and optional provider identity. Create and inspect loggers from the Loggers view.

An instrument can have one logger assignment or an explicit “No Logger” assignment. Manual changes are recorded as manual assignments. For provider-managed assets, inspect the existing relationship before overriding it.

Use the logger detail to understand which instruments are associated with a device. Do not treat a logger as an instrument channel; measurements belong to variables on instruments.

Create useful groups

Choose Create group, then add instruments or loggers from the group detail page. Membership is manual and scoped to the project. Examples include a sensor family, a subcontractor’s equipment, or a review package.

Instrument and logger memberships are independent. Adding a logger to a group does not move its instruments into that group or change their assignments. Instrument groups can also define instrument access scope, so review grants when changing membership.

Keep historical identities intact

Use Include archived to locate retired instruments. Archiving an instrument stops ingestion and calculation while preserving its recorded history. Reconfigure active dependent calculations before archiving their inputs. See Archiving and lifecycle for restoration behavior.