mirror of
https://github.com/minio/docs.git
synced 2025-09-14 20:09:30 +03:00
- Adds Audit Kafka tab to list of settings sections - Adds info about diagnostic report uploading to SUBNET Closes #788
106 lines
5.1 KiB
ReStructuredText
106 lines
5.1 KiB
ReStructuredText
.. _minio-console-subscription:
|
|
|
|
===============================
|
|
SUBNET Registration and Support
|
|
===============================
|
|
|
|
.. default-domain:: minio
|
|
|
|
.. contents:: Table of Contents
|
|
:local:
|
|
:depth: 2
|
|
|
|
|
|
You can use the MinIO Console to perform several of the license and subscription related functions available in MinIO, such as:
|
|
|
|
- View the license you are currently using for your MinIO deployment.
|
|
- Subscribe to |SUBNET|.
|
|
- Manage the deployment's SUBNET license.
|
|
- Access Support tools for sharing with MinIO Engineering.
|
|
|
|
License
|
|
-------
|
|
|
|
MinIO offers two licensing options:
|
|
|
|
#. Open source with the :minio-git:`GNU AGPLv3 license <mc/blob/master/LICENSE>`
|
|
#. Paid commercial license with included support direct from MinIO Engineers
|
|
|
|
This page shows the current license status of the deployment.
|
|
You can also begin the registration process to sign up for a paid subscription or add the deployment to an existing subscription.
|
|
|
|
Deployments licensed under AGPLv3 must comply to the terms of the license.
|
|
MinIO cannot make the determination as to whether your application's usage of MinIO is in compliance with the AGPLv3 license requirements.
|
|
You should instead rely on your own legal counsel or licensing specialists to audit and ensure your application is in compliance with the licenses of MinIO and all other open-source projects with which your application integrates or interacts.
|
|
|
|
MinIO Commercial Licensing is the best option for applications which trigger AGPLv3 obligations (for example, open sourcing your application).
|
|
Applications using MinIO — or any other OSS-licensed code — without validating their usage do so at their own risk.
|
|
|
|
Support
|
|
-------
|
|
|
|
Proprietary application stacks that register for a commercial license choose engineering support under either the :guilabel:`Standard` or :guilabel:`Enterprise` License and Support plans.
|
|
Both support plans share the same commercial license to MinIO.
|
|
|
|
The :guilabel:`Support` section provides an interface for generating health and performance reports.
|
|
Support functionality requires registering your deployment with |subnet|.
|
|
Unregistered deployments display a :guilabel:`Register Your Cluster` button to register with your |subnet| account.
|
|
See the :guilabel:`License` section in the Console or visit the `MinIO SUBNET <https://min.io/pricing?jmp=docs>` website for more information on registration.
|
|
|
|
This section contains several subsections.
|
|
|
|
Health
|
|
~~~~~~
|
|
|
|
The :guilabel:`Health` section provides an interface for running a health diagnostic for the MinIO Deployment.
|
|
For clusters connected to the Internet, the report uploads automatically to SUBNET.
|
|
|
|
The resulting health report is intended for use by MinIO Engineering via |subnet| and may contain internal or private data points such as hostnames.
|
|
Exercise caution before sending a health report to a third party or posting the health report in a public forum.
|
|
|
|
If desired, you can download the latest report from the page.
|
|
|
|
Performance
|
|
~~~~~~~~~~~
|
|
|
|
The :guilabel:`Performance` section provides an interface for running a performance test of the deployment.
|
|
The resulting test can provide a general guideline of deployment performance under S3 ``GET`` and ``PUT`` requests.
|
|
|
|
For more complete performance testing, consider using a combination of load-testing using your staging application environments and the MinIO :minio-git:`WARP <warp>` tool.
|
|
|
|
Profile
|
|
~~~~~~~
|
|
|
|
The :guilabel:`Profile` section provides an interface for running system profiling of the deployment.
|
|
The results can provide insight into the MinIO server process running on a given node.
|
|
|
|
The resulting report is intended for use by MinIO Engineering via |subnet|.
|
|
Independent or third-party use of these profiles for diagnostics and remediation is done at your own risk.
|
|
|
|
Inspect
|
|
~~~~~~~
|
|
|
|
The :guilabel:`Inspect` section provides an interface for capturing the erasure-coded metadata associated to an object or objects.
|
|
MinIO Engineering may request this output as part of diagnostics in |subnet|.
|
|
|
|
The resulting object may be read using MinIO's :minio-git:`debugging tool <minio/tree/master/docs/debugging#decoding-metadata>`.
|
|
Independent or third-party use of the output for diagnostics or remediation is done at your own risk.
|
|
You can optionally encrypt the object such that it can only be read if the generated encryption key is included as part of the debugging toolchain.
|
|
|
|
Call Home
|
|
---------
|
|
|
|
.. versionadded:: Console v0.24.0
|
|
|
|
Call Home is an optional feature where a deployment registered for |SUBNET| can automatically send daily health diagnostic reports or real-time error logs to SUBNET.
|
|
Having these reports equips engineering support with a record of diagnostics, logs, or both when responding to support requests.
|
|
|
|
MinIO installs with Call Home options disabled by default.
|
|
|
|
.. important::
|
|
|
|
Call Home requires an active SUBNET subscription.
|
|
|
|
Use the :guilabel:`Call Home` section to enable or disable uploading either once-per-day health diagnostic reports or real-time error logs to SUBNET.
|
|
The health reports and real-time logs are separate functions you can enable or disable separately.
|
|
You can enable both diagnostics and logs at the same time, if desired. |