OIAnalytics®
Query time series data from OIAnalytics® SaaS application.
Connection Settings
Main Configuration
| Setting | Description | Example Value |
|---|---|---|
| Use OIAnalytics registration | Use pre-configured connection settings from OIAnalytics registration. Default: enabled. | Enabled/Disabled |
| Timeout | Duration in seconds before connection failure is reported. Default: 30. | 30 |
Manual Configuration (when registration not used)
| Setting | Description | Example Value |
|---|---|---|
| Host | Hostname of the OIAnalytics® SaaS application. | https://optimistik.oianalytics.com |
| Accept unauthorized certificate | Enable if HTTP queries pass through a firewall that strips certificates. | Enabled/Disabled |
Authentication Settings
| Setting | Description | Example Value |
|---|---|---|
| Authentication method | Authentication type for the connection. | Access key/Secret, Azure AD (Client Secret), Azure AD (Certificate) |
| Access key | Access key for Access key/Secret authentication. | my_access_key |
| Secret | Secret for Access key/Secret authentication. | •••••••• |
| Tenant ID | Azure AD tenant identifier (for Azure AD methods). | tenant-id-uuid |
| Client ID | Azure AD client identifier (for Azure AD methods). | client-id-uuid |
| Client Secret | Azure AD client secret (for Azure AD Client Secret method). | •••••••• |
| Certificate | Certificate file path (for Azure AD Certificate method). | /path/to/cert.pem |
| Scope | OAuth scope (for Azure AD Certificate method). | https://resource/.default |
Proxy Configuration
| Setting | Description | Example Value |
|---|---|---|
| Use proxy | Route requests through a proxy server. | Enabled/Disabled |
| Proxy URL | URL of the proxy server. | http://proxy.example.com:8080 |
| Proxy username | Username for proxy authentication (if required). | proxy_user |
| Proxy password | Password for proxy authentication (if required). | •••••••• |
Group Settings
Items can be organised into groups. Each group defines a shared collection schedule and default throttling settings. Items in the same group are still fetched one at a time in sequence — the group simply provides common defaults that individual items can override.
| Setting | Description | Example Value |
|---|---|---|
| Name | Unique label for the group within this connector. | Group A |
| Scan mode | Schedule used to collect all items in the group. | Every 1 min |
| Throttling | Default throttling values (Max read interval, Read delay, Overlap) inherited by items in the group. | 3600, 200, 0 |
Item Settings
Each item can be individually configured. Items inherit their scan mode and throttling defaults from their group, but each setting can be overridden per item by disabling Sync with group.
Throttling Settings
Throttling controls how OIBus paces historical data requests. These settings appear on each group (for connectors that support groups) or on each item (for single-item connectors). Items in a group can override the group defaults by disabling the Sync with group toggle.
| Setting | Description | Example Value |
|---|---|---|
| Max read interval | Maximum duration of each sub-query in seconds. Larger time ranges are automatically split into chunks not exceeding this value. | 3600 |
| Read delay | Pause in milliseconds between consecutive sub-queries. Helps prevent server overload and manages rate limits. | 1000 |
| Overlap | Time in milliseconds subtracted from @StartTime of each query to capture late-arriving data from the previous interval. | 60000 |
How Throttling Works
- Interval splitting — A 24-hour range with
Max read interval = 3600(1 hour) is split into 24 separate 1-hour sub-queries. - Read delay — A pause is inserted between sub-queries to manage server load.
- Overlap — With
Overlap = 60000(1 minute), a query for[10:00–11:00]actually requests[9:59–11:00], ensuring no late-arriving data is missed.
The overlap value is subtracted from the start of the overall query, not from the start of each individual sub-interval when a large range is split into chunks.
Recommended Configurations
| Scenario | Max read interval | Read delay | Overlap |
|---|---|---|---|
| Stable network, small datasets | 3600 (1 hour) | 500 | 0 (no overlap) |
| Unstable network | 1800 (30 min) | 2000 | 0 (no overlap) |
| Large historical retrievals | 7200 (2 hours) | 1000 | 0 (no overlap) |
| Real-time with occasional gaps | 900 (15 min) | 200 | 15000 (15 sec) |
Endpoint Settings
| Setting | Description | Example Value |
|---|---|---|
| Endpoint | API endpoint for HTTP requests | /api/oianalytics/data/values |
Query Parameters
Query Variables:
@StartTime: Initial execution time, updates to most recent timestamp from results@EndTime: Current time (now()) or sub-interval end when queries are split
Large time intervals are automatically divided into smaller chunks using:
- Max read interval (from throttling settings)
- Reduces server and network load
- Improves data stream resilience
CSV Serialization Options
| Setting | Description | Example Value |
|---|---|---|
| Filename | Output filename pattern with variables: @ConnectorName, @CurrentDate | data_@ConnectorName.csv |
| Delimiter | Field separator character | COMMA (,), SEMI_COLON (;), DOT (.), COLON (:), PIPE (|), SLASH (/), TAB (\t), NON_BREAKING_SPACE |
| Compression | Enable gzip compression | Enabled/Disabled |
| Output datetime format | Format for datetime fields in CSV | yyyy-MM-dd HH:mm:ss |
| Output timezone | Timezone for datetime values | UTC or Europe/Paris |
@ConnectorName: Connector name@CurrentDate: Current timestamp inyyyy_MM_dd_HH_mm_ss_SSSformat (fixed format)- Datetime format setting doesn't affect filename timestamp