This page describes the steps required to install Database Collector on Linux (Debian). 

Ensure that the machine on which you install the Database Collector has network access to the databases you want to monitor.

Perform the following steps:

  1. Add the Splunk AppDynamics repository:

    sh -c "echo 'deb [trusted=yes] https://appdynamics.jfrog.io/artifactory/deb-hosted/ appdynamics main' >> /etc/apt/sources.list"
    CODE
  2.  Refresh the list of packages:

    apt update
    CODE
  3. Display the information about the package:

    apt show appddbcollector -a
    CODE
  4. Install the Database Collector:

    apt install appddbcollector
    CODE
  5. Update the configuration file /opt/appdynamics/appddbcol/conf/appddbcollector.yaml:

    appddbcollector.yaml

    appdynamics_credentials:
      client_id: <client-id>
      client_secret: <secret>
      endpoint: <data-endpoint>
      token_url: <auth-endpoint>  
    
    # Set below fields in the config to provide SSL details
    # tlsConfig:
    #  certificate: <certificate>
    #  hostNameInCertificate: <hostname>
    
    # Set below field in the config to specify environment (defaults to self-hosted)
    # environment:
    #  platform: self-hosted # Other possible properties "AWS", "Azure"
    
    monitoring_config:
      sqlserver/1:
        configName: ${CONFIG_NAME}
        hostname: ${HOSTNAME}
        hostport: ${HOSTPORT}
        username: ${USERNAME}
        password: ${PASSWORD}
        database: ${DATABASE}
        tlsConfig:
          certificate: ${CERTIFICATE_CRT}
          hostNameInCertificate: ${HOSTNAMEINCERTIFICATE}
        environment:
          platform: ${CLOUD_CONFIG}
      mysql/1:
        configName: ${CONFIG_NAME}
        hostname: ${HOSTNAME}
        hostport: ${HOSTPORT}
        username: ${USERNAME}
        password: ${PASSWORD}
        environment:
          platform: ${CLOUD_CONFIG}
        tlsConfig:
          certificate: ${CERTIFICATE_CRT}
          hostNameInCertificate: ${HOSTNAMEINCERTIFICATE}
      aurora-mysql/1:
        configName: ${CONFIG_NAME}
        hostname: ${HOSTNAME}
        hostport: ${HOSTPORT}
        username: ${USERNAME}
        password: ${PASSWORD}
        environment:
          platform: ${CLOUD_CONFIG}
        tlsConfig:
          certificate: ${CERTIFICATE_CRT}
          hostNameInCertificate: ${HOSTNAMEINCERTIFICATE}
      mariadb/1:
        configName: ${CONFIG_NAME}
        hostname: ${HOSTNAME}
        hostport: ${HOSTPORT}
        username: ${USERNAME}
        password: ${PASSWORD}
        environment:
          platform: ${CLOUD_CONFIG}
        tlsConfig:
          certificate: ${CERTIFICATE_CRT}
          hostNameInCertificate: ${HOSTNAMEINCERTIFICATE} 
      aurora-postgresql/1:
        configName: ${CONFIG_NAME}
        hostname: ${HOSTNAME}
        hostport: ${HOSTPORT}
        username: ${USERNAME}
        password: ${PASSWORD}
        environment:
          platform: ${CLOUD_CONFIG}
        tlsConfig:
          certificate: ${CERTIFICATE_CRT}
      postgres/1:
        configName: ${CONFIG_NAME}
        hostname: ${HOSTNAME}
        hostport: ${HOSTPORT}
        username: ${USERNAME}
        password: ${PASSWORD}
        environment:
          platform: ${CLOUD_CONFIG}
        tlsConfig:
          certificate: ${CERTIFICATE_CRT}
    YML

    • Specify aws or azure for the platform field. Keep the field empty if you are not using any of these platforms.
    • By default, logs are available in the /opt/appdynamics/appddbcol/logs directory.
  6. Restart the service:

    systemctl restart appddbcollector
    CODE

    You can check the logs using the following command:

    tail -f /opt/appdynamics/appddbcol/logs/appddbcollector.log
    CODE