Release Version: AlphaRelease VersionAlpha

The Omnidots source imports vibration records from one selected measuring point in Omnidots Honeycomb.

Setup

Prerequisites

Before setting up this integration, make sure you have:

  • An Omnidots API token
  • Access to the Omnidots measuring point you want to import

Credential Setup

Use Omnidots Credentials to create or select the credential for this integration. IMSURGE uses the credential to list available measuring points during setup and to read records during pipeline runs.

Integration Setup

After selecting the Omnidots credential, configure the source using:

  • Measuring Point - The Omnidots measuring point IMSURGE should read from.
  • Record Type - The scalar record type to import: Peak, VDV, or Veff.

Some options may include sensor details for context, but the selected value is the measuring point.

Reference

Credential fields are documented in Omnidots Credentials.

Initial and backtrack fetches are limited to 7 days. Subsequent executions follow the configured pipeline polling rate, up to 24 hours.

Data Type Recommended Backtrack
Omnidots records 1hr Up to 7 days
Field Description Required
Measuring Point Omnidots measuring point IMSURGE reads from. ✓
Record Type Scalar record type to import: Peak, VDV, or Veff. ✓
Record Type Metrics Units
Peak Peak Fdom X/Y/Z, Peak Vtop X/Y/Z Fdom: Hz, Vtop: mm/s
VDV VDV X/Y/Z m/s^1.75
Veff Veff X/Y/Z mm/s

Limitations

  • Live validation - No-data responses, maximum fetch windows, rate limits, UTC timestamp behavior, partial or missing axis values, and final Vtop unit confirmation still need validation with live credentials.
  • Trace data - Omnidots trace and waveform data is not currently exposed by this source integration. Traces are 1kHz x/y/z waveform arrays rather than ordinary scalar records.
  • Alpha Integration - Omnidots is an alpha integration. Results may vary while the integration is being validated.

External References