Sample Source Configurations
Here are some examples for configuring the agent to connect to various data sources:
##########
# BigQuery
##########
# sources:
# - identifier: Example BigQuery source
# connectionFactory:
# type: bigquery
# host: https://www.googleapis.com/bigquery/v2
# port: 443
# Add the BQ key file to the agent_config directory and reference it below for the agent
# keyFile: /app/config/bigquery_credentials.json
# maxConcurrentInteractiveActivities: 1
# maxConcurrentActivities: 3
#
##########
# Databricks
##########
# Server Hostname, Port, and Http Path should be pulled from Databricks Advanced Options (JDBC/ODBC tab).
# Personal Access Tokens can be generated in your Databricks UI:
# https://docs.databricks.com/en/dev-tools/auth.html#token-management
# Additional info can be found here:
# https://docs.bigeye.com/docs/connecting-to-databricks-deltalake#2-gather-connection-details-from-delta-lake
# - identifier: Example Databricks source
# connectionFactory:
# type: spark
# host: example.cloud.databricks.com
# port: 443
# user: Http Path (ie sql/protocolv1/o/5542344243/54935-34534-anon123)
# password: Personal Access Token (ie. 4f9aaac66235d46a4b12ebf1f058a62c101)
#
# - identifier: Example Databricks oauth source
# connectionFactory:
# type: spark
# host: example.cloud.databricks.com
# port: 443
# databaseName: Http Path (ie sql/protocolv1/o/554234234713/5945-34534-anon123)
# user: Oauth App Name (i.e. d58c5cad-47fb-4d3b-9de5-008d3327bb33)
# password: Oauth Secret (i.e. dose984735ab8ab7aa9a47)
# authType: AUTH_TYPE_OAUTH2_M2M
#
##########
# Redshift
##########
# - identifier: Example Redshift source
# connectionFactory:
# type: redshift
# host: example.redshift.amazonaws.com
# port: 5439
# user: user
# password: "password"
# databaseName: somedb
#
##########
# Snowflake
##########
# - identifier: Example Snowflake username/password source
# connectionFactory:
# type: snowflake
# host: example.snowflakecomputing.com
# port: 443
# user: user
# password: "password"
# # NOTE - for snowflake, put the warehouse name as the databaseName
# databaseName: somewarehousename
#
#
# - identifier: Example Snowflake keypair source
# connectionFactory:
# type: snowflake
# host: example.snowflakecomputing.com
# port: 443
# user: user
# authType: AUTH_TYPE_KEYPAIR
# keyFile: "/path/to/rsa_key.p8"
# password: "privateKeyPassword"
# # NOTE - for snowflake, put the warehouse name as the databaseName
# databaseName: somewarehousename
#
##########
# Oracle
##########
# - identifier: Example Oracle source
# connectionFactory:
# type: oracle
# host: oracle.example.com
# port: 1521
# user: user
# password: "password"
# databaseName: somedb
#
# If you need to provide custom configuration to the Oracle JDBC driver, you can use the
# jdbcUrl options instead of the host, port, and databaseName combination. To configure an
# SSL connection to your Oracle database, you must first mount a copy of the Java Key Store
# with the necessary certificates somewhere the agent can access it while running. The
# example JDBC URL below has the necessary options to connect using SSL. The full list of
# options that can be specified on an Oracle JDBC URL can be found here:
# https://docs.oracle.com/en/database/oracle/oracle-database/21/jajdb/oracle/jdbc/OracleConnection.html
#
# - identifier: Example Oracle Custom JDBC URL SSL source
# connectionFactory:
# type: oracle
# user: user
# password: "password"
# jdbcUrl: jdbc:oracle:thin:@tcps://<host>:2484/<databaseName>?javax.net.ssl.trustStore=<path/to/JKS>&javax.net.ssl.trustStoreType=JKS&javax.net.ssl.trustStorePassword=<JKS password>
#
##########
# SAP HANA
##########
# - identifier: Example SAP HANA source
# connectionFactory:
# type: sap
# host: hana.example.com
# port: 39017
# user: user
# password: "password"
# databaseName: somedb
#
##########
# Synapse
##########
# - identifier: Example synapse source
# connectionFactory:
# type: synapse
# host: example.sql.azuresynapse.net
# port: 1433
# user: user
# password: "password"
# databaseName: somedb
#
##########
# Teradata
##########
# The Teradata JDBC driver isn't included with the Bigeye Data Source agent due to licensing restrictions, so it is
# necessary to download it onto the host where the agent will be running. Do this after the agent setup steps have
# been run.
# See: https://docs.bigeye.com/docs/agent-connection#teradata-jdbc-driver
#
# - identifier: Example Teradata source
# connectionFactory:
# type: teradata
# host: 10.123.123.123
# port: 1025
# user: user
# password: "password"
##########
# Netezza
##########
# The Netezza JDBC driver isn't included with the Bigeye Data Source agent due to licensing restrictions, so it is
# necessary to download it onto the host where the agent will be running. Do this after the agent setup steps have
# been run.
# See: https://docs.bigeye.com/docs/agent-connection#netezza-jdbc-driver
#
# - identifier: Example Netezza source
# connectionFactory:
# type: netezza
# host: 10.123.123.123
# port: 5480
# user: user
# password: "password"
# databaseName: somedb
##########
# Vertica
##########
# - identifier: Example Vertica source
# connectionFactory:
# type: vertica
# host: 10.123.123.123
# port: 5433
# user: user
# password: "password"
# databaseName: somedb
Updated 9 days ago