Feedback Plugin

The feedback plugin is designed to collect and, optionally, upload configuration and usage information to MariaDB.org or to any other configured URL.

See the MariaDB User Feedback page on MariaDB.org to see collected MariaDB usage statistics.

MariaDB is usually distributed with this plugin included, but it is not enabled by default. On Windows, this plugin is part of the server and has a special checkbox in the installer window. Either way, you need to explicitly install and enable it in order for feedback data to be sent.

Verifying the Plugin's Status

To verify whether the feedback plugin is installed and enabled, execute the statement or query the table:

If that SELECT returns no rows, then you still need to install the plugin.

When the plugin is installed and enabled, you will see:

Installing the Plugin

In some releases, the plugin's shared library is distributed with MariaDB by default, but the plugin is not actually installed by MariaDB. There are two methods that can be used to install the plugin with MariaDB.

The first method can be used to install the plugin without restarting the server. You can install the plugin dynamically by executing or :

The second method can be used to tell the server to load the plugin when it starts up. The plugin can be installed this way by providing the or the options. This can be specified as a command-line argument to mariadbd, or it can be specified in a relevant server in an :

Uninstalling the Plugin

You can uninstall the plugin dynamically by executing or :

If you installed the plugin by providing the or the options in a relevant server in an , then those options should be removed to prevent the plugin from being loaded the next time the server is restarted.

Enabling the Plugin

You can enable the plugin by setting the option to ON in a relevant server in an :

In Windows, the plugin can also be enabled during a new installation. The MSI GUI installation provides the "Enable feedback plugin" checkbox to enable the plugin. The MSI command-line installation provides the FEEDBACK=1 command-line option to enable the plugin.

See the next section for how to verify the plugin is installed and active and (if needed) install the plugin.

Collecting Data

The feedback plugin collects the following data:

• Certain rows from and .

• All installed and their versions.

• System information such as CPU count, memory, architecture, and OS/linux distribution.

• The , which is a SHA1 hash of the MAC address of the first network interface and the TCP port that the server listens on.

The feedback plugin creates the table in the database. To see the data that has been collected by the plugin, you can execute:

Only the contents of this table are sent to the .

MariaDB stores collation usage statistics. Each collation that has been used by the server will have a record in output of SELECT * FROM information_schema.feedback , for example:

Collations that have not been used will not be included in the result.

Sending Data

The feedback plugin sends the data using a POST request to any URL or a list of URLs that you specify by setting the system variable. By default, this is set to the following URL:

• https://feedback.mariadb.org/rest/v1/post

Both HTTP and HTTPS protocols are supported.

If HTTP traffic requires a proxy in your environment, then you can specify the proxy by setting the system variable.

If the system variable is not set to an empty string, then the plugin will automatically send a report to all URLs in the list a few minutes after the server starts up and then once a week after that.

If the system variable is set to an empty string, then the plugin will not automatically send any data. This may be necessary if outbound HTTP communication from your database server is not permitted. In this case, you can still upload the data manually, if you'd like.

First, generate the report file with the MariaDB command-line client:

Then, you can upload the generated report.txt from the command line with tools such as :

Manual uploading allows you to be absolutely sure that we receive only the data shown in the table and that no private or sensitive information is being sent.

System Variables

feedback_http_proxy

• Description: Proxy server for use when http calls cannot be made, such as in a firewall environment. The format is host:port.

• Command line: --feedback-http=proxy=value

• Read-only: Yes

• Data Type: string

feedback_send_retry_wait

• Description: Time in seconds before retrying if the plugin failed to send the data for any reason.

• Command line: --feedback-send-retry-wait=#

• Scope: Global

• Dynamic: Yes

feedback_send_timeout

• Description: An attempt to send the data times out and fails after this many seconds.

• Command line: --feedback-send-timeout=#

• Scope: Global

• Dynamic: Yes

feedback_server_uid

• Description: Automatically calculated server unique id hash.

• Scope: Global

• Dynamic: No

• Data Type: string

feedback_url

• Description: URL to which the data is sent. More than one URL, separated by spaces, can be specified. Set it to an empty string to disable data sending.

• Command line: --feedback-url=url

• Scope: Global

• Dynamic: No

feedback_user_info

• Description: The value of this option is not used by the plugin, but it is included in the feedback data. It can be used to add any user-specified string to the report. This could be used to help to identify it. For example, a support contract number, or a computer name (if you collect reports internally by specifying your own feedback-url).

• Command line: --feedback-user-info=string

• Scope: Global

Options

feedback

• Description: Controls how the server should treat the plugin when the server starts up.

  • Valid values are:

    • OFF - Disables the plugin without removing it from the table.

_{This page is licensed: CC BY-SA / Gnu FDL}