
Operator by Fibric
Operations Analyst
Ask what is happening in plain language and get an answer grounded in your real data. Then turn that answer into a vetted action.
ConnectorData & events
Governed aggregates from your BigQuery datasets, one canonical definition per metric.
Answers are based on this listing. For anything it can't answer, our team can.
For anything this page can't answer, talk to us.
The BigQuery connector pulls the aggregates behind an operator's metrics from the datasets you grant, running as a service account you create and can revoke. Paired with a semantic pack, each metric compiles to one canonical query, so the number an operator quotes is auditable back to the SQL and the dataset that produced it. Authorized views work naturally here: you can expose exactly the columns the connector should see and nothing else.
The target contract requires verified tenant and source-dataset context and explicit fallback labels. Resumability, coverage, and bookkeeping behavior must be validated for the deployment. BigQuery is managed early access and deliberately read-mostly.
A Google Cloud service account with BigQuery read roles on the datasets you grant, its key stored in your tenant's secret store.
Metric query results from the datasets you grant.
Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.
Target capability: Records read cursors and query receipts in its own dataset. Actual authority, duplicate controls, and recovery depend on the validated deployment and downstream system.
This listing is informational and not self-serve. A deployment review must validate the connector, credentials, action boundary, recovery path, support, and contractual pricing before use.
Your deployment engineer verifies each line with you during onboarding.
This connector is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.
Listings this is designed to pair with. Each listing has its own live or managed early-access state.

Operator by Fibric
Ask what is happening in plain language and get an answer grounded in your real data. Then turn that answer into a vetted action.
Data & events connector
A managed early-access pattern for querying governed warehouse metrics with source context and explicit missing-state handling.
Data & events connector
Reads your operational tables under row-level tenant isolation, the same wall that keeps tenants out of each other's data.
Data & events connector
Watches a bucket for the report, feed, or proof file that lands: an inbox an ingest operator can pick up and normalize.
This connector is developed, published, and supported by Fibric. It integrates with BigQuery through published APIs. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy
Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.