Running the diagnostic tool creates an analytic package which contains information about the current state of the Database Security sensor including sensor log files. Provide the analytic package to Customer Success when you request assistance.
You can change the sensor log level and create an Analytic package remotely.
Follow these steps when the sensor is displayed as Disconnected from the Database Security server console:
Change the log level from INFO to DEBUG in the sensor configuration file as follows:
On Linux —
/etc/sysconfig/mfe-dbs-sensorOn Solaris —
/etc/default/mfe-dbs-sensorOn AIX —
/etc/mfe-dbs-sensorOn HPUX —
/etc/rc.config.d/mfe-dbs-sensorOn Windows —
TrellixDBSConfig.exe
Run the Database Security sensor for 10 minutes.
Run the diagnostic tool:
On Linux —
/sbin/service mfe-dbs-sensor create_analytic_packageOn Solaris —
/etc/init.d/mfe-dbs-sensor create_analytic_packageOn AIX —
/etc/rc.d/init.d/mfe-dbs-sensor create_analytic_packageOn HPUX —
/sbin/init.d/mfe-dbs-sensor create_analytic_packageOn Windows —
Analytics.exe
Save the Analytic package.
Restore the log level in the web console to INFO after troubleshooting is complete.
Follow these steps when the sensor is displayed as Connected from the Database Security server console:
On the Sensors page, click Properties next to the appropriate sensor.
From the Log Level drop-down list, select DEBUG.
Run the Database Security sensor for 10 minutes (no sensor restart is required) and repeat that action resulting in the issue as many times as possible in those 10 minutes.
Click Generate.
Restore the log level in the web console to INFO after troubleshooting is complete.
The Analytic package file name is displayed in the web console when the process is complete. Send the file by email to the Customer Success team.