DataEx
DataEx
DataEx is the console group for the people who consume what the platform decides: which agents act and within what limits, which models serve them and where, and what TIDE found.
The DataEx pages (Models & inference and Trust are sub-tabs of Agents)
| Row | ?tab= | What it answers |
|---|---|---|
| Agents | agents | What does each agent do, which model answers it, how autonomous is it, who may arm it, and what did it run? |
| Agents › Models & inference | inference (a sub-tab of Agents) | Which model serves each tier, where, and is it running what its card says? |
| Estate | resolve | Data maturity and probe maintenance over the rules, also applied to the infrastructure through its IaC definitions: what the sources contain, how data is used, and does each source match what it declares? |
| Agents › Trust | harness (a sub-tab of Agents) | What did TIDE find, and what can it do about each finding? |
Connections and the data-access runners are in the rail footer, under Integrations.
The datagov agent’s controls, verdicts and what it never reads.
DataEx HTTP routes and their auth class.
Error strings from the console and the CLI, with cause and fix.
Three rules that hold across DataEx
- Reads never dial. No page load contacts a tenant source. The one path that dials a registered source is DataEx › Estate’s actions (Test, Explore, Access patterns, Map estate), run only on an admin’s action.
- Credentials are write-only. No read returns a connection’s credential bundle.
- Unread is never empty. When the console cannot read a source it says so (
source:"unavailable",complete:false, anunmeasured[]entry with the reason). It does not report “none”.
Where the installation’s data sources live
All of the installation’s PostgreSQL, MySQL and Kafka sources are served in one shared namespace,
data-systems, and the console registers them from a manifest it reads in its own namespace
(tide-system, ConfigMap tide-connection-manifests). A manifest holds names only:
- A credential is a reference to a key of a Secret in
data-systems(fromSecret). The console reads it at the moment a connector needs it and never stores, logs or serves the value. - A setting that lives in a Secret, such as the Kafka broker’s CA certificate (
ssl_ca_pem), is asettingsFromSecretentry. If the Secret or key is missing, that connection is reported BLOCKED (Connections › Needs setup, with the Secret and key named). It is never registered with an empty setting. - Kafka is SASL over TLS only. The console refuses a Kafka record whose
security_protocolisplaintextorsasl_plaintext, or that turns off certificate verification, and the connector refuses it too. Databases aressl_mode = requireor stricter. - Only namespaces in
TIDE_CREDENTIAL_SECRET_NAMESPACES(defaultdata-systems) can be referenced; the platform’s own namespaces are refused even if listed.