hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Notification-Service.md

Browse Source 
Removed change history, changed company name.
This commit is contained in:
Markus Mäkelä
2017-04-19 17:04:46 +03:00
committed by Markus Mäkelä
parent a54d6fe816
commit 1e34bd7642
1 changed files with 8 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
Documentation/Tutorials/Notification-Service.md
View File

@ -1,27 +1,5 @@
# MariaDB MaxScale Notification Service and Feedback Support # MariaDB MaxScale Notification Service and Feedback Support
Massimiliano Pinto
Last Updated: 10th March 2015
## Contents
## Document History
<table>
<tr>
<td>Date</td>
<td>Change</td>
<td>Who</td>
</tr>
<tr>
<td>10th March 2015</td>
<td>Initial version</td>
<td>Massimiliano Pinto</td>
</tr>
</table>
## Overview ## Overview
The purpose of Notification Service in MariaDB MaxScale is for a customer registered for the service to receive update notices, security bulletins, fixes and workarounds that are tailored to the database server configuration. The purpose of Notification Service in MariaDB MaxScale is for a customer registered for the service to receive update notices, security bulletins, fixes and workarounds that are tailored to the database server configuration.
@ -30,9 +8,9 @@ The purpose of Notification Service in MariaDB MaxScale is for a customer regist
MariaDB MaxScale may collect the installed plugins and send the information's nightly, between 2:00 AM and 4:59 AM. MariaDB MaxScale may collect the installed plugins and send the information's nightly, between 2:00 AM and 4:59 AM.
It tries to send data and if there is any failure (timeout, server is down, etc), the next retry is in 1800 seconds (30 minutes) It tries to send data and if there is any failure (timeout, server is down, etc), the next retry is in 1800 seconds (30 minutes).
This feature is not enabled by default: MariaDB MaxScale must be configured in [feedback] section: This feature is not enabled by default: MariaDB MaxScale must be configured in `[feedback]` section:
``` ```
[feedback] [feedback]
@ -41,11 +19,12 @@ feedback_url=https://enterprise.mariadb.com/feedback/post
feedback_user_info=x-y-z-w feedback_user_info=x-y-z-w
``` ```
The activation code that will be provided by MariaDB corp upon request by the customer and it should be put in feedback_user_info. The activation code that will be provided by MariaDB Corporation Ab upon request by the customer and it should be put in feedback_user_info.
Example: Example:
```
feedback_user_info=0467009f-b04d-45b1-a77b-b6b2ec9c6cf4 feedback_user_info=0467009f-b04d-45b1-a77b-b6b2ec9c6cf4
```
MariaDB MaxScale generates the feedback report containing following information: MariaDB MaxScale generates the feedback report containing following information:
@ -57,12 +36,12 @@ MariaDB MaxScale generates the feedback report containing following information:
- All the modules in use in MariaDB MaxScale and their API and version - All the modules in use in MariaDB MaxScale and their API and version
- MariaDB MaxScale server UNIX_TIME at generation time - MariaDB MaxScale server UNIX_TIME at generation time
MariaDB MaxScale shall send the generated feedback report to a feedback server specified in feedback_url MariaDB MaxScale shall send the generated feedback report to a feedback server specified in _feedback_url_.
## Manual Operation ## Manual Operation
If it’s not possible to send data due to firewall or security settings the report could be generated manually (feedback_user_info is required) via MaxAdmin If it’s not possible to send data due to firewall or security settings the report could be generated manually (feedback_user_info is required) via MaxAdmin.
``` ```
MaxScale>show feedbackreport MaxScale>show feedbackreport