For example: | INF: Tracing enabledMySQL_Prepared_Statement::setInt| INF: this=0圆9a2e0| >MySQL_Prepared_Statement::checkClosed| con(driver->connect(host, user, pass)) /*Activate debug trace of the MySQL client library (C API)Only available with a debug build of the MySQL client library!*/con->setClientOption("libmysql_debug", "d:t:O,client. Trace functions are removed by the preprocessor.Ĭompiling the connector with tracing functionality enabled causes two additional tracing function calls per eachĬonnector function call. By default, tracing functionality is not available and calls to The connector as long as you have enabled the tracing module at compile time using cmake It is available with debug and nondebug builds of The second trace is the MySQL Connector/C++ internal trace. Shows the internal function calls and the addresses of internal objects as shown here: >mysql_stmt_init| >_mymalloc| | enter: Size: 816| | exit: ptr: 0圆8e7b8| init_alloc_root| | enter: root: 0圆8e7b8| | >_mymalloc| | | enter: Size: 2064| | | exit: ptr: 0圆8eb28 Trace file, compile MySQL Connector/C++ against a debug version of the library to use this trace. Because only debug versions of the MySQL client library are capable of writing a To enable this trace, the connector will call the mysql_debug()Ĭ API function internally.
Since its introduction, it has been implemented in other operating systems, the most noteworthy being FreeBSD and Mac OS X. The first trace file can be generated by the underlying MySQL client library ( libmysqlclient). DTrace, or Dynamic Tracing, is a powerful diagnostic tool introduced in the Solaris 10 OS. Trace file generated internally by MySQL Connector/C++ Right-click any log file and click Copy to copy the contents of that log file to the clipboard.Trace file generated by the MySQL client library In these logs you can see the time, URL, status, IP address, user and application that opened a connection to the particular website. Filtered websites – This list is useful if you want to view a list of websites that were blocked by Web access protection or Web control. Web control – Shows blocked or allowed URL addresses and details about how they were categorized.ħ. The Event column lists the detected attacks, the Source column tells you more about the attacker and the Protocol column reveals the communication protocol used for the attack.Ħ. Firewall logs contain information about detected attacks on your system. Firewall – The firewall log displays all remote attacks detected by the firewall.
This information is available for a packet capture: Filename Filename specifies the name of the captured packet trace. Select the History tab in the Capture Packet Trace dialog box to view the packet capture history.
Here you can also see details such as device type, serial number, vendor name and media size (if available).ĥ. Collect Logs With Real-Time Monitoring Tool (RTMT) Download RTMT and collect logs, for more information on how to download and collect files refer to IM and Presence Server RTMT Log Collection Configuration Example. Right-click the client, then select Packet Trace History. If the rule does not match a connected device, a log entry for a connected device will not be created. Only devices with a Device control rule will be recorded to the log file.
Use this option for MAC-based configuration instead of IP-based. Destination MACs to be used per each interface.
Output the configuration to a file.-o /etc/trexcfg.yaml-dest-macs. Device control – Contains records of removable media or devices that were connected to the computer. Create a configuration file by specified interfaces (PCI address or Linux names: eth1 etc.)-c 03:00.1 eth1 eth4 84:00.0-dump. Double-click any entry to view the details of a specific computer scan.Ĥ. Computer scan – Results of all completed scans are displayed in this window.
Events – All important actions performed by ESET Endpoint Security for macOS are recorded in the Event logs.ģ. Detected threats – Information about events related to the detection of infiltrations.Ģ. Select the desired log type using the Log drop-down menu at the top of the window. Log files are accessible from the ESET Endpoint Security for macOS main menu by clicking Tools > Log files.
It is possible to view text messages and logs directly from the ESET Endpoint Security for macOS environment, as well as to archive logs. Information is recorded based on the current log verbosity settings. Logging is performed actively in the background with no user interaction. Logging is an essential tool in system analysis, threat detection and troubleshooting. Log files contain information about all important program events that have occurred and provide an overview of detected threats.