Splunk® DB Connect

Deploy and Use Splunk DB Connect

Share data in Splunk DB Connect

The main purpose of collecting telemetry data from a DB Connect perspective is to gather real-time insights related to performance and feature adoption. Telemetry data collection is enabled by default. However, you can disable it at any time. To disable Telemetry data collection:

  1. Go to $SPLUNK_HOME/etc/apps/splunk_app_db_connect/local/dbx_setings.conf.
  2. Change enabled to false for the [telemetry] stanza.
    [telemetry]
    enabled = false
    


How we collect telemetry data

Splunk DB Connect uses the Splunk Telemetry API to collect data. It does not collect sensitive information or data that is processed or ingested.

What telemetry data we collect

Information about search time commands

It allows us to know if the search time command works well and which databases are most used.

Attribute Type Description Example
command string Search time command executed. dbxquery
connection_type string Connection used to execute the underlying database query. mysql
execution_time long Total time from when we receive the request until we return a result. 10000
total_records int Amount of retrieved records. 1000
total_records_bytes long Size in disk of the amount of retrieved records. 100


Information about user behavior

It allows us to know which are the most used functionalities and if the Customer uses our API to develop custom integrations, etc.

Attribute Type Description Example
action string Action performed. delete
source string API or UI. Customer can have custom integration using our API directly. UI
resource string Object type, e.g. connection, identity, input, output. connection


Information about data ingestion

It allows us to know which databases and types of inputs are the most used.

Attribute Type Description Example
connection_type string Connection type used by the input, it allows to determine the database vendor usage. mysql
input_mode string Rising or batch, it helps to determine most common scenarios. rising
execution_time long Total time from when we execute the SQL query until the events are sent through the HEC. 100
total_records int Amount of retrieved records. 1000


For more information about how Splunk collects and uses data, refer to the Splunk Privacy Policy.

Last modified on 30 January, 2025
About Splunk DB Connect   How Splunk DB Connect works

This documentation applies to the following versions of Splunk® DB Connect: 4.0.0


Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters