The Error Log log_error_services=’log_filter_internal; log_sink_internal; log_sink_json’ SET PERSIST log_error_services = ’log_filter_internal; log_sink_internal; log_sink_json’; log_filter_internal; log_sink_1; log_sink_2 log_sink_1; log_filter_internal; log_sink_2 1028 •If  --console  is given, the default destination is the console. ( --console  takes precedence over  -- log-error  if both are given, and the following items regarding  --log-error  do not apply.) Default Error Log Destination on Windows On Windows,  mysqld  uses the  --log-error ,  --pid-file , and  --console  options to determine whether the default error log destination is the console or a file, and, if a file, the file name: The server interprets options that determine the default error log destination somewhat differently for Windows and Unix systems. Be sure to configure the destination using the information appropriate to your platform. After the server interprets the default error log destination options, it sets the  log_error  system variable to indicate the default destination, which affects where several log sink components write error messages. The following sections address these topics. •How the Default Error Log Destination Affects Log Sinks •Default Error Log Destination on Unix and Unix-Like Systems •Default Error Log Destination on Windows In this discussion, “console”  means  stderr , the standard error output. This is your terminal or console window unless the standard error output has been redirected to a different destination. This section describes which server options configure the default error log destination, which can be the console or a named file. It also indicates which log sink components base their own output destination on the default destination. If the enabled log components include a sink that provides Performance Schema support, events written to the error log are also written to the Performance Schema  error_log  table. This enables examining error log contents using SQL queries. Currently, the traditional-format  log_sink_internal  and JSON-format log_sink_json  sinks support this capability. See Section 27.12.21.1, “The error_log Table” . Note 5.4.2.2 Default Error Log Destination Configuration In this case, log events pass to the first sink, then to the built-in filter, then to the second sink. The first sink receives unfiltered events. The second sink receives filtered events. You might configure error logging this way if you want one log that contains messages for all log events, and another log that contains messages only for a subset of log events. In this case, log events pass to the built-in filter, then to the first sink, then to the second sink. Both sinks receive the filtered log events. Compare that to this  log_error_services  value: The order of components named in  log_error_services  is significant, particularly with respect to the relative order of filters and sinks. Consider this  log_error_services  value: Or you can set it using  SET PERSIST :