Oninit® Grafana Data Sources — Configure
Both plugins share the same connection model: a single Informix® wire-listener endpoint, optional TLS, and standard Informix authentication. The configuration editor is reached from Connections → Data sources → Add data source after the plugin is installed.
Connection
| Field | Required | Description |
|---|---|---|
| URL | yes | Wire-listener endpoint, including scheme and port. Example: https://informix.example.com:9089. The plugin issues all requests as POST against this base URL. |
| Database | yes | Default database name. Queries that do not specify a database explicitly resolve against this one. |
| User | yes | Informix user the wire listener authenticates as. The user needs the appropriate SELECT / EXECUTE privileges for the queries the panel will run. |
| Password | yes | Stored as a Grafana secret — readable only by the Grafana server process, never returned to the UI after save. |
TLS
The plugin honours the wire-listener's TLS configuration directly. Three modes are supported via the TLS / SSL section of the editor:
| Mode | Description |
|---|---|
| None | Plain TCP. Suitable for same-host or trusted-network deployments only. |
| Server certificate | Verify the listener's certificate against the host's CA bundle. The default and recommended mode for any cross-network deployment. |
| Client certificate (mutual TLS) | Paste the PEM-encoded client certificate and key into the secure-data fields. The wire listener must be configured to require client authentication. |
The Skip TLS verify toggle exists for local-development convenience only; production deployments should keep certificate verification enabled.
Per-plugin notes
The two plugins differ only in the query-side fields exposed by the query editor. The connection-side configuration is identical:
- oninit-json-datasource — the query editor exposes collection, filter, projection, sort, and limit fields. The connection editor adds a Default collection field for queries that omit it.
- oninit-wire-datasource — the query editor exposes a single SQL text area for pure SQL statements. The editor handles ordinary relational SQL plus the two SQL surfaces Informix exposes for TimeSeries data — direct TS SQL routine calls (Calendar, GetRange, Apply, Hits, …) against a TimeSeries column, and Virtual Table (VT) selects that present a TimeSeries column as a relational view. The connection editor adds no extra fields beyond the shared connection set.
Test
The Save & test button at the bottom of the editor issues a health request against the listener and surfaces either a success banner or the listener's error message verbatim. A typical first-run failure is a TLS-verification mismatch (certificate common name does not match the URL hostname) or an authentication failure (the configured user lacks CONNECT privilege on the named database). Both surface as plain-text listener responses in the test result.