Connectors

Connectors define the data sources that Bigeye agents connect to. Each connector type has specific configuration requirements (credentials, hostnames, etc.) that the Agent CLI walks you through interactively.

Adding Connectors

# Interactive — prompts for connector type
./bigeye-agent add-connector

# Specify connector type directly
./bigeye-agent add-connector -c snowflake
./bigeye-agent add-connector -c tableau

# Add multiple connector types at once
./bigeye-agent add-connector -c snowflake -c bigquery

# Import from an existing properties file
./bigeye-agent add-connector -c snowflake --from-existing /path/to/snowflake.properties

# Skip connection validation
./bigeye-agent add-connector -c snowflake --skip-validation

Option	Description
`--connector`, `-c`	Connector type (e.g., `snowflake`, `databricks`). Can be specified multiple times. If omitted, you'll be prompted.
`--from-existing`, `-fe`	Path to an existing properties file to import configuration from. Only works with a single connector type.
`--skip-validation`, `-sv`	Skip validation of connector configuration during setup.

Editing Connectors

# Interactive — prompts for connector type and connection
./bigeye-agent edit-connector

# Specify connector type
./bigeye-agent edit-connector -c snowflake

The edit-connector command removes the existing connection configuration and walks you through setup again. After editing, agent configuration files are regenerated and the agent is restarted.

Deleting Connectors

# Interactive — prompts for connector type and connection
./bigeye-agent delete-connector

# Specify connector type
./bigeye-agent delete-connector -c snowflake

# Specify connector type and connection name
./bigeye-agent delete-connector -c snowflake -cn my_connection

The delete-connector command removes a connection from the agent configuration. You will be asked to confirm before the connection is deleted. After deletion, agent configuration files are regenerated and the agent is restarted. If the deleted connection was the last one for its connector type, the entire connector entry is removed.

For database connectors, the corresponding source is also deleted from Bigeye when the data source agent is configured.

Option	Description
`--connector`, `-c`	Connector type (e.g., `snowflake`, `databricks`). Can be specified multiple times. If omitted, you'll be prompted.
`--connection-name`, `-cn`	Name of the connection to delete. Required when multiple connections exist for a connector type.

Modifying Connectors via YAML

You can also edit connector configuration directly in bigeye_agent.yml. After editing, run:

./bigeye-agent sync

This regenerates the agent configuration files from the updated YAML.

Supported Connector Types

The table below lists all supported connectors and the CLI name to use with the -c flag.

Connector	CLI flag
AtScale	`-c atscale`
Azure Data Factory / Synapse Pipelines	`-c datafactory`
BigQuery	`-c bigquery`
Custom Data Mappings	`-c customdatamappings`
Databricks	`-c databricks`
DB2	`-c db2`
dbt	`-c dbt`
Fivetran	`-c fivetran`
Informatica PowerCenter	`-c powercenter`
Looker	`-c looker`
Looker v2	`-c looker_v2`
Matillion	`-c matillion`
Oracle	`-c oracle`
PostgreSQL	`-c postgresql`
Power BI	`-c powerbi`
Qlik Replicate	`-c qlikreplicate`
Qlik Sense	`-c qliksense`
Redshift	`-c redshift`
SAP CalcViews	`-c sap_calcviews`
SAP HANA	`-c saphana`
Snowflake	`-c snowflake`
SnapLogic	`-c snaplogic`
SQL Server	`-c sqlserver`
SSIS	`-c ssis`
SSRS	`-c ssrs`
Synapse	`-c synapse`
Tableau	`-c tableau`
Teradata	`-c teradata`

# Interactive — prompts for connector type
./bigeye-agent add-connector

# Specify connector type directly
./bigeye-agent add-connector -c snowflake
./bigeye-agent add-connector -c tableau

# Add multiple connector types at once
./bigeye-agent add-connector -c snowflake -c bigquery

# Import from an existing properties file
./bigeye-agent add-connector -c snowflake --from-existing /path/to/snowflake.properties

# Skip connection validation
./bigeye-agent add-connector -c snowflake --skip-validation

Option	Description
`--connector`, `-c`	Connector type (e.g., `snowflake`, `databricks`). Can be specified multiple times. If omitted, you'll be prompted.
`--from-existing`, `-fe`	Path to an existing properties file to import configuration from. Only works with a single connector type.
`--skip-validation`, `-sv`	Skip validation of connector configuration during setup.

Editing Connectors

# Interactive — prompts for connector type and connection
./bigeye-agent edit-connector

# Specify connector type
./bigeye-agent edit-connector -c snowflake

The edit-connector command removes the existing connection configuration and walks you through setup again. After editing, agent configuration files are regenerated and the agent is restarted.

Modifying Connectors via YAML

You can also edit connector configuration directly in bigeye_agent.yml. After editing, run:

./bigeye-agent sync

This regenerates the agent configuration files from the updated YAML.

Supported Connector Types

The table below lists all supported connectors and the CLI name to use with the -c flag.

Connector	CLI flag
AtScale	`-c atscale`
Azure Data Factory / Synapse Pipelines	`-c datafactory`
BigQuery	`-c bigquery`
Custom Data Mappings	`-c customdatamappings`
Databricks	`-c databricks`
DB2	`-c db2`
dbt	`-c dbt`
Fivetran	`-c fivetran`
Informatica PowerCenter	`-c powercenter`
Looker	`-c looker`
Looker v2	`-c looker_v2`
Matillion	`-c matillion`
Oracle	`-c oracle`
PostgreSQL	`-c postgresql`
Power BI	`-c powerbi`
Qlik Replicate	`-c qlikreplicate`
Qlik Sense	`-c qliksense`
Redshift	`-c redshift`
SAP CalcViews	`-c sap_calcviews`
SAP HANA	`-c saphana`
Snowflake	`-c snowflake`
SnapLogic	`-c snaplogic`
SQL Server	`-c sqlserver`
SSIS	`-c ssis`
SSRS	`-c ssrs`
Synapse	`-c synapse`
Tableau	`-c tableau`
Teradata	`-c teradata`

SQL Server Kerberos Authentication

SQL Server supports four authentication modes: SQL Server (username/password), Windows, Entra ID (Azure AD service principal), and Kerberos.

When Kerberos is selected, the installer prompts for:

Prompt	Description
Kerberos principal	e.g. `[email protected]`
Path to keytab file	Per-source keytab; copied into the agent config directory as `<connection_identifier>__<original_basename>` so multiple Kerberos sources can be added without filename collisions
JAAS configuration name	Defaults to `Bigeye_<connection_identifier>`; same value is used in `jaas.conf` and the JDBC URL's `jaasConfigurationName=` parameter
Path to `krb5.conf`	Prompted once per install; subsequent Kerberos connectors reuse it

Stored-procedure mapping is automatically skipped for Kerberos SQL Server sources as it is not currently supported.

A single krb5.conf is shared across every Kerberos-authenticated SQL Server source. Keytabs can be per-source, or multiple Kerberos identities can be merged into a single keytab and referenced from each connector.